I look forward to your explanation about what exactly you find so difficult about it. I find it quite useful. Some of the individual dialogs are difficult to use or are a mystery (e.g. I don't know what the Plugins dialog is for at all), but all in all the Preferences tree is one of the best recent features added to OmegaT.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was talking about the way the preferences were coded. And you are right that what we have now is very nice. But it does not reflect the way preferences are handled in the code :-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I look forward to your explanation about what exactly you find so difficult about it. I find it quite useful. Some of the individual dialogs are difficult to use or are a mystery (e.g. I don't know what the Plugins dialog is for at all), but all in all the Preferences tree is one of the best recent features added to OmegaT.
https://github.com/omegat-org/omegat/pull/386/commits
I was talking about the way the preferences were coded. And you are right that what we have now is very nice. But it does not reflect the way preferences are handled in the code :-)
see also https://github.com/omegat-org/omegat/pull/2204 and the accessibility roadmap in https://github.com/zs-stpa/omegat/blob/topic/stpa/accessibility/swing-quickwins/src/docs/developer/adr/2026003.PresentationAndAccessibility.md which includes centralizing the at least the editor presentation options all in one place which was previously the colours settings table.