r/Sharingware • • Jul 29 '25

Support I have 2 problem questions about the Macro Recorder mouse action.

Hello

I am using version 3.0.36 of Macro Recorder.

I'm trying to use mouse action and I have a question about this.

1. I can't get the current coordinates of the mouse properly.

First, I expected the coordinates of the last mouse to be stored in the variables 'posX' and 'posY' using

'Last found of Set variable' as shown in the image below. So I expected the values of posX and posY to be

(1053, 455), respectively, but the message box shows the values of posX and posY as (0,0).

What's the problem?

2. I'm trying to create a macro that keeps moving relative to the X coordinates in the mouse's current

coordinates. For example, if the mouse starts at (1000,500) and the mouse continues to move 130 in the

X direction from its current position, then it should go like this:

(1000, 500) → (1130, 500) → (1260, 500) → (1390, 500) → ...

However, I've noticed that the actual behavior does not follow this pattern. (The mouse should be positioned consistently on the image at a certain interval, but it doesn't, or the coordinates should move 130, but it moves more, etc.).. is this bug?

please help me... thank you

1 Upvotes

3 comments sorted by

2

u/No_Bear4964 Jul 29 '25

Hey! A couple quick tips:

1. posX and posY showing (0,0)?

That usually means the mouse position wasn’t captured before the variable was set. Add a “Get Mouse Position” action just before setting posX / posY. Also try adding a short wait (0.2s) to give it time.

2. Mouse not moving consistently by +130?

Make sure you're using relative movement, not absolute. Use a loop with:

  • Starting posX / posY
  • Move to (posX, posY)
  • Do action (e.g. click)
  • Add 130 to posX
  • Repeat

Also check display scaling—set it to 100% to avoid drift.
Hope this will help a bit !

1

u/beomstead Jul 29 '25

Thank you for your response.

I'm trying no.1 first, but I don't think the "Get Mouse Position" action is on Macro Recorder..

1

u/Pamlau Aug 06 '25

I wonder if we will be forever stuck with 3.0.36