This version is out of date, covering development from v4.6.0 to v4.7.1. It is maintained here only for inbound reference links from elsewhere.

Jump to the current version of aTbRef.

A Tinderbox Reference File : Misc. User Interface Aspects : Map view interface : Smart Adornments

Smart Adornments

Smart adornments were added from v4.7.0. 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:

Notes within the current map matching the query are moved onto the adornment.
Adornments don't auto-expand to encompass notes. In some cases where there are so many matching notes that they fill the adornment, some notes may be placed around to the adorment.
Matched notes are sorted as per the adornment's sort attributes
Matched notes have their Xpos/Ypos altered
The outline order of matched notes is not affected.
Matched notes are laid out in a grid (sort) order on the adornment until the available areas is filled. Thereafter notes may be stacked on top of one another or alongside the adornment until the latter is manually resized to accommodate all matched notes.
Notes no longer matching the query remain on the adornment and if required must be removed manually (or possibly removed by another smart adornment).
Notes/containers/agents that are locked are ignored.
Other attributes are ignored. Notes 'in' other adornment will be moved (even if the original adornment's sticky flag is set).

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 OultineOrder can be looked up via its Info view (General section).

Up: Map view interface
Previous: Shaped Map notes	Next: Viewport detail in containers & agents

[Last updated: 14 Dec 2009, using v5.0]

Licensed under Creative Commons Attribution-Noncommercial-Share Alike 3.0 License
[See aTbRef CC licence Attribution/Waiver info info]