Synchronizer

On the Synchronizer screen you pick one running profile under Master profile and tick one or more running ones under Target profiles. All of them have to be open already, because the windows themselves are what is being driven.

Mirroring is only useful if you can watch it, so the windows you work in can be laid on one grid across the display your cursor is on. Each running profile takes one cell, and a profile started without a window is left out.

Five kinds of action leave the master window. Everything else stays where you did it.

• Clicks

  The element under the pointer, plus where inside the window you hit.

• Typing

  Every letter and pasted text: the target types the letters itself, with keys, at its own pace, and pastes a paste with the same key combination.

• Scrolling

  The distance you scrolled with the wheel or a finger.

• Keys

  Enter, Tab, Backspace, Delete, Escape, the arrows, Home, End, Page Up, Page Down and keys pressed outside a field.

• Address changes

  A typed address and a step back or forward; a target follows a link with its own click. Blank and error pages are never forwarded.

A captured click is not a pixel. It carries a short path down to the element you hit and the point you hit as two fractions of the window.

In each target the path is tried first, the wheel turns until the element is in view and the mouse moves to it before it is clicked. That road survives a window of another size.

• The path finds the element

  It is scrolled into view and clicked, which is the case that survives different window sizes.

• The path finds nothing

  The fractions take over, resolved against that window's own width and height rather than the master's.

• The target just navigated

  It simply misses the action. A held action would land on a page you had already left.

A profile usually has more than one tab open. On ARMANOS Browser the pages themselves are asked which one is on screen, so the tab in front of you is the one that leads.

That answer is taken once, when you press Start syncing, and held for the whole session. On the built-in engine nothing is asked: the profile window that last had focus leads, and the start page window is taken only when there is no other.

A synchronizer is for work you are doing anyway, once, with your eyes on it: the same banner in eight accounts, the same form, the same checkout.

A flow is for work you will do again. It costs more to write and far less to repeat, and it can be put on a schedule.

The recording listeners are taken off the master's page and their queue is deleted. Both lived apart from the site's own scripts, in a separate part of the page kept for the program.

Nothing about the session is written to disk. That is the honest half of the trade: what leaves no trace cannot be replayed tomorrow.