as per subject
nice easy hack!
so corrected the summary. It was highly inaccurate .. ;)
Would suggest it also have a menu bar entry and it be able to reset all paragraph, character and direct formatting options.
Tagging this for the creation of the necessary uno command, so that i can be included in the menu bar and suggest using Ctrl + Alt + M as the shortcut, as its not used anywhere in LO.
Migrating Whiteboard tags to Keywords:(needDevEval -> needsDevEval)
(Harmonize spelling of term)
@Cor: Is this for applying default paragraph style as there is already a shortcut for that (Ctrl+Shift+0) and its listed in the styles menu. Maybe we can add a shortcut to set default character style as well, maybe ctrl+shift+alt+0.
Please keep in mind that average users struggle to understand styles and have even more problems to follow the difference between paragraph and character styles plus direct formatting. If there are different ways to get rid of a styling it adds confusion.
Also I'm against complex shortcuts with three modifiers keys. If the user wants to configure this cumbersome finger posture, I'm sorry for her. But when we deliver software with this complexity there is something wrong with our usability (26 letters by 6 variants makes it 156 different shortcuts to remember, at worst).
Sounds like a WONTFIX to me.
In theory the user has to do several steps to have a document without any formatting: Ctrl+m for direct formatting, Ctrl+0 for default paragraph style, go to the styles sidebar and assign default character style, go through other styles like lists and tables.
These are many steps. But how often an average user has to do this? I doubt a own shortcut is justifiable for this.
If a new command will be introduced, then I want a super reset command that also set all other styles back to a default/unstyled state. Not only paragraph and character styles.
(In reply to Thomas Lendo from comment #8)
> If a new command will be introduced, then I want a super reset command that
> also set all other styles back to a default/unstyled state.
You mean 'default/unmodified' I guess.
> Not only paragraph and character styles.
Fine for me. I'm not hindered by short cuts I do not use.
The behavior of Ctrl+M is fine and has been discussed before the latest change (few years back). But now leaves the gap for the behavior that this issue is about.
There seems to be some agreement on this request and the shortcut also sounds like a good idea (if we need a shortcut). So removing UX.
@heiko: easy hackeble?
(In reply to Cor Nouws from comment #11)
> @heiko: easy hackeble?
Yes. Would follow the clear formatting command and copycat this plus the character style cleaning function. Though have no code pointers out of the box.
Dear Cor Nouws,
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
after all these years, I do not really understand the fun/use of the idea.
(And I did not write it in the comment. Stupid me :) )