Yeah, this 'xdotool' Tool looks indeed like it is an "Equivalent" like 'AHK' or 'AutoIt' for Ubuntu...groundfalling wrote:found a workaround clicking the dialog box to uncheck and click 'play' usingnext issue is finding a solution for 50 lines limit in the macro code. could you suggest anything?Code: Select all
xdotool
(Could be nice if you could share your 'xdotool' Script btw... )
>>>
For the "50 Line Limit", foufffff...!, I haven't really done any "Thinking" about it, as I don't use v10.0.2 at all for myself so I haven't been "confronted" with that Limit...
Hum..., can't have a Macro call another Macro as the 'URL GOTO=imacros://run/?m=' Syntax is not supported either, grrr...!
Do you still have the same Limit with an embedded Macro in your '.html' Page...? Hum, yeah, I guess so...
Maybe you can play with the 'EventListener' and have several Macros play after each other...?
OK..., one "Solution" that should work, I think..., but it's a bit "cumbersome", ah-ah...! And it's actually already a "better" and more generic Solution for the embedded Macro, as you can reuse the same '.html' Page for different Macros, ah-ah...!
=> '.html' Page with the embedded Mechanism on TAB_1.
Your '.iim' (File) Macro opened on TAB_2. ('.iim' Files are "simple" Text Files that you can open like any '.txt' Files in your Browser...).
Have your "original" '.iim' Script "truncated" in, say, "Sub-Macros" of about 30 or 40 Lines of Code, and separated with some "unique" Separator like "[MACRO_SUB]" for example... Oh...!, no...!, even better!, simply repeat the 'VERSION' Command at the beginning of each Sub-part, ah-ah...!
And you need to repeat also all '!TIMEOUT_xxx' + '!ERRORIGNORE' etc Settings as those get reset for each Macro executed...
Have the "first" 'e_m64' Macro navigate to TAB_2, extract the whole Macro, using 'EVAL()', split it on the 'VERSION xxx' Line, "keep" only 1 'split()' Part (starting at Index=1 because of the first 'VERSION' Line), go back to TAB_1, re-append that Mechanism (hum, might be better to use 3 separate Vars), have the Macro overwrite the 'e_m64' Var (or the 2nd Var), and some 'REFRESH' needs also to be included..., + need to keep track of the 'split()'-Index..., maybe using the OS Clipboard... Same thing if different Sub-Macros need to reuse some '!VARn'... (Hum, it all sounds a bit messy, ah-ah...! )...
The 'REFRESH' will force reloading the '.html' Page that will then execute the first Part of the Macro + repeat the "Automorphism" Mechanism for Part 2, refresh to execute Part 2 and prepare for Part 3, etc...
Might need to concatenate the 'e_m64' Var from 3 Vars, Base64 encoded on the fly...
Hum, like I said, is "cumbersome" and sounds a bit messy, it won't work directly, you'll need to "experiment" a bit, if you get the "Principle", ah-ah...! It's just an "Idea"...
And pfff..., for myself..., I would go "customizing" the Add-on, oops...! It's "Open-Source" after all...! That "50" Limit must be hard-coded somewhere, with some "IF fio.exe Not Found => Limit=50" or stg like that..., then simply increase that Limit to 100 or 1000 or 10000, ah-ah...!