Finally found a way to fire a macro using a designated macro key in combo with buttons without the default mapping being triggered. I am using the track pad button as a macro shift. I had to create a macro just for that and added a function to block device outputs. Then when using it in conjunction with another button the default mapping was blocked.
My question is, shouldn't adding a 'block output device' function in the individual macros do that too? Or is that a bug when using two (combo) triggers or when adding another action? Doing it the way I did I would have to use a different button combo if I did want the default mapping to also trigger for some reason.
Asus STRIX X299-E GAMING MB, i7-7820X 3.6/4.5GHz 8-Core, 32GB Corsair Dominator Platinum (CMD16GX4M2B2400C10), NVIDIA TITAN X (Pascal), Samsung 970 Pro 1TB M.2-NVMe w/Western Digital 2TB (WD2000F9YZ), Samsung 65Q9FN QLED, HTC Vive, 850w PS, W10
So to blank out a mapping channel, instead of mapping Source -> (rubbish) you need to map (rubbish) -> Destination. Also, I think what you may be looking for is the "temporary mappings" macro command, this can force a mapping onto a device temporarily while the macro is active
I am brainstorming up a new state modifier designed specifically for handling "shift states". Let me know if this thought process sounds good?
- Each channel that you want to have multiple states will have its own "shift state" state modifier.
- The user will select the input channel (aka the channel that will have multiple possible outputs)
- the user can then add as many shifted states to a list aka "If / Then", each will ask for a "Shift Modifier" ie the button pressed to enable the state, and will also have a command list that has what to do when triggered, I am thinking command list because presumably we want this to have more capabilities than just button outputs.
- There will also be a option for an "Else" condition where if the input is pressed but no shift modifiers are pressed it will do a command or if not chosen will just map back to the input button as if normal.
The input channel will not map their input to the output device (unless the default map input to same output is used in the "else" logic), the "Shift Modifier" will not map to output so long as the input channel is pressed. What this means is if I have multiple states for [cross] and the shift modifier is [L2], when I press just one of either of those channels alone they will still map, so its best to use a non crucial button as the shift modifier such as aim, and not something like shoot, or to use a extra channel like trackpad button.