Skip to content

Favourites, and copying a button

Added in 1.3.0.

Two small things that go together: a set that is always at the top, and a way to take a button someone else wrote and make it your own.

Favourites

Star a button and it joins your Favourites set, pinned to the top of the panel. Star it again and it leaves. The set ignores the per-connection filter entirely, which is the point: the six buttons you use on everything follow you from a switch to a PBX to a Linux box without being named on all three connections.

Starring copies the button in rather than linking to it. Edit the original afterwards and your favourite is unchanged, and the other way round.

Sharing your Favourites works

Exporting the Favourites set and publishing it is fine, and it does the sensible thing. Favourites has a fixed id, but the app renumbers set ids on import, so the person who downloads it gets an ordinary set called Favourites sitting alongside their own. It does not merge into their favourites and it does not overwrite anything.

Copying a button

Copy any button into any set, under a new name. This is how you take one of the 2,714 buttons that ship with the app and adjust it for your kit — your interface naming, your VLAN numbers, the extra check your change process wants.

The copy is a snapshot, not a link. Once it is made the two are independent: editing either leaves the other alone, and a later app release that revises the shipped button will not touch yours.

Why copy rather than edit in place

You can edit a shipped button directly — nothing stops you, and it is your install. But a copy keeps the original around to compare against and to fall back to, and it means the set you eventually publish to the exchange is recognisably yours rather than a shipped set with three lines changed in it.

What a copy carries

  • Every step, its input fields, its placeholders and its confirmation gate, exactly as they were at the moment you copied.
  • A note of where it came from, kept for your reference. It is a record, not a connection — nothing resolves it and nothing depends on it, so it stays harmless even after the button it names is gone.
  • No credentials and no global variable values. A button references a global by name; the value lives in your own global variables file and never travels with a copy or an export.