Default Note Text Color

In attempting to do X last night I inadvertently accomplished Y (unwanted). Text is now green; I can go in and change it to black for that note but the next new note I create the text is automatically back to green.

‘Normal’ now automatically switches to ‘custom’: I have lost my ‘normal’ option if that is relevant. The “0” in the color list is also now this green… can’t remember what it was before.

How do I make the change from green text back to black “stick” (apply?) for all new notes created from now on out?

TIA

Ok, then general point here is attribute inheritance.

Finer detail. The moment you create $Text, it is styled with whatever style you set. So once you set some text to , for instance green, all text after that is green. The easiest way to reset this is to select all $Text, or the affected part, and use menu FormatStyleStandard Font. This should reset everything.

The takeaway, all $Text is styled.

Hmmm… Format > Style > Standard Font seems to be from the dropdown. This still gives me green text.

It’s green at the Inspector “level” so, I’m guessing, green is the new standard (?). So in the inspector, I open the color drop down, I choose “black” thinking it will replace the green, but the green keeps coming back (see earlier screen shots).

Add $TextColor as a Displayed Attributes for the note. It will show the actual colour set. What value do you see?

The document default for a new TBX is actually set via the Settings:Text tab:

To prove the point, here is the same file’s System Inspector showing $TextColor and indicating is it set as a preference (i.e. dialog above):

I don’t know why black is reported as #000000. Though both resolve to the same colour, named colours may be changed if a new colour scheme is applied. But the latter isn’t likely a factor here.

So walking back up the inheritance chain:

  • Select all $Text and FormatStyleStandard Font. This should apply the notes $TextFont, $TextFontSize and $TextColor.
  • View the note’s $TextColor.
  • If using a prototype, view the prototype’s $TextColor
  • View the document’s $TextColor in the Inspector.

Which of these is green or a hex value (#-prefixed 6-figure number) equating to a green colour.?

This is what I see:

Document Settings corrected it. Thank you.

1 Like

It occurs to me that, one other way the observed colour could go wrong is if named colour ‘black’

Hmm, it seems I don’t have an aTbRef article on ‘named’ colours but also see Colors tab, and Colour Scheme Files. A bot of a rabbit hole, but each colour scheme (or the current TBX) can define the displayed colour of a ‘named’ colour (see a Chart of Tinderbox's defined colours), where ‘defined’ equates to ‘name’ colour. So, on reflection lots of scope for confusion.

For example, in the same file with the same content, changing the colo(u)r scheme can literally alter colours you experience:

Same document but with colour scheme ‘London’. This might be an old scheme on my system only, but look at the green [sic] note:

So, it’s not impossible that the colour called ‘black’ might actually be rendrred on screen as green.

Thanks for confirming you found a fix and I’m glad you have.

My answer above might also explain another quick of ‘named’ colours in Tinderbox. :slight_smile: