Repository navigation
creating controller overlay toggle/autohide #2350
Unanswered
TheDoogie-crypto
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Help. I'm new but I'm trying everything.
Goal of the mod
Virtual controller overlay ON when no controller connected
Virtual controller overlay OFF automatically when a controller is connected at boot
Overlay comes back when controller disconnects
Overlay editor still works
No graphics API crashes
Controller settings toggle for manual override (later phase)
The key lesson from my two failed builds so far:
Never interfere with startup initialization.
Let Flycast initialize normally, then react to controller changes.
setVGamepadEditMode() is more critical than it sounds
overlay delegate must still initialize
Flycast startup order is fragile
controller-at-boot ≠ controller-after-launch
Android graphics init can fail if lifecycle timing changes
edit overlay and touch system are coupled
Now avoiding start hacks, event hacks only.
I realize that obviously this hasn't been implemented before for a reason. Please help if you know anything 🙋🏻
Trying to add Android auto-hide for virtual controls when a physical controller is connected. Startup checks in NativeGLView broke overlay editing and caused init issues. Is there an existing input lifecycle hook or listener path you’d recommend for toggling VirtualJoystickDelegate visibility safely after initialization?
All reactions