You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In V5 we introduced a new feature: You can go one menu-level up (from a sub-menu to the main-menu) by pressing Run/Stop. Subsequently you can also close then main menu via Run/Stop (additionally to via Help). But if you do so, the Run/Stop keypress that happens to close the OSM is propagated to the C64.
You can see this for example if you run
10 PRINT "HELLO"
20 GOTO 10
and then - while this BASIC program is running - you open the OSM and then close it via Run/Stop: The BASIC program will be interrupted.
Expected behavior:
The Run/Stop keypress that happens within the OSM shall not be propagated to the C64 core.
The text was updated successfully, but these errors were encountered:
In V5 we introduced a new feature: You can go one menu-level up (from a sub-menu to the main-menu) by pressing Run/Stop. Subsequently you can also close then the main menu via Run/Stop (additionally to via Help). But if you do so, the Run/Stop keypress that happens to close the OSM is propagated to the C64. Fixes: #80
The keypress of "Run/Stop" was propagated to the actually running core if you used Run/Stop to close the menu. This lead to undesired consequences for example on the C64: MJoergen#80
In V5 we introduced a new feature: You can go one menu-level up (from a sub-menu to the main-menu) by pressing Run/Stop. Subsequently you can also close then main menu via Run/Stop (additionally to via Help). But if you do so, the Run/Stop keypress that happens to close the OSM is propagated to the C64.
You can see this for example if you run
and then - while this BASIC program is running - you open the OSM and then close it via Run/Stop: The BASIC program will be interrupted.
Expected behavior:
The Run/Stop keypress that happens within the OSM shall not be propagated to the C64 core.
The text was updated successfully, but these errors were encountered: