A Tinderbox note consists of a large number of attributes. Every note possesses every attribute—both built-in (system) and user-created (user) attributes—even if not using it.
Every system attribute starts with the built-in default which becomes the default for the document for that attribute. Unless pre-configured otherwise, each attribute data has its own default value (0 for Number, 'never' for Date, 'false' for Boolean, etc.).
For user-created attributes, the default is set at creation time and will start with the data-type default unless changed by the user.
The easiest place to review all attribute values for a note is the attributes tab of the Get Info pop-over. This allows the user to select an attribute group and then scroll through a table of attribute names and values.
To edit attribute values, for the currently selected note, i.e. only one note, use any of:
- the Get Info/attributes tab. The edit mechanism is as described for the Displayed Attributes table (next bullet below).
- the note's Displayed Attributes table.
- the Quickstamp Inspector.
- any Action code via rules, edicts, stamps, agents, etc.
To edit attribute values, for selections of multiple items use any of:
- the Quickstamp Inspector.
- any Action code via rules, edicts, stamps, agents, etc.
Get Info & Displayed Attributes vs. Quickstamp vs. Actions
The first two (functionally the same table) make it easier to see/edit multiple attributes. Quickstamp show one attribute ate a time, though can still set any attribute but it has the upside of being able to act on the selection, thus one, or more notes.
Action code generally addresses a different context but can set as many attributes as required and any scope, depending on the code the user writes.
Stamps and Quickstamp have a link beyond the name as a stamp can be thought of as a pre-configured Quickstamp. Like a Quickstamp it acts on the current selection and is run once only per use (unlike a rule or edict).
See also—notes linking to here: