tass_co wrote: ↑September 10th, 2023, 3:54 pm
I have 2 computers. Dual-core Celeron 1037U 1.8 GHz. It consumes 30-40 watts of power. I use this computer only for torrent downloading. When I overload it, there are lags/freezes, which is normal for the processor. So it's nothing to do with the Rainmeter app. Becasue when I use the same code on second my PC, I do not encounter any problems etc. (Ryzen 9 5900x)
The name of the Macro application I am using is Macro Express Pro.
Unfortunately, I have no idea how to change the number of repetitions outside the application
But as you said, maybe it can be done with a different application.
As can be seen, the macro content is simple.
+Activate the qBittorent window
I'll take a look at the AutoIt app
I see. Yeah, it depends on how powerful is the computer and how much stuff runs in the background. All I'm saying is that is much more efficient and light on recources to run a program just once and perform a loop several times per second from inside its macro script, than running that program or the .mxe several times per second to perform a single step in the loop.
I suspected you use a different application than AutoIt or its sister app AutoHotKey (both free, by the way, with the script language roughly similar between the two, bar some syntax differences). As far as I can tell, Macro Express Pro has loops too, see here
, the only questions would be how to set the stuff from your one step macro to repeat itself a number of times using those repeat commands, and how to pass that number of times to the main application or the .mxe file. The latter is mostly done via command line parameters in other similar programs, so maybe it would be possible in this case too (e.g. ["#Path2#\TorrentAccept.mxe #Again#"]
or something along those lines, and grab the #Again# parameter as a variable in your macro in order to know how many times to repeat a single step in the loop).
One more thing about your script: it will work for your configuration, screen resolution and such, but not necessarily on other systems, since the Mouse Move is relative to screen coordinates. In other words, if it's run on a different resolution, the click might not be performed where you want it to happen. Of course, if you only made this to run on your system and configuration, you normally wouldn't have to worry, but just in case you think about distributing a similar skin / macro, this is something to consider.
Anyway, it's up to you if you want to settle on the way you do things already, or you want to explore other alternatives.