My use case is as follows.
I use a Momentary Button/Display (Text) button to show radio data via "Title Text Change on DCS Update Settings". I'd love for the press of this button to change the radios, however it requires me to string together a 3-key macro in the Apache. I could do that with either a Multi Action button, or a Super Macro (BarRaider), but of course that means creating another button.
One solution in my opinion, is that the DCS Command could become a series of commands, with delays definable. Maybe a section in the Export profile to lua-code up key-press combinations into one Button ID, similar to how you use the Export profile to SendData for a Title Text Change.
I imagine that macroing key presses is not unique to any particular airframe, and would be a good update for your tool in general.
My use case is as follows. I use a Momentary Button/Display (Text) button to show radio data via "Title Text Change on DCS Update Settings". I'd love for the press of this button to change the radios, however it requires me to string together a 3-key macro in the Apache. I could do that with either a Multi Action button, or a Super Macro (BarRaider), but of course that means creating another button.
One solution in my opinion, is that the DCS Command could become a series of commands, with delays definable. Maybe a section in the Export profile to lua-code up key-press combinations into one Button ID, similar to how you use the Export profile to SendData for a Title Text Change.
I imagine that macroing key presses is not unique to any particular airframe, and would be a good update for your tool in general.
Thank you for your consideration.