-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MEGA65+C65: problems with -autoload -go64 #269
Comments
Thanks. I've edited your post a bit to have more visual syntax, if you don't mind. I do not use this feature too much any more. The POKE stuff is intended for faster load by switching into ~40.5MHz mode during the loading and then back for MEGA65 (works in both of C64 and C65 mode). But it's fine for me, if it goes away. Sooner or later (seeing the amount of works, probably "later") this function will be re-implemented with the READY-trigger feature, but till that I'll do that modification since as you stated it works for you this way, then let it be, till that. |
Previously these functionalities used the "fake typing" subsystem which is very picky, and often misses "faked keypresses". It would be nice to try that sorting out (eg also for "pasting any text via fake keypresses"), but it's actually easier to migrate these over the "inject" framework, used also by the PRG direct run (+inject) functionality. Other then -autoload, -go64 alone (to boot into "C64" mode) is much better this way, using only the virtual "Commodore" key without the need to give the "GO64" command.
Drop using the two-phase ?"@" trick to release RETURN, and use a timeout instead. For C64 LOAD, let's use two normal phase though, we can save the ugly keyboard buffer trick (just introduced in the previous commit btw ...), and we can use "turbo mode" for loading too, to speed of LOADing (no need in MEGA65 mode, as it's usually 40.5MHz mode already). Also several clean-ups here and there.
If you use -autoload & -go64 together then it fails as some of the keys are ignored when switching to c64 mode. I have been testing with this change & it appears to work with both xmega65 & xc65
The text was updated successfully, but these errors were encountered: