numworks / epsilon

Modern graphing calculator operating system.
https://www.numworks.com/resources/engineering/software/
1.75k stars 463 forks source link

missing simulator keys on the python workshop #2087

Open AngeDieu opened 1 year ago

AngeDieu commented 1 year ago

Describe the bug

The main uper keys of the calculator (such as ON/OFF, OK, HOME, bakspace, xnt, exp...) aren't available in the web simulator on the python script pages (my.numworks.com/python/user/script). This mean it is imposible to test numerous scripts (using the OK key for example) before uploading them on the calculator.

Screenshots

I can't start the game, I'm blocked on this screen: image

To Reproduce

Steps to reproduce the behavior:

  1. Go to the python workshop
  2. Choose any game script (for example antarctus' tanks )
  3. You can't test the game because the is no way to press OK.

Expected behavior

It would be great if we had the calculator keyboard next to the screen, or under as it is on the web simulator. Another option (good also) is to associate all these keys with normal computer keyboard key, and list them in the documentation page somewere we can easily access the corespondance list.

Environment

mobluse commented 1 month ago

The Python script Anykeys shows which keys you press and you can press several at the same time. The last key pressed is shown in the lower left corner. In the emulators on the NumWorks site only a few buttons on your emulator’s physical keyboard work: e.g. Tab (toolbox), Backspace, Enter (EXE), Shift, Alt+x (exp), Alt+v (var), Alt+e (EE), Alt+r (sqrt), Alt+p (pi), Alt+Shift+2 (**2), Escape (BACK) and the arrow keys, but of these only Tab, Enter, Shift, and the arrow keys work in Anykeys. The BACK/Escape key interrupts the program (as it should). None of the JavaScript emulator’s screen keys work with Anykeys. In the emulator for iPhone only the OK button works with Anykeys. It works well with the real calculator, but if you press many keys some non pressed keys might be added or removed; this is probably due to the keyboard matrix circuit.

There are some pull requests regarding this issue: https://github.com/numworks/epsilon/issues/1555

adri1numworks commented 1 month ago

Thank you for your input. Two issues were created internally:

We will likely do first one before the second one. I will keep you updated