On January 2, 2014 at 17:42, Duct Tape said...
the variable field lets you change the button graphic based on the variable you assign it to.
if you look at the button properties window, you will see that there is a normal and pressed state for both the text and the image itself.
when the variable is true, it displays the pressed state of the image and text.
Okay, I'm probably being dumb, but how is this different than using the Text command down in the actual Macro instructions area? For instance, I have an If/Else statement that uses a Variable for determining the Power Status of a device that provides status commands via RS-232 thru my MRX-2. The query for status is sent to the device, the device responds with a certain string if it is indeed turned On. Based on that response, I then use the Text field to display the words "Power Is On" in bright green letters on the button that is normally called "Power Status". I then have a Delay to display that for a good 6 seconds. Then it goes back to being called "Power Status" again. (it of course does the Power is Off in Red letters if the On string is not returned). In this specific use case, how would the button choice at the top of "Variable" really help me? Would it for instance change the Button permanently? that would be strange, but interesting. Actually, stop the presses, I just tried it and it looks like the "pressed" text is available to you, but only stays there as long as the button is pressed, which is like 2 seconds. I believe this could be useful, but how is that any better/more flexible than my use of the Text command in the macro and then the nice delay of 6 seconds to ensure the user has plenty of time to see the visual display of the button?
Thanks again!