al_keys / Keyboard Setup

[paul-gallenkemper]

Hey Rasmus,
We now want to be able to give experimenters the option to control parts of the experiment from another position, so we now have a second keyboard aswell as some chunks of code that use these functions:
"pause;"
as well as
"input(input test, 's');"
in addition to your
al_bigScreen(...)
which uses "KbCheck()"

It all works, but the input these functions take is very limited. Usually, they should take "any key", so that we can instruct student conductors (SHKs) to always use "enter". But, these are the oddities we find:

• for the first call of "pause;" only the inputs ü, ö and ä work, as if the "usual" keyboard was blocked.
• the bigScreen should be ended by "enter" (which is defined as the key number 37), but it actually is only ended by the s key, which is defined as 40.

As of now, my workaround is to instruct the experimenter which buttons to press to continue by giving output like
disp('Press s to continue');
It would of course be less error-prone if we could always choose enter as the key that simply continues the procedure

Debugging done so far:

• i could confirm the assignment of keys by calling KbNames() individually
• when calling "locale" in bash, everything is set up in German, this should not be the problem.
• the same issue occurs, when the second keyboard is disconnected.

If you want to look into the implementation in detail, check al_infantConditions in the version of your repository on my github: https://github.com/paul-gallenkemper/Infant-version-Cannon-Task/blob/infant_version/Task/TaskVersions/ResearchUnit/Infant/al_infantConditions.m

Best regards,
Paul

[paul-gallenkemper]

PS: The same problem with the input (it only taking ö,ü or ä) also occurs when i use the input() function instead of the pause; function at first. Afterwards, it resets aswell.