AOZ Studio V1 (TBD bugs clean/-> V2)

Correction to example results above:

Keys: q w e r t y u i o p
should return 16 17 18 19 20 21 22 23 24 25 26 27.
instead returns 0 0 0 NaN NaN NaN NaN NaN NaN NaN NaN 0

Also verified this is still broken in 0.9.5
Adjusted affected version from 0.9.3.2 to 0.9.5.

Fixed! And thank you for the table of scan code, I never could find one... (Y)

Thank you! ...but it's only mostly fixed. Some codes are still wrong:

\ to the right of the "querty" row should be 13 vs. 43.
Enter on the keypad should be 67 (different than regular Enter: 68).

Hopefully that's the last of them.

Also, (another issue), but Key State is all screwed up. Here's what Key State should return:

Bit 0:    1 Left Shift  instead returns 3 (combined left & right shift)
Bit 1:    2 Right Shift instead returns 3 (combined left & right shift)
Bit 2:    4 Caps Lock   returns NOTHING
Bit 3:    8 Ctrl        returns 8 (this is the only one working)
Bit 4:   16 Alt     returns 48 (16 + 32)
Bit 5:   32 ??? usused ???
Bit 6:   64 ??? usused ???
Bit 7:  128 ??? usused ???

Finally, I'm not sure about this, but I think some of the keys that return the states are also supposed to return scan codes. (I'll have to test this on a real Amiga to see.)

The problems I mentioned in 0.9.5.1 remain.

One more problem found. Both of the enter keys will not sustain the key down state.

They will reset while the keys are still held down.

(This is besides the fact that they should return different codes. Perhaps this is related?)

Oops! Forgot to up the "affected version". Problem still exists in 0.9.6.3

Tested again in 0.9.9. It works better. Now some of the shift states work, but many keys are still messed up.

The shift states are about half fixed now.

Bit 0:    1 Left Shift   WORKING!
Bit 1:    2 Right Shift SHOULD return 2, instead returns 1.
Bit 2:    4 Caps Lock SHOULD return 4, instead returns NOTHING
Bit 3:    8 Ctrl            WORKING!
Bit 4:   16 Left Alt     WORKING!
Bit 5:   32 Right Alt   SHOULD return 32, instead returns 16
Bit 6:   64 Left Meta WORKING!
Bit 7:  128 Right Meta SHOULD return 128, instead returns "ContextMenu" in Inkey$  This will be a problem in BOTH Amiga and PC manifests!
  When someone hits the "ContextMenu" key we don't need C o n t e x t M e n u in the input buffer!!!  This is another modifier key and should return *nothing*!

I also still suggest adding:

bit 8: 256 to detect the Right Ctrl key. (Again, should return nothing in the input buffer, just a shift state.)

Also... right now, you can't enter a control key. Instead of having Ctrl modify the letter typed, it enters that letter into the input buffer / Inkey$

Ctrl-a returns the proper shift state, but instead of putting Chr$(1) into the buffer, it puts "a" in.
Ctrl-m again returns the proper shift state, but instead of putting Chr$(13) into the input buffer (just as Enter should), it puts "m" in.
As mentioned above, the Enter key, instead of putting Chr$(13) into the input buffer, puts "Enter" E n t e r into the input buffer. Definitely a problem no matter what manifest is in use!

(Think abut these keys with respect to say, writing a word processing program! MAJOR problem!)

What if someone wants to use the Right Meta key? Right now, instead via the input buffer & Inkey$, they'll get 11 keystrokes, "ContextMenu", instead of the appropriate shift state : 128! Again... a MAJOR problem no matter what the manifest.

I fixed these a while back. The modifier keys are all working now. There are slight differences betweeen browser implementations which have been accommodated. In the Amiga manifest, the proper scan codes are returned with the exception of 0. This is unavoidable due to the current implementation. It also better corresponds to the AOZ/PC version. In AOZ mode, for the most part, event.what is returned... which will be the JavaScript equivalent of scan codes.

NOTE: Perhaps in the future, we can add the option of returning actual PC scan codes for better compatibility with other PC applications.