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 no longer updates but it 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:
- grid (default). Aliases are arranged in a grid pattern, left-right/top-bottom in sibling order.
- row. (From v8.7.0) Aliases are arranged in a single row, left-right in sibling order.
- column. (From v8.7.0) Aliases are arranged in a single column, top-bottom in sibling order.
- box. Aliases are arranged in a an open box (square) arrangement, clock-wise in sibling order from top-left.
- none. Auto-layout is suspended, the user is free to arrange the items within the agent containers as they would any other map. Whilst in this freeform mode the normal Map view Cleanup pop-up menu items may also be used. In "none" mode Tinderbox adds new aliases to the agent map by the logic used for a normal map so it should avoid overlapping/hidden icons, etc.
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.
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.
From v8.7.1, if an adornment is added inside an agent, the agent’s $CleanupAction is set to "none".