Bug report: OpenSesame 0.27~pre 26 (italian translation)

embodiment

I report two bugs.

• There's a bug due to the italian translation. If you set the order of a loop as random, OS always run in sequential order because, I think, it doesn't recognize the italian translation "casuale". Indeed, if I modify the loop script replacing "casuale" with "random", it works.

---

• Another strange behavior is that, when you try to manually modify an element by the script, you have to repeat twice "apply and close", or "discard and close", before the script window is closed.

sebastiaan

Thanks! Indeed, a similar bug to the one that you reported before: 'sequential' and 'random' should not be translated by the GUI, because these words have a special meaning.

Regarding to the second bug. I don't see the same behaviour. Do you have a specific recipe to reproduce this issue?

Cheers!

embodiment

I work on a Windows 7 PC. Here are the steps by which I encounter the problem.

1. open a simple default template
2. open the script editor of the Welcome sketchpad element (but the problem appears also, for example, with the notepad)
3. modify the script
4. click on "apply and close" and confirm the new name. The editing window is still opened.
5. click again on "apply and close" and now OS returns to the sketchpad window.

sebastiaan

I just tried it also under Windows 7, and I don't experience the same thing. Is there any other indication that something goes wrong? E.g. perhaps there is an error message in opensesame.exe.log when you close the program? If it does no harm, then I guess it's not a big deal, although it's definitely strange.

And what do you mean by:

click on "apply and close" and confirm the new name. The editing window is still opened.

You don't mean that you are renaming the item, right? It's really about applying the script after you have edited it?

Cheers!

embodiment

No, there is no opensesame.exe.log file in my folder. I run OS~pre from source, so I thought that the problem could arise from something wrong in my installation. So, I tried OS-0.27 standaolne, with the same results. I also noticed that the "discard changes and close" button doesn't work for me.

In this video I show in detail what happens.

Cheers,

Andrea

sebastiaan

Thanks for taking the time to make that screencast. I see what you mean now. Somehow, OpenSesame apparently interprets clicking the script buttons as a rename signal, because the rename dialog should not appear. Still, I haven't managed to reproduce this issue...

• Just to be sure: The screencast is taken using the 0.27~pre26 binary package, right?
• Does it always happen, or only sometimes?
• Does it also happen if you disable the Italian locale (i.e. by starting with opensesame --locale en_EN)?
• Finally, if you run OpenSesame in debug mode (i.e. by starting it from a command prompt or with a bash script like opensesame --debug) you should see all kinds of messages appear. Could you by any chance post the debug output that you get when you trigger this problem?

A very strange issue...

embodiment

Hi Sebastian.

• yes, I used the 0.27~pre26 binary package
• the problem always appears, also if I disable the Italian locale
• I have run OpenSesame in debug mode but no messages appear in the debug window, related to this problem.

I have tried to unistall all the programs of my manual installation of OpenSesame, because I have reasoned that some kind of "conflicts" could be the cause of the problem. Same problems...

After that, I have re-installed OpenSesame 0.26, but this time from the .exe file and not from source: now the problem appears also in the 0.26 version! The differences are that OpenSesame 0.26 asks me to rename the element only once, and the "discard changes" button works.

