Martin Vermeer wrote: > > Probably. Why not. But how to save the colour into the doc file? > Having the colours named has value. What If I extend the list of > available colours to include more rgb.txt entries? Note also that > blue and red should probably go as they are too dark for background.
Why not define logical colours "branch1", "branch2" etc which you save in the doc. Adding them to the LColor.h enum and LColor.C array of all such colours will automagically allow the user to specify their on-screen representation from the preferences dialog. -- Angus
