Today we had issues logging button presses and scanner triggers when they were associated to integers.
Example: the scanner’s trigger, which has code 53 but is translated by PTB into “5%”. The button 1 translates into “1!”. Letters seem to be fine.
I do not know why this happened today, I don't think I ever encounter this issue in the past. But probably a simple and robust solution would be to avoid the conversion from code to character, and use the codes directly instead.
Today we had issues logging button presses and scanner triggers when they were associated to integers.
Example: the scanner’s trigger, which has code 53 but is translated by PTB into “5%”. The button 1 translates into “1!”. Letters seem to be fine.
I do not know why this happened today, I don't think I ever encounter this issue in the past. But probably a simple and robust solution would be to avoid the conversion from code to character, and use the codes directly instead.