By default, new Tinderbox files are created with 29 predefined 'named' colours:
- 10 shades of grey with numerical names
0through9. - 19 colours with colour names:
black,blue,bright blue,bright green,bright red,cool gray,cool gray dark,cyan,gray,green,magenta,orange,poppy,red,violet,warm gray,warm gray dark,white, andyellow.- Note that 'gray' appears to be added by the default colour scheme ('Mordern') and is not defined by the core Tinderbox named colour set ('colors.xml').
Names add since Tinderbox launch
Most of the basic named colours were added in v1.0.0. Later additions:
- v2.1.0: 'poppy'
- v6.0.0: 'violet' and '0' through '9'
Case-sensitive names
When used in code, colour names are case-sensitive - 'blue' and 'Blue' are treated as separate colours. Tinderbox-defined named are always lowercase-only.
What do the named colours look like?
The named colours actual displayed colour can be seen here, displayed using the built-in 'Tinderbox 7' scheme which does not alter original colour values and includes all the 29 post-v6 defined named colours. That scheme is no longer the default scheme for new TBXs but does give colours truest to the names used. The image used (a screen grab of a map view in the aTbRef source TBX) includes all the built-in shade variants of the named colours.
These names are used in pop-up lists in the Colors Inspector and in other Inspector panes for Color-type attributes. These pop-ups show a small circle filled with the rendered value of that colour. There is no preview of colour shade variations except by setting that variant as a colour value.
Despite the implication of their name, these colours can have their actual colour value set to something else. So whilst named colour 'red' may logically be some shade of red, there is nothing to stop the user setting a different red value—or any valid colour value—for that named colour. See below for setting/altering named colour values.
This seems odd at first sight. But the method of a fixed name but varying values allows for Tinderbox's method of implementing different colour schemes. by simply adding a files that redefines colour values (see more).
Do all TBXs have the same named colours?
Named colours seen in a Tinderbox file (TBX) apply only to the current TBX document. However, as all TBXs are created with a default set of named colours, these are generally consistent across all (a given users) TBXs.
Can a different default set of named colours be used?
In short: No. However, once a document is created, a saved custom colour scheme can be applied.
[Not recommended for non-expert users] Those wanting a customised set of colours available by default in all their TBXs should investigate use of Configuration files, specifically a colors.xml file; such changes will affect all TBXs created after the custom colors.xml file has been created and the app re-started. This method does not allow the user to customise the colour of 'normal' either at app or TBX level.
User defined named colours
It is possible to add new, user-defined, named colours via the Inspector, see below.
Adding, deleting or amending named colour values
This is all done via the Colors Inspector, which see. The actual value of any defined named colour is set/altered via the Inspector.
New, user-defined colours may be added. this change is restricted to the current TBX document.
User defined or default built-in named colours can be deleted. There is no undo for this. To re-assert a deleted built-in colour it must either be manually redefined or apply a suitable built-in colour scheme. Be aware the latter re-asserts all its defined colour, so the manual method is likely better for a single colour needing attention.
Reverting to base defaults after experimenting with colour schemes
There is no 'reset' for colours but applying the 'Tinderbox 7' colour scheme is the best way to revert to colours that reflect their actual name. If wanting to rest to 'as new' start for post v8 TBXs, use 'Modern'.
See also—notes linking to here: