first of all I want to say that I am having great time program my experiments in open sesame
after working on my experiment when I select the logger I see only the script page and when I try to apply or discard changes I get the error message "super(type, obj): obj must be an instance or subtype of type (Edit the script to fix this)"
and also when I try to open file by double clicking I get an error that the log file could not open (access denied errno.13)
I run it from admin account, and I tried to re-install opensesame.
last question, is there a better way searching the forum except from the search bar on top?
thenx
hi first of all I want to say that I am having great time program my experiments in open sesame
Thank you!
when I select the logger I see only the script page and when I try to apply or discard changes I get the error message "super(type, obj): obj must be an instance or subtype of type (Edit the script to fix this)"
This is probably not related to the logger. Do you happen to have two instances of the
form_consent
plug-in? If so, this is a known issue:
https://github.com/smathot/OpenSesame/issues/116
. If not, could you perhaps post a screenshot of the overview area of your experiment?
when I try to open file by double clicking I get an error that the log file could not open (access denied errno.13) I run it from admin account, and I tried to re-install opensesame.
Do you mean that you get an error when you try to
open
an experiment by double-clicking on it? Or do you get an error when you try to
run
an experiment after you have opened it? If the last is the case, you simply should select a location for the log file where you have write access. If the first is the case, could you provide some more details (i.e. what happens
exactly
)?
last question, is there a better way searching the forum except from the search bar on top?
You could try
The old search site:
http://www.cogsci.nl/search/
Google:
https://www.google.com/?q=site:forum.cogsci.nl
Cheers,
Sebastiaan
1. I sent you the log file and the exp.
2. where I can see if I have two form_consent plug-in?
3.open sesame crash after double click on an experiment (to open it in opensesame -not run it) it works ok when I open it after opensesame is already open.
4.and finally - after the logger problem occurs - there is no variables in the variables inspector.
Traceback (most recent call last):
File "dist\libqtopensesame\qtopensesame.py", line 708, in refresh_variable_inspector
File "dist\libqtopensesame\widgets\variable_inspector.py", line 85, in refresh
File "dist\libopensesame\experiment.py", line 600, in var_list
File "E:\OpenSesame\plugins\form_text_input\form_text_input.py", line 82, in var_info
return super(form_text_input, self).var_info() + \
TypeError: super(type, obj): obj must be an instance or subtype of type
Traceback (most recent call last):
File "opensesame", line 94, in
File "dist\libqtopensesame\qtopensesame.py", line 850, in open_file
UnicodeDecodeError: 'ascii' codec can't decode byte 0xee in position 22: ordinal not in range(128)
Traceback (most recent call last):
File "opensesame", line 94, in
File "dist\libqtopensesame\qtopensesame.py", line 850, in open_file
UnicodeDecodeError: 'ascii' codec can't decode byte 0xee in position 22: ordinal not in range(128)
do you need the experimant file? (how can I post it here
thenk you
Open the "General properties" tab, click "Script editor" and copy the whole script,
go to
pastbin.com
or
gist.github.com
, upload your script there (simply paste and submit)
and provide us with the resulting link in your forum post.
Best,
Lotje
Did you like my answer? Feel free to
I tried to delete the form and to replace it with text input and it worked! all the errors vanished, don't know why...
thank you for your help
Hi Dror,
Thanks. This is indeed a bug, similar to the one that I had already identified (and fixed in the development version) for the
form_consent
plug-in. Basically, the error will be triggered when
there are two instances of a
form
plug-in (probably not just
form_text_input
)
and the variable inspector is visible
For now, a simple workaround would therefore be to not show the variable inspector, at least not when opening and interacting with these plug-ins. I appreciate that this is not very convenient, though.
A
bug report
has been filed, and it will be fixed for the bug-fix release that is planned for 0.27.
Cheers!
Sebastiaan