This version is out of date, covering development from v6.0.0 to v6.6.5. It is maintained here only for inbound reference links from elsewhere. It is no longer actively updated.

Jump to the current version of aTbRef

TinderboxSix Icon

Smart Adornments

Any adornment is made into a smart adornment simply by giving it a query (stored in $AgentQuery) using agent query syntax - i.e. action code. Importantly, the scope of the query in a smart adornment is always the current map, the map on which the adornment lies. All other notes are automatically out of scope. The following facts apply:

If a smart adornment is made larger (manually or via an action) and in doing so overlaps non-matching notes then the latter are displaced to one side so as to remain outside the adornment. Re-sizing a normal adornment the notes would simply lie inside the new adornment boundary.

Smart adornments cannot be used to move or act on notes outside the current map. So, for instance, it can not move a note into a (container's) subordinate map or promote it to a parent map, or indeed pull it from another map. Put another way, it can only act on its siblings.

In the case of conflict, were two or more smart adornments match a note, the adornment with the lowest $OutlineOrder will match the note. An adornment's $OutlineOrder can be looked up via its Info view (General section).

A Tinderbox Reference File : Windows : Document Window : View pane : Map view : Smart Adornments