So you've told us we can suppress the system pause menu with this:
poke(0x5f30,1) |
And that works great. However, I wanted to write something that allows you to access both the game pause and the system pause, by using short presses for game pause and long presses for system pause. Unfortunately, there's a bug/misfeature/oversight that prevents this:
You're still debouncing the button at the system level, even if the system menu is disabled, so if the button is held down, it's only reported down on the first frame. This prevents me from detecting a long press.
I'm guessing this is just because you check the menu-suppression flag after you've recognized and absorbed the button press, rather than wrapping the button check as well.
Any chance of a fix in the next version? :)
Here's a quick demo of what I was trying to do. I had to write a quickndirty little fake pause menu that runs off of the 🅾️ button instead, just so the button wouldn't auto-debounce, but otherwise it works the same:
So one approach is to first open up a custom pause menu at which point additional ENTER presses bring up the system menu.
Except additional enter presses are intuitively what the user would use to close the custom pause menu.
Also @trevorade, I think this is less about HOW to overcome Felice's particular problem and more about the inherent issues with being unable to detect long pause presses in general. One would assume it would work like any other button press, being able to check if the button is being held or has been released should be doable for all buttons, including pause.
[Please log in to post a comment]
