WWO
Full Member
Posts: 21
|
Post by WWO on Apr 27, 2022 3:44:04 GMT
No doubt this is front and center obvious somewhere, but my search fu seems to be broken ... Ignoring 'run action', mmm lines seem to be of the form: # | x | y | t | action where: | = delimiter # = line number x = x coordinate y = y coordinate t = time action = action What is t? I think I've seen it as: wait time t; move the mouse to coordinates x, y; perform action However, my timing always seems to be off / mentally tracking line and what I'm seeing on screen seems ... backwards. (For lack of a better word.) I've ended up coding things as: 1 | 100 | 200 | 100 | Mouse movement 2 | X | X | 100 Left Click 3 | X | X | 300 | Mouse Movement just to be able to mentally track each (triplet) step with (optional) before / after delays so my eyes can follow things / steps. So what is 't' (herein), and what is the right way to think about / read such lines? [Sorry, no doubt this should be obvious, but I'm just not getting it / missing something - flow across several mouse moves and clicks ... just doesn't.] Links to the right place my current search fu can't seem to grasp, welcome. * Other threads describe x, y, and action, but skip over the meaning of the number, part. e.g. '15' in minimousemacro.proboards.com/thread/228/question-syntax, so I've asked herein. |
|
|
|
Post by cyberchipz on Apr 27, 2022 20:05:43 GMT
No doubt this is front and center obvious somewhere, but my search fu seems to be broken ... Ignoring 'run action', mmm lines seem to be of the form: # | x | y | t | action where: | = delimiter # = line number x = x coordinate y = y coordinate t = time action = action What is t? T is the time in Millseconds to perform the click, IOW in 100 milliseconds press and release the mouse button. This is the time BEFORE the action takes place; unless someone corrects me on this. ;-) It was originally written for mouse clicks to have a seperate mouse press, and release time, two lines of code; shorted now to Left Click. When you "record" a macro, and make mouse clicks, which I haven't done in a while; it records the mouse clicks as two actions. (since I haven't used in a while, I forget what they are) I use Left or Right Click... but, when recording, it records the time before you press the mouse button down, how long you hold it down before you release, so, the recording is a series of records of whatever you do... the time before each action, and the action itself. Mousemovement is always an added line, never recorded, it has no trigger; at least I've never seen it trigger in a recording. ;-)I think I've seen it as: wait time t; move the mouse to coordinates x, y; perform action However, my timing always seems to be off / mentally tracking line and what I'm seeing on screen seems ... backwards. (For lack of a better word.) So what is 't' (herein), and what is the right way to thing about / read such lines? Delay the action for this many millseconds; then perform the action. Of course, the code will take a small amount of time to execute; you have no control over that; it depends on many factors... what is going on in the background of your computer; and such.[Sorry, no doubt this should be obvious, but I'm just not getting it / missing something - flow across several mouse moves and clicks ... just doesn't.] Links to the right place my current search fu can't seem to grasp, welcome. * Other threads describe x, y, and action, but skip over the meaning of the number, part. e.g. '15' in minimousemacro.proboards.com/thread/228/question-syntax, so I've asked herein. Of course the other one is mousemovement; which basically waits the alloted time then moves the mouse; great for seeing where the click is taking place. It usually leaves a little trail of arrows (or whatever you use for your pointer) everywhere there is a mouse movement; I use it to confirm that the mouse is clicking in the right place; if this location due to 3rd party code is subject to change. Which makes the mouse click fail. Hope this helps. |
|
WWO
Full Member
Posts: 21
|
Post by WWO on Apr 27, 2022 22:04:45 GMT
<sigh> THANK YOU! [My bad, I knew it was milliseconds, should have said that.] So ... t means different things on different actions. On mouse clicks it is the 'duration' of the click. On other things it is the delay (pause) before the (mouse) movement. No wonder I've been ... spinning 'round. I just expected every line to be <x> <y> <delay> <action>, and you note that that is not the case. Thank you, muchly. |
|
|
|
Post by cyberchipz on Apr 28, 2022 15:11:09 GMT
At least that's my understanding. In reality it only makes a difference for background activities; the only issues I have, where I raise the amount of time is when I click something that requires the background screen to change; like when the screen will move to another page completely. If it's on the internet; that time can vary; if it is an app; you will get an idea of how long that takes, I usually give that 300 to 500 milliseconds.. For website page changes; I have to capture a pixel that will disappear when the page changes; and I watch for that activity. When the pixel disappears, the page has changed; I give it a little more time to settle down; and then I can take an action. Most of the time, I am overly cautious; and have to include routines, when dealing with a website, for lag. These can include counters that will set a maximum time for the page to change; I've seen lag, in some games last up to a minute. If you know what will appear on the next page, on a website; you can look for that image to appear; then when it finds that image; you "Know" the page has changed. Otherwise, handling lag is the worst issue. But, one that seldom appears inconsistently when dealing with applications or computer programs. Only online websites have to deal with lag. Otherwise, click time can be as low as 30ms for a page change... except for websites.
|
|
WWO
Full Member
Posts: 21
|
Post by WWO on Apr 28, 2022 16:26:48 GMT
Yep. Been there, and experiencing, that. Thanks for your comments. Appreciated.
|
|
|
|
Post by Steve on Apr 28, 2022 20:00:36 GMT
<sigh> THANK YOU! [My bad, I knew it was milliseconds, should have said that.] So ... t means different things on different actions. On mouse clicks it is the 'duration' of the click. On other things it is the delay (pause) before the (mouse) movement. No wonder I've been ... spinning 'round. I just expected every line to be <x> <y> <delay> <action>, and you note that that is not the case. Thank you, muchly. Hi WWO The 'T' is always time in milliseconds prior to the event running. A wait then run the keyboard entry. The 'T' is only a wait for keyboard entries. Let me break this down... 1 | 607 | 314 | 10 | Mouse Movement 2 | 608 | 309 | 134 | Left Click Line number | mouse X pos | mouse y pos | time to wait in milliseconds prior to execution | keyboard event t means different things on different actions. On mouse clicks it is the 'duration' of the click. On other things it is the delay (pause) before the (mouse) movement. No this is a bit off. It works the same on Left Click, mouse movement, and keyboard presses. It's the same for all. It is simply the time to wait post execution of the previous line. Let me break that down... 3 | 1539 | 580 | 100 | Left Click Down 4 | 1539 | 580 | 500 | Left Click Release Line 3 executes a left click down 100 ms after line 2 ends. Line 4 executes a left click release 500 ms after line 3 ends.
Hope this helps.
|
|
