[solved] Solving the closing quotation error

Tristan

Hey,

I'm running OpenSesame version 3.0.5 on a Windows computer. However, my experiment won't open anymore due to a missing quotation. There are several topics on this error but I can't seem to find a solution. I tried opening the .osexp file with several text editors but they all seem to show the file in modern day gibberish. Any Idea's on how I can add the missing quotation?

Thanks in advance,

Debug Information:

Failed to parse line "draw textline center=1 color=white font_bold=no font_family=mono font_italic=no font_size=18 html=yes show_if=always text="Er verschijnt een afbeelding <br>". Is there a closing quotation missing?

item-stack: 
exception message: No closing quotation
time: Tue Feb 23 14:36:04 2016
exception type: ValueError

Traceback:
  File "dist\libopensesame\syntax.py", line 170, in split
  File "shlex.pyc", line 279, in split
  File "shlex.pyc", line 269, in next
  File "shlex.pyc", line 96, in get_token
  File "shlex.pyc", line 172, in read_token
ValueError: No closing quotation

sebastiaan

Hi Tristan,

You probably have something in the file pool, in which case the .osexp is really a .tar.gz file (a kind of zip format):

• http://osdoc.cogsci.nl/miscellaneous/file-format/

So you should be able to open the file with a tool like 7zip (and maybe give it a .tar.gz extension so that it's clear what format it is) and extract the script file in this way.

Importantly though, this should never happen. Can you describe in more detail what you did before the problem occurred? And is there a way reproduce the problem? This information would help a lot to make sure that this doesn't happen again.

Cheers,
Sebastiaan

Tristan

Hey Sebastiaan,

Thank you, I managed to fix my problem.

Took me a while to reproduce the problem. Apparently, if you hit enter just in front of the closing quotation the error isn't fixed automatically. Adding text, extra quotations and HTML outside of inside the quotations all seem to be corrected.

The error video for more information:

sebastiaan

Hi Tristan,

Thank you for getting on top of this! That's very useful information, and the issue should be fixed for 3.0.6.

Cheers,
Sebastiaan