Blue Eye Macro

If you adjust the throttle on a macro, and any macro.pause or macro.wait has a variable for it's time, it removes that line of code all together.

It works fine for me. Do you click on "update macro" when using the throttle? Does it pop-up a window and state that the new execution speed has been applied? Then what happens...it just deletes pauses?

Post the code so we can see if we can duplicate the problem. Maybe it's something specific because it seems to work fine for me.

Yes it pops up with the window, and all the macro.pause\wait that have time in milliseconds are updated correctly. Just the ones with {vars} disappear. It only deleted the .pause, I didn't have any .wait. Again, I'll try to dig out the version that caused this from my packed laptop.

Oh, I think it's already known...check the bottom of the throttle window (I've circled it in yellow). It looks like the throttle can't be used with variable pauses.

*Although I did get it to work with "humanly.pause", so it may still need to be updated; humanly pauses were just added recently.
**Macro.Wait for execution time...are recorded macros with "timeline" checked.

Yes I've seen that on the throttle window. "for execution time" can still easily be interpreted as to include variables though, since variables (when the program is running) are a value. I understand how it works now, it's just not clear. Why does it need to remove the lines with variables, or is it back to the original post, a bug?

Maybe it could be rewritten...I'm sure Gigus will take a look.

Here's more of an explanation though: When you record a macro with "timeline" selected, it will record all pauses as "macro.wait for execution time" instead of macro.pause. If you decide you want to modify macros that were recorded under "timeline" it's not very fun. You either have to change every execution time or re-record your macro. The throttle feature was added so that users could easily change the timing of these macros without going through all of that. So, if a user has a lot of pauses whether it's macro.pause or execution time, they can easily adjust the timing with the throttle feature. Although it's not it's only use, it's very helpful in adjusting the timing of very lengthy recorded macros.

So, I think after you have read the intended purpose of the tool you will have a better understanding between how your trying to use it and what it was designed for...well, more to the point...what the annotations on that pop-up refer to.