I agree 100% and I think the problem might be bigger than you expect. If you're merely interested in preventing those inputs from hitting an emulator in Retroarch then you're in luck because Retroarch supports volume changing via its hotkey (F1 in RRVL). If it's not already mapped to F1+left/right then you can do it in RetroArch settings. Now regarding mitigation at the global level, this is an entirely different challenge. ogage is the rust daemon RRVL and RR uses to handle global input across all apps and its hotkey is F5. Preventing these global input events from hitting other apps is technically doable but has proved to be quite difficult to do without side effects and/or suffering increased input latency (which we don't want!).kelbot wrote: ↑Sat Sep 05, 2020 10:52 amA couple suggestions to help polish the user experience a bit (I can submit issues for these as well if that would be helpful):
1. If possible, when adjusting volume somehow capture the button presses and not pass them through to retroarch. Currently when you are adjusting volume and brightness the dpad button presses are still registered in retroarch and scrolls and selects things you don't intend to.
I've also thought about this a lot and even tried a few solutions but to no avail. I'm able to write notifications to the console framebuffer but I haven't managed to overlay graphics on top of apps that are already using the DRM/KMS interface. Surely if we operated in X or Wayland this would be much easier but maybe someday someone will figure out a way.