Description: Direct formatting combined with styles confusion Steps to Reproduce: 1. Open the attached file 2. Be a Benjamin -> Disable bold using direct formatting 3. Go to Sidebar -> Character style 4. Right click example -> Modify 5. Change the font to Italic/Bold & Press OK 6. Notice the Bold Formatting being disabled 7. Select ABCDEF & enable BOLD (CTRL+B) 8. Go to Sidedebar -> Character style 9. Right click example -> Modify 10. Change the font Regular & Press OK The easy way out the mixture; select a different style and back.. but not a 'nice' solution. Font is still bold.. Menu Style -> Strong Emphasis (really didn't consider it a font style (managed in the sidedeck; more a 'quick formatting' setting. Again.. A benjamin speaking.. not everybody reads the manual :-). Or the license agreement when installing software.. Actual Results: Styles mixed with direct formatting can be a source of trouble and confusion Expected Results: Style causing highlighting of direct formatting buttons.. bit of tricky area. Options: * Block direct formatting of text formatting with styles (however default paragraph style is also a style...) * Modify the icons of the formatting toolbar if a character style/paragraph is involved (the default character can't be modified; so no issue there.. However the default paragraph style shouldn't be editable in this case either. It's the direct formatting style :-). Or at least highlighting, font & font effects should be disabled) *... Other suggestions Reproducible: Always User Profile Reset: No Additional Info: Version: 7.0.0.0.alpha1+ (x64) Build ID: f9790da286f2d2fa47f1748f8cfa6172c6622ca3 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win; Locale: de-CH (nl_NL); UI: en-US Calc: CL
Created attachment 160951 [details] Example file
Probably NOT A BUG.. but throw it in anyhow..
This is a FAQ. For example discussed here https://wiki.documentfoundation.org/Design/Meetings/2018-08-01 * Clear styles ... + problems will occur with nested styles and when a character style is combined with direct formatting + users have to take care of putting DF on top of character styles; it's not the supposed workflow + we could think about disabling DF when a character style is set (Stuart) => there are more side effects and negative consequences than benefits = WF/WFM Point is, users have to learn to use a complex software. Mastering means to understand the details. If we disable DF is any CS is set and vice versa, Stuart's idea from back then, Benjamin users likely have no clue why this happens and Eve users call it a regression. => WF