Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Supported by

OpenSesame 3.3.3 released! Includes OSWeb 1.3.8 and Rapunzel 0.4.7

About this update

OpenSesame 3.3.3 Lentiform Loewenfeld is the third maintenance release in the 3.3 series. It contains bug fixes and minor improvements, and should be a pleasant and safe upgrade for everyone who is using the 3.3 series.

As always, you can download OpenSesame from here:

If you are upgrading from OpenSesame 3.2 or earlier, please see the list of important changes:

Credits

Thanks to:

  • Daniel Schreij (@dschreij) for his work on OSWeb, the Mac OS package, and bug fixes

Bug fixes and improvements

opensesame:

  • Updated to 3.3.3
  • Better management of subprocesses

rapunzel:

  • Updated to 0.4.7
  • Better management of subprocesses

pyqode.core

  • Updated to 3.0.0

pyqode.python

  • Updated to 3.0.0

opensesame-plugin-media_player_mpy:

  • Updated to 0.1.11

QOpenScienceFramework:

  • Updated to 1.3.1

Comments

  • In Windows 7, I always have a command window open next to the OS window. If I close it, both windows are closed together. In previous versions of OS, I sometimes had the command window until the OS window was opened, but now it keeps to be there until I close OS. Not sure whether this was intended or is a bug. Just wanted to report it here.

  • @DahmSF I'm aware of the command window thing. It's not ideal, but it's an artifact of how OpenSesame is launched when you directly open an .osexp by double-clicking on it. And I haven't been able to figure out how to avoid this from happening. If you launch OpenSesame from the start menu it doesn't happen, right?

  • edited August 2020

    True. If I open the experiment from within OpenSesame the command window does not appear. Only by double clicking on the experiment (which to me appears the more userfriendly way to open the experiment).

  • Hi Sebastiaan! Unfortunately I cannot launch any .osexp files after updating my OpenSesame to the version 3.3.3. The program itself starts though... What could be the problem?

  • @Alex_M Could you open a new discussion for this, and then explain in more detail what you are doing, and in what sense it goes wrong?

This discussion has been closed.