OS 0.27~pre22 Bug report/Feature requests

Daniel

I almost find no serious bugs or error anymore, nice job going on there. I do however have one feature request that is related to a previous one.

When you choose to open a new experiment from the menu, the file browser's location will be the folder in which you last opened or saved an experiment. For the file pool however, the file browser always defaults to the opensesame program folder. Would it be possible to let the file pool browser show the same behaviour as the "Open Experiment" browser (e.g. start in the folder where you previously left off).

I'll see if I can do some thorough tests of this version soon...

sebastiaan

Thanks, yes, that's a good suggestion. I fixed it and I hope that I also fixed the keyboard problem. I'm not 100% sure what caused it, though, so please let me know whether or not the keyboard issue is gone with 0.27~pre23 (which I'll upload later today).

Cheers!

Michif

Hi sebastiaan,

I have an issue here: When I save a list with exp.set in an inline script it is stored as a unicode. Example:

col2 = [120,1,.25]

exp.set('col2', col2)

%Retrieving it in a next inline script script

col1 = [120,1,.75]

col2 = exp.get('col2')

test = col2[2] / col1[2] %wont work

ERROR:

unsupported operand type(s) for /: 'float' and 'unicode'

Michif

Just checked with Daniel: maybe it does not come from .set but from .get?

col2 = [120,1,.25]

exp.col2 = col2

%Retrieving it in a next inline script script

col1 = [120,1,.75]

col2 = exp.get('col2')

test = col2[2] / col1[2] %wont work

ERROR:

unsupported operand type(s) for /: 'float' and 'unicode'

sebastiaan

The set() and get() methods are intended to store and retrieve your experimental variables, i.e. variables that you want to write to the log-file, strings that you want to show, etc. As you experienced, they will automatically convert values to a float, int, or unicode, depending on what you put in. They are not intended to store more complicated objects, such as lists.

Presumably, you are set()-ing the list, because you want to access it later on, right? If that's the reason, you will want to declare that variable global instead:

global col1
col1 = [120, 1., .75]

Hope this answers your question!

Michif

True. Okay, I thought this was not intended which is why I posted it here, sorry!