'Archer' has some really nice 'Wait' icons for the pressed button state, but you don't get to see much of them.

I think that it would be good if a button remained in the 'pressed' state for as long as the Action-list of the button was being executed. Perhaps that would interfere with holding it down for repeat actions?

What do other's think about this (as a wish item of course)?

BTW, I stumbled across an interesting way to post a 'busy' icon for those long action-lists: Make the first action a JUMP to an "I'm busy" page, let it run the rest of the action list, the last of which is a jump back to the original page (or to whatever other page you intended to jump to).
Barry

You will see a Tuning - Please Wait (and others) page on my Midnite and Blizzard PCF's when you press a button that has a macro that is several seconds long.

Archer

I was thinking of something similar. The best thing about the NG is the ability to put jumps in the middle of macros. Watch this. Take, say, 200 pixels of the window's width. Divide it into 100 2-pixel wide chunks. We all have macros that take lots of time. The important part of the macro is when it is sending a command. Take the number of commands you actually send and divide it by 100. Immediately after a command is sent, jump to a new page whose status bar is that much percent (x2 per pixel) farther along.

Say you have 4 commands, with pauses in between to sync things up. Before the first command, jump to a status page that has 0% filled. Send the first command, and jump to a page that has a 50-pixel long (25%) status bar. Pause until the next command. Send the next command, then jump to a 100-pixel long bar. ... After the fourth command, update to 100%, pause for a split second, then goto the real device panel.

Now all I need is to sell my old TSU-2000, and get a 3000 so I can implement this. Sad thing is, a friend from work may buy it. He has a 1000, and is looking for TWO MORE PRONTOS!!!! His wife (also a co-worker of ours) is gonna kill me.

Frank

The problem with that is that your macro will just take longer to run. I just did a test where when a button was pressed it ran a macro that had 9 page jumps and nothing else in it. It took 11 seconds to do those 9 page jumps. So roughly if you added four extra page jumps to a macro, your going to extend its playing time by 5 seconds.

It will take a little more testing to verify that because the other steps might be running while the page is loading thus reducing the overall time!!!

that sounds like a good idea, I am going to have to try that one.. I'll get back with the results.