Tinderbox v9 Icon

Re-arrangeable Agent Maps

By default, a map of an agent cannot be re-arranged. This is because at each agent update cycle, the aliases are refreshed adding/deleting aliases as their originals match, or cease to match, the agent query.

However, if the agent is turned off ($AgentPriority or Action Inspector Query sub-tab or Get Info agent tab.) if is possible to then manipulate the map's contents. When 'off' the agents ceases updating but it still retains its contents from the last active agent cycle. If the agent is turned on again, the map is re-arranged to the normal agent-organised layout.

Maps within an active agent can be rearranged by the user, which attempts to get around the above problem. Note that this flexibility applies to the agent-created aliases on the map; the user cannot add additional items. If the user deletes an alias it will be re-created next agent cycle. Also, like normal aliases, it is not possible for the agent's aliases to contain other notes so no nesting is possible.

The feature is controlled by the agent's $CleanupAction. In the default mode, the agent's contents in map view will be organised in a grid, as was previously the case (see above); the order of items in the grid being set again, as before, via the sort attributes for the agent container. A number of cleanup layouts are supported (seen in the Cleanup Action pop-up list), with items being ordered via outline order ($OutlineOrder) unless the parent container has no sort ($Sort) set:

Changing the Clean-up order

By default, items are arranged ordered via outline order ($OutlineOrder) unless the parent container has no sort ($Sort) set. If a sort is set, the items are listed in ascending sort order. This will vary by data type e.g. number-type: lowest first, date-type: earliest first). This can be reversed by setting the $SortBackward attribute or ticking the 'reverse' box on the Sort Inspector.


User-added adornments are allowed in agent maps—an exception to the only aliases forming the child objects of an agent. If the agent sort is enabled, i.e. $CleanupAction is "grid", this trumps the effect of smart adornments; smart adornments themselves ignore $CleanupAction completely. Adornments can be dragged or pasted into agent maps.

If an adornment is added inside an agent, the agent's $CleanupAction is set to "none".


Agents do not force a default cleanup on file load. Thus agent maps using "none" correctly maintain their layout across different sessions.

Should the agent be re-enabled, the custom icon positions will be lost as the agent rearranges the icons.

Regardless of whether an agent is enabled it is always possible to link to/from aliases on the map of the agent's contents.