Closed bluecursor closed 2 years ago
I haven't been able to reproduces this.
Just to make sure we're on the same page: I've loaded the demo and opened the virtual keyboard:
After that I pressed "Commodore" and the credits screen appeared:
Pease be aware of #701. The keyboard preferences are broken in the latest version. I.e., you are not able to switch between positional and symbolic mode in v4.4 nor can you use customised key assignments. This will be fixes asap.
@bluecursor please retest with this program https://csdb.dk/release/?id=198164 and report back whether the Commodore key triggers ... thanks
It triggers fine, still… their are still unclaimed keys
Frank Michielli Sent with OSX/iOS Spark! On Oct 21, 2021, 2:23 PM -0400, mithrendal @.***>, wrote:
@bluecursor please retest with this program https://csdb.dk/release/?id=198164 and report back whether the Commodore key triggers ... thanks — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsub
scribe. Triage notifications on the go with GitHub Mobile for iOS or Android.
please append pictures ... preferably with the anykeys.prg ... thanks
v4.5b1 is online.
Either thru typing or using the virtual keyboard, the commodore key c= does not work. It would be nice if you had the ability to map out the special keys on the commodore. ie RUN STOP or RESTORE or C=.
Attached is an example of the need to press then commodore key c=. The key is suppose to show the greets and the main menu. Please fix....
Smoke Exploration Tool, The.t64.zip .