Sequential commands, One button

[S77th-ReOrdain]

Hi Z,

I've done some searching to see if this has been asked previously but didn't find this question. Just wondering if you've ever explored the possibility of programming more than one command on a single button (hotspot). I guess a better way of putting it is: If you push a button once it issues a specific command, the second time you push it, it enters an alternate command.

For example, SytRep's F4:AF profile uses the Radar altimeter button which actually has (3) states, (on, standby and off). The button can indicate all three states no problem, but each state is a different set of key presses (Shift-A, Alt-A and Ctrl-A). Currently, the alternative I'm using is to have four separate buttons, (1) for each of the (3) commands and (1) to indicate which state is active. I've also tried the clone feature as an alternative but using the toolkit with the cloning feature will change the clone to the button it is emulating. I know this is probably a hassle, otherwise it would be simple to come up with a solution for buttons that remain in state when another that cancels its function is selected (i.e., autopilot states on the Su-25T in Lock on). The only other alternative I can think of is to simply allow a button to alter the state of another, without actually entering the command. Just a thought, and ultimately something that would be nice to have working in conjuction with the TB Toolkit.

[Wild.Bill.Kelso]

Currently, you can do 2 states using a Hold or Touch button using the macro_select and macro_deselect macros.

What if there were a:
macro_1 =
macro_2 =
macro_3 =
:
macro_x =

Where each time the button was pressed, it executed the next macro. Then at the end it started over with the first macro?

[S77th-ReOrdain]

WBK - Looks like your macro sequence is exactly what I was trying to describe. I've tried using macro_select and macro_deselect, but in a different manner, with not much success. I'm probably not interpretting the function correctly, 'cause I've tried to use it as a trim feature, whereas when pressed as a hold (macro_select) it would begin to trim, when unpressed (macro_deselect) the trimming would stop and maintain that level level of trim.

In your described sequence, if a cycle button state macro could be put in as well, touchbuddy would be virtually unstoppable and would rule over all other game programs (for me, it kinda does now ). But can you imagine the possibilities in programming if you could add to the sequence:

macro_1 =
macro_2 = (cycle state of tab_button_autopilot)
macro_3 =
macro_4 = (cycle state of tab_button_autopilot)
:
macro_x =
Where specific states of buttons on selected tabs could be altered.

or,

macro_select1 =
macro_2 = (reset state of tab_x_button_apbarohold)
macro_select3 =
macro_4 = (reset state of all buttons on tab_z)
macro_select5 =
:
macro_x =

In the above condition, the simple macro following macro_select would run automatically and remain in a paused state. When pressed again, it would continue the sequence until you got to x at which point it would reset. I do realize that this is complex, but it would offer unlimited flexibility over all buttons and tabs with a single button. The alternative to return to previous states is to go to the *TB* tab and reset, which will likely return to initial state, buttons that you would like to remain on their current displays.

[Wild.Bill.Kelso]

When you say 'states' are you just referring to the image that is displayed?

[S77th-ReOrdain]

Yes. Or, to be more specific state1, state2 . . . indicating whichever image it may be on a toggled button.

[Wild.Bill.Kelso]

Ok. Well wait for Zorlac to respond to this. It seems like something could be done, but he'll know better.

[zorlac]

This is on the list for v1.4. It will act pretty much like a "toggle" button, but will allow a new macro set per "state" as you cycle through them.

[S77th-ReOrdain]

Excellent. Looking forward to it.