Closed eah13 closed 7 years ago
Hi,
I think our preference is the first option above -- i.e. stick with the simplicity of the 'up' key always firing an 'up- event.
Changing the mappings depending on the Sense HAT orientation could get very complicated, especially when the key/event mapping changes during the the execution of a program. It may also get confusing for certain situations, e.g. what is the expected behaviour when the yaw is 135?
I've been told that when coding the Astro Pi, children come to realise that the 90 degree rotation of the Sense HAT means that pressing what looks like up actually fires a 'left' event. This is actually quite a nice learning opportunity, and the orientation of the Sense HAT feels like an extension of this same problem.
Sticking with the above also means that the emulator has a clearer parallel to what happens with the physical Sense HAT.
Rik.
Closing! We went with 'up' always firing an 'up' event. This means students will need to learn/visualize how the Sense HAT is oriented in the Astro Pi, which is facilitated by the enclosure toggling.
Howdy testers!
We'd like specific feedback on the key-to-joystick mappings. Currently, the 'up' key on your keyboard maps to the joystick state that sense_hat fires an 'up' keyboard event. This means if you're at yaw=180 and press up in your browser, the joystick will move downwards, towards you and sense_hat will hear an 'up' keyboard event.
There are a few options:
Regardless of what we pick, We'd rely on tutorials to explain the underlying concepts, but the goal here is to choose the least bad cognitive dissonance.