Facilitator only?
Will config file do? I'm guessing UI is needed?
Buttons only or word list as well?

Yes, config file fine.

Word list and buttons. But, for initial release, word list is most important.

Phase Two:
Menu driven.

Have used Tapir settings page and added Text, bg, sel text & sel bg colour buttons. Realise this is a bit messy.

Works for me.

If easy, then could options be added to a menu (i.e. clicking on the Dkey icon in top left of window-bar to get at).

If not, config file and on-screen keyboard access (i.e. as-is) is OK for now and add to ticket for future version.

Does this mean you do not particularly want any of the options on buttons as they are now? We're running out of buttons to use without getting a bit more complex. MInd you we'll need the extra logic to handle re-assignable keys as any number could be used

For now, options in menu is fine if this is easier (or, in fact, just in config file). Could ditch settings button entirely for now and add it as a ticket for later version. (my user wouldn't change options themselves, and, in fact having them on buttons only makes sense for scanning or for keyboard-keypad input anyway..)

Actually, not config file for font etc!!!

OK, I was thinking ahead to scanning. Lets see how easy menue are and leave config file a 'hidden' detail. I was thinking of losing the title bar and window furniture completely but seems it will be needed after all

I've had a day of nothing working properly so for now click on the window between buttons to toggle between settings and main.
I know this is horrid but I've run out of time.