When to record mouse moves in Macro by Zaweba

By default, Macro by Zaweba records your clicks but not the journey the mouse makes between them. Tick Record mouse moves before recording and it keeps every movement as well, sampled every 15 milliseconds. That gives a faithful copy of the path, at the cost of a much longer macro.

The default is deliberate. For almost every everyday job, where you click a field, type, click a button and move on, the path in between doesn't matter. Only the clicks do. Leaving movement out keeps the step list short and readable.

What gets recorded either way

Even with mouse moves off, Macro records a great deal: clicks, double-clicks, drags with their path, scrolling in both directions, keystrokes and the time between them. Drags are worth calling out, because people sometimes assume they need mouse moves for them. They don't. A drag keeps its path whether or not the option is ticked.

So the option only adds the free movement of the pointer when no button is held down.

When the path does matter

Some programs react to the pointer simply passing over things. A menu that opens when you hover, a tooltip you need to appear before clicking, or a web page where a panel slides out under the mouse all depend on movement. If replaying the macro skips straight to the click, the menu may never open and the click lands on nothing.

Testers sometimes want an exact copy of how a person moved through a screen, hover effects and all. Some games also respond to movement. In those cases, tick Record mouse moves.

The cost of recording movement

Sampling every 15 ms adds up quickly. A few seconds of moving the mouse around becomes hundreds of small Move steps. The macro is longer to read, harder to edit, and you have more to scroll past when you want to fix one click.

There is a quieter cost too. The step editor turns a recording into plain-English steps such as Click left at 512, 300 and Type "hello". That readability is the main reason to use Macro rather than a scripting tool. A wall of Move steps buries the clicks and typing you actually care about.

A middle way

If only one moment in a long job needs a hover, there is a neater route than recording every movement. Record the job with mouse moves off. Then open the step editor and add a single Move step just before the click that needs the hover, with a short Wait after it to let the menu open. You can pick the position by pointing at the spot: the editor reads the cursor after three seconds.

You can also record just the awkward part separately with Record and insert into this macro, ticking mouse moves only for that short recording.

Habits that keep macros short

Don't tick mouse moves by habit. For form filling, menus you click open and ordinary buttons, clicks alone are enough and the macro stays clear.

Don't wander. If you do record movement, move the mouse purposefully. Every idle circle you draw while thinking is replayed faithfully, and at slow speeds it wastes time.

Remember that faster replay speeds shorten the waits between steps. A hover that needed a moment at normal speed may not have time to work at 10x. If a movement-dependent macro misbehaves, slow it down first.

And if windows move between runs, consider positions relative to the active window, so clicks are measured from the window's corner rather than the screen's.