Map view allows optional 'flags' to assist in qualitative analysis and coding. One common Tinderbox task is qualitative analysis of existing materials, such as letters, surveys, diaries, and personal papers. An important preliminary step in this work is coding—identifying occurrences of special interest for the study. For example, if we were analysing a collection of nineteenth-century diaries to study what people recorded about food and drink, we might want to code where the food was consumed. We might mark every passage that discussed eating at home with the code P1, eating at the residence of another family member with the code P2, eating at a pub with P3, and so forth. We might also note places where money is discussed: C1 might indicate that the writer paid for their meal, C2 that someone else explicitly paid for the writer's meal, and so forth.
Flags offer a convenient and flexible way to foreground selected codes in map view. Flags are defined via $Flags, a List-type attribute. When not empty, small "flags" are displayed above the note in map view. (N.B. flags do not appear in other views). Note that as $Flags is a List-type attribute, actions can add new flags with "+" or remove flags with "-". Adding a flag to a note that already possesses that flag has no effect.
$Flags is an intrinsic attribute; it is not inherited from prototypes and an alias may have different flags from its original note.
For simple coding tasks, using $Badge may be adequate. Flags provide a wider range of visual cues, and new flags can be improvised quickly when coding needs change.
Flags are described using a concise textual shorthand, and are illustrated in the screen-grab. (A visual flag editor is planned for the future.). Whilst it is generally easier to use named Tinderbox colours, hexadecimal values can be used to define flag colours as in the first example below. Possible design variations . Note the possibility of combining styles:
- Single solid colour. A red flag:
- Horizontal stripes. List the stripe colours separated by hyphens:
- Vertical stripes. List the stripe colours separated by the vertical bar character:
- Diagonal stripes. List the stripe colours separated by the '/' symbol:
- Chequered flag. List the two colours separated by the '$' symbol:
- Cross symbol. List the cross colour, a '+' sign and then background colours:
- Saltire symbol. List the cross colour, an asterisk '*' and then background colours:
- Diagonal line. The '%' sign adds a diagonal line:
- Chevron. The '>' symbol adds a chevron:
- Pall. The '}' character adds a pall:
- Pall and Chevron. The pall and chevron work together:
- Text caption. A period '.' adds a short textual annotation (1-3 characters) on top of any other colour/pattern:
BZ.yellow$light green. The characters
>*+.$%}are treated as literal characters if they are used the first three characters of flag code using the period marker, so
+.reddraws a plus sign on a red flag.
- Text colour. Though text is normally white, a colour may be specified:
black:C.lighter blue, or
- The text may be an emoji:
Multiple Flags and icon width
The default map icon will display up to 4 flags, or the first four listed flags if more. By dragging the note wider, all flags can be displayed (as illustrated).
As $Flags is a Set-type attribute, if defining multiple flags for a note, use a semicolon between each flag's code, e.g.
Colours and Tinderbox Colour Schemes
As Tinderbox colour schemes files allow a named colour to be any value, it may be safer to use use colour values (e.g.
#00ff00) rather than named colours (e.g.
red) if you are not using the Tinderbox v7 standard scheme or switching between schemes.