Block top-level button assignments on nested press?
An analogue is Razer's Hypershift:
- In the scenario that I have actions defined to a button at the top-level (LBP), and
- I have actions defined to that button (LBP-B) nested within another button (RBP) (so, 'RBP > LBP-B'),
- I need to be able to toggle in LBP-B that on the press event for RBP the actions defined in LBP-B replace the actions in the top-level LBP.
Preferably, if I checked a box in the actions list for the LBP nested under RBP, when I press RBP and then press LBP, only the actions I defined in RBP > LBP would run, as if the actions defined at the top-level for LBP temporarily don't exist.
The current options do not meet this need:
- Stop Further Outputs triggers after LBP's press event is called and would be unusable when
- The actions (ex. left click) cannot be defined exclusively in the Release. I could not realistically use the left mouse button functionality at the top-level if it's only triggered on release.
- Switching profiles would require two consecutive presses. The first would obviously switch the profile and subsequently block further outputs. I'd have to press the button twice and would lose functionality on RBP as a switch back to the parent profile would be required on release of RBP in the alternate/sub-profile.
- Nesting the top-level actions within the top-level does not work. If I attempt to nest the LBP actions within an LBP > LBP event then regardless whether I also define an LBP > RBP empty or wait-only nest, when I trigger RBP > LBP-B, the event LBP > LBP will also trigger.
- Waits are inefficient. I have tried multiple Waits preceding the LBP actions, but because I cannot actually stop the actions following the Wait command from processing until I release RBP > LBP-B, the actions for LBP will also trigger when I press RBP > LBP-B. Further, even a 5ms wait delay is noticeable. (I can't handle it, I'm sorry.)
So, what are some use cases? These are lifted from my gameplay in AC Odyssey, but I think you get the idea:
- I want the Left Fingertip Press to Whistle (Q) / Call Phobos (Holding Q). However, if I am aiming the bow (RBP), I instead want a rapid fire loop on Left Fingertip Press that begins on press and ends on release.
- I have the Left and Right Triggers assigned to a mix of hotkeys that can be tapped and hotkeys that need to be held down. However, if I am holding one of the thumb buttons, I want to trigger only the actions I define under the thumb button for the Left and Right Triggers, not the ones I defined in the Press and Release events at the top-level.
Any help with this is super important. I wish I could help with the development of the driver and software for this mouse. This is one of the most important devices I've ever purchased, and I want to see this thing pushed to its conceivable limits in every direction.