Mouse Pointer doubling - confusing to debug.

[WWO]

It seems that actions occur before the mouse pointer catches up. 

It seems that the mouse is moved to X:Y, then the time delay applied, then the action effected. The mouse pointer is displayed at the new location after the action is effected. Am I understanding that / things correctly?

Even if I move the mouse, then move it one more pixel, the mouse pointer is still showing at the old location, prior to the first move, as well as at the new location.

How do I delay / keep the mouse pointer in sync with the currently executing line?

[Loops are getting out of sync. I'm trying to figure out which line needs additional time allowed to give things time to catch up, but with duplicate mouse pointers on screen at the same time, I'm going bug-eyed trying to discern which line I need to change.]

[Steve]

Jul 26, 2020 20:57:07 GMT WWO said:

[Loops are getting out of sync. I'm trying to figure out which line needs additional time allowed to give things time to catch up, but with duplicate mouse pointers on screen at the same time, I'm going bug-eyed trying to discern which line I need to change.]

Can you expand on this? duplicate mouse pointers?

This might help:

1 | 100 | 200 | 1000 | Mouse Movement
2 | RUN ACTION | MESSAGE PROMPT | Hello
3 | 200 | 400 | 2000 | Mouse Movement
4 | RUN ACTION | MESSAGE PROMPT | Goodbye
5 | 400 | 600 | 3000 | Mouse Movement
Line 1 reads like this:  1 | 100 | 200 | 1000 | Mouse Movement

1 = The number of the line. In MMM this helps to visualize and sort the macro and also is a reference for GOTO actions that reference a line number value.
100 = The mouse X value
200 = The mouse Y value
1000 = Execute this line with a 1 second delay. Meaning to wait 1 second before running this line.
Mouse Movement = Move the mouse to the X Y.


The whole macro reads like this:
1 - Move the mouse to 100/200 pos after 1 second
2 - message prompt the word hello
3 - Move the mouse to 200/400 pos after 2 seconds
4 - message prompt the word goodbye
5 - Move the mouse to 400/600 pos after 3 seconds

[WWO]

Here is an example:

Attachments:

[Steve]

Thanks for your example.
Does this behavior occur outside of the game/app your in?

[WWO]

I'll have to see and get back to you.

If I never do, the answer is no. (i.e. issue specific to the WebGL app, so it's the app's problem, not mmm.)

When I get near it next, I'll try to remember to add some timeout (# | X | X | 3000 | Mouse Movement), see if it's just a matter of the app catching up / 'network' lag.

I'm also starting to wonder if it isn't video card / driver related - but I can't easily test that. [Only the one windows computer.]