I have tried OpenSesame 0.27 binary package on another machine with Windows 7, and the "apply" buttons worked (the rename window didn't appear). However, the "discard changes" button still didn't discarded the changes! On this machine I have run both the english and the italian version of the program.

Since you can't reproduce the problem, I seriously think that it is due to pecific settings of my PC, at least for the "apply" buttons.

Yes, it's a very strange behavior. :-/

sebastiaan

I actually did find a bug yesterday, which explains why changes to the script were applied when the discard button was pressed: The script was applied automatically when it lost focus (just like for example the inline_script items). This should be fixed as of 0.27~pre27.

This may be a different issue though: It is not clear to me if and how this explains the other issues (i.e. the rename window appearing).

embodiment

Yes, the pre27 discard button now works but, more importantly, I found the source of the "apply" problem. In the preferences, "offer to rename new items immediately" was cheked. It was my distraction, of course. ">

I am not sure, however, that such preference has to be applied when you modify an element by script.

Best,

Andrea

sebastiaan

Yes, that's it. :-) Mystery solved. I guess I should just remove this option altogether. I doubt many people use it, and it just adds some complexity and potential for trouble (as we have experienced!). What do you think?

embodiment

Well, I had checked that option because I generally use to rename the new items immediately, so it was comfortable for me. But, of cource, if it should not be available in future, I think it will not be a great loss. Stability first.

Daniel

Bug: For an experiment that was made in OpenSesame 0.26 and which uses the deprecated OpenGL backend, the backend selection box in OS 0.27 is greyed out and fixed on psychopy. You don't get the option to alter the backend anymore.

---

Bug: On help pages, the button "Done" at the top right does nothing. The only way to exit a modules help page, is to click on the module again in the Overview section

---

Feature request: Is there a reason OS 0.27 still uses PyOpenGL 3.0.1? Version 3.0.2 recently got released and, next to a lot of bug fixes and performance improvements, it offers a lot of additional functionality (framebuffers, shaders, etc.), that might be useful. I strongly recommend to update the PyOpenGL version that is packaged with OpenSesame 0.27 to 3.0.2
(On windows, the official package of PyOpenGL 3.0.2 didn't work correctly for me (missing dll's), so I downloaded another distro from http://www.lfd.uci.edu/~gohlke/pythonlibs/, which worked perfectly.)

embodiment

Bug: if you try to show this

______________ INSTRUCTIONS ¯¯¯¯¯¯¯¯¯¯¯¯¯¯

by a textdisplay item, it will show the default 'enter your text here'. It seems due to the underscores above the text, and not to the macrons below.

---

Feature requested related to the first bug reported by dschreij: an experiment created on 0.27 using Xpyriment is obviously not runnable in 0.26, since it doesn't recognize the backend. It could be useful to enhance the compatibility, by making that 0.27 automatically creates a script that checks the actual version of OpenSesame and, for experiments created in Xpyriment, converts the backend in Legacy.

sebastiaan

Thanks guys!

For an experiment that was made in OpenSesame 0.26 and which uses the deprecated OpenGL backend, the backend selection box in OS 0.27 is greyed out and fixed on psychopy.

Right. The back-end combobox offers a number of standard back-ends, and if something non-standard is selected, it greys out. You can still change the back-end by opening the script editor and changing the back-end variables, as described here. I appreciate that this might be confusing for the few users that were using the OpenGL back-end. But I nevertheless think it's a good approach, because it prevents people from selecting a deprecated back-end when starting a new experiment.

It could be useful to enhance the compatibility, by making that 0.27 automatically creates a script that checks the actual version of OpenSesame and, for experiments created in Xpyriment, converts the backend in Legacy.

I'm afraid this will be tricky, as it would require retrospectively updating 0.26 so that it deals with the xpyriment back-end by switching to legacy. Wouldn't it be easier to select the legacy or psycho back-end if you intend on running the experiment with 0.26? (And as described above, you can always change the backend using the script editor.)

Bug: On help pages, the button "Done" at the top right does nothing.

That is not a button ... It's a status indicator that says when the page has finished loading. For the help files on your computer this doesn't make a lot of sense, I know. But it does when you open a web-page with the help browser (because the same browser is used for the help files and the web pages).

The only way to exit a modules help page, is to click on the module again in the Overview section.

If you enable one-tab-mode, that is how the GUI always works, isn't it? A tab remains open until it is replaced by a new one. If you disable one-tab-mode, you will see the close buttons on the tabs again, and you can also have multiple tabs open at the same time.

Is there a reason OS 0.27 still uses PyOpenGL 3.0.1? (...) On windows, the official package of PyOpenGL 3.0.2 didn't work correctly for me (missing dll's), so I downloaded another distro from http://www.lfd.uci.edu/~gohlke/pythonlibs/, which worked perfectly.

Thanks for the heads up! I wasn't aware that 3.0.2 had been released and I'll check it out.

Bug: if you try to show this

______________
INSTRUCTIONS
¯¯¯¯¯¯¯¯¯¯¯¯¯¯

by a textdisplay item, it will show the default 'enter your text here'.

Indeed, this is a bug, thanks!