Once an attribute has been explicitly set (i.e. not via inheritance) to a non-default value, Tinderbox inheritance no longer occurs. This is deliberate, the rationale being that the user wants that note's attribute to retain the value; maintaining inheritance might cause the user-set value to be unintentionally over-written.
This can catch out the new user when prototypes are in use. One of the strengths of prototypes is that a change to the prototype is instantly imposed on all notes using that prototype - except where a note's attribute has been explicitly changed.
A very simplistic example might be where a prototype sets note $Color, e.g. 'blue'. If the user sets a note using the prototype to $Color 'green', if the prototype's $Color is then changed to 'red' all the other note's using the prototype will go red - but not the one explicitly changed to green. Many new users would expect them all to go red.
So, fine if the user wanted to take an attribute out of the inheritance stream - but what if it was a mistake. In the above scenario, if the user reset the changed note's $Color back to 'blue' would inheritance re-occur? No. That is because whilst the inherited colour is 'green', an explicitly set value is still seen as an explicitly set (i.e. non-inherited) value even if the same as the notional inherited value.
An easy way to confirm if an attribute value for a particular note is inherited or not is to view the attribute either as a Key Attribute or in the note's Get Info/Attributes tab (Cmd+Opt+i). Attributes being inherited are listed in normal weight text and those locally set in the note are shown in bold text.
How is inheritance re-enabled?
The trick is to set the attribute value to no value - something you cannot do by typing into a value input box (e.g. as in displayed key attributes). There are several approaches that can be used and which may appeal to different users' styles of work. The resetting process can be done in a number of ways:
- Use the Quickstamp Inspector. Select the note(s) and use Method 1 below.
- Use Get Info's (Cmd+Opt+i). Select the note and use Method 2 below.
- In an action or rule, using method 3 below.
- Menu 'normal' option in some pop-ups, see method 4 below.
Method 1 - Use the Inspector (works for all currently selected items)
To change a single attribute for all selected note(s):
- Open the Properties Inspector, Quickstamp tab
- Do either of:
- Choose the Attribute Group from the top pop-up and then the desired attribute from the second-pop-up.
- Use the Search box and select the desired attribute from this of matches.
- Click the left button above the value box.
To change a multiple attributes, repeat the above process for each attribute in turn.
Method 2 - Use Info view (works for current single item only)
To change a single attribute for a single note:
- Open Get Info, attributes tab (Cmd+Opt+i)
- Do either of:
- Choose the Attribute Group from the top pop-up and then the desired attribute from the second-pop-up.
- Use the Search box and select the desired attribute from this of matches.
- Select the line of the table for the desired attribute.
- Right-click and select the 'Use Inherited Value' menu item. The attribute name and value will revert from bold text to normal text.
To change a multiple attributes, repeat the above process for each attribute in turn.
Method 3 - Use Code (in an attribute or stamp)
Code can be run as a $Rule or $AgentAction or within a stamp.
To set any data-type of attribute to its inherited value:
$MyAttribute=;
Note that no quotes are used around the semicolon. The above is not the same as simply setting a string to empty or a number to zero. Why? Because the latter is simply setting that value locally and thus still blocking inheritance.
Method 4 - Use menu 'normal' options
A number of menus and pop-up /context menu have a 'normal' item at the top of the listing. For example his can be seen with menus for setting $Color or $Badge. In any of these, clicking the 'normal' option will reset the local attribute to re-inherit values.