I'd like to encourage this effort as it seems quite promising.
As for this emulator, I guess that the idiosyncrasies of JavaScript's key handling feed into the problem. I see that on my keyboard, the Ø and Æ keys, which reside in the physical positions that ; and : occupy on the Electron, do produce those symbols, along with the corresponding shifted symbols (+ and *). However, the + key on my keyboard, which resides in the position of -/= on the Electron, doesn't do anything here, but the - key on my keyboard, which is situated between ./: and right shift, does work.
Here, I also see that F12 is mapped to Break. This was an issue with Elkulator, where Ctrl-Break then becomes unusable because stupid desktop environment developers love to steal key combinations involving F12 and then hide or remove the setting that might get it back. In my case, the desktop does some kind of performative minimisation of windows that presumably looks great in a conference demo but otherwise has an indecipherable purpose (other than to minimise the windows and leave some kind of trace of them in the corners of the screen).
The lack of keyboard configuration is something that makes jsbeeb less than usable on many occasions, meaning that I don't get to fully appreciate various interesting projects that are casually demonstrated via that emulator. If I have missed anything with regard to jsbeeb - a fine piece of work and surely an inspiration for this emulator - or indeed this effort, please let me know. I hope that this kind of feedback is helpful.
Emulators can be a pain when it comes to keyboard layouts, not always addressing the issue thoroughly. ElectrEm was a notable exception, and I once put some effort into doing Norwegian layouts, both "logical" which attempted to preserve the key functions of the user's own keyboard (more useful for applications), and "physical" which attempted to map the user's keyboard as closely as possible to the physical layout of the Electron's keyboard (more useful for games). Frustration with Elkulator in such matters, which did support keyboard redefinition but clumsily, eventually drove me to take action and make it usable for more than casual gaming.The ;+ and :* keys on the Japanese keyboard are the same as on a UK keyboard, however neither do anything on Electroniq.
As for this emulator, I guess that the idiosyncrasies of JavaScript's key handling feed into the problem. I see that on my keyboard, the Ø and Æ keys, which reside in the physical positions that ; and : occupy on the Electron, do produce those symbols, along with the corresponding shifted symbols (+ and *). However, the + key on my keyboard, which resides in the position of -/= on the Electron, doesn't do anything here, but the - key on my keyboard, which is situated between ./: and right shift, does work.
Here, I also see that F12 is mapped to Break. This was an issue with Elkulator, where Ctrl-Break then becomes unusable because stupid desktop environment developers love to steal key combinations involving F12 and then hide or remove the setting that might get it back. In my case, the desktop does some kind of performative minimisation of windows that presumably looks great in a conference demo but otherwise has an indecipherable purpose (other than to minimise the windows and leave some kind of trace of them in the corners of the screen).
The lack of keyboard configuration is something that makes jsbeeb less than usable on many occasions, meaning that I don't get to fully appreciate various interesting projects that are casually demonstrated via that emulator. If I have missed anything with regard to jsbeeb - a fine piece of work and surely an inspiration for this emulator - or indeed this effort, please let me know. I hope that this kind of feedback is helpful.
Statistics: Posted by paulb — Sat Nov 23, 2024 12:52 pm