Created attachment 150697 [details]
writer -> menubar -> View -> Hide Whitespace
all other toggles boxes are activated to show x only hide whitespace is active when something is hidden.
also the guideline say that checkboxes should be activated when something is shown not hidden.
Andreas, I hope you agree that "Show Whitespace" should be activated by default.
HIG is "Turning on an item in the menu should always enable the option. Negative options create a double negative which can be confusing. For example, use 'Show hidden files' instead of 'Hide shown files'."
Of course, the default needs to get changed too.
Removing UX, and it's an easyhack.
(In reply to Dieter Praas from comment #1)
> Andreas, I hope you agree that "Show Whitespace" should be activated by
for sure as most other items are activated by default.
At the moment I am not very familiar with the LO codebase. Just a short question: does this change only affect the sw folder or are there any other positions to consider?
Hm, maybe it's a bit more work...
(not sure all are relevant as some files are for pdf export)
Thank you very much! I have already seen all these files and I am afraid that I break something in another part of LO. At the moment my code works, but I have to do some other work, until I can submit a patch. Busy times ...
I have some small questions about this change:
- Should there be changed the whole backend including function names, function calls, variables etc. or should there just changed the ui behaviour?
- How I handle the translation of the new label? Unfortenatley, I did not find any good documentation about adding translation to the code base
(In reply to Andreas Heinisch from comment #7)
> I have some small questions about this change:
> - Should there be changed the whole backend including function names,
> function calls, variables etc. or should there just changed the ui behaviour?
> - How I handle the translation of the new label? Unfortenatley, I did not
> find any good documentation about adding translation to the code base
Code is up to the developer, if you are unsure the IRC channel or mailing list is the right place to ask. I would keep it simple.
If you change strings in the hrc files (NC_) it goes automatically to the localization. No need to trigger anything there.