Created attachment 139340 [details] test file When creating an odt text with different font colors, I noticed that if I wanted to change a certain part of my text to a recently used color this particular color wasn't present in the recent font color menu. this causus meto use all kinds of workarounds to get the right color. Something odd is going on with the reasoning behind why a color is picked as recent font color, can this be improved?
For example in the test fil, when I continue typing in the blue text, the blue color will be added to the menu, but when I afterwards select the green text, green is added to the recent colors and the blue color has disappeared from this list.
For me the "Document color" option is sufficient enough (you have access to it via the font color icon).
Hi Dieter, the "document color" option is indeed providing me with all used colors, this will help me out for now thanks. However, the behavior of recent colors is not correct /intuitive and this is what I'd like to better with this report.
Can you describe what do you mean with "not correct / intuitive"? When I use a font colour, it is added to recent used. So I can't see a problem here.
Hi Dieter, when I use a font color on a certain sentence, and I want to use this color to "Paint" another sentence the color is not in the recent used list.
I can't confirm this with Version: 5.4.4.2 (x64) Build-ID: 2524958677847fb3bb44820e40380acbe820f960 CPU-Threads: 4; BS: Windows 6.19; UI-Render: Standard; Gebietsschema: de-DE (de_DE); Calc: group
This is what I use. Version: 6.0.1.1 (x64) Build ID: 60bfb1526849283ce2491346ed2aa51c465abfe6 CPU threads: 8; OS: Windows 6.1; UI render: default; Locale: nl-BE (nl_BE); Calc: group Maybe I should try to record this behavior to give an example.
> Maybe I should try to record this behavior to give an example. Would be useful, because I can't see a problem even in 6.1.0.0.
No repro with Version: 6.1.0.0.alpha0+ Build ID: 96d551636e9179eb6874a5156b191ef3bff0a10c CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk3
(In reply to Roeland from comment #7) > This is what I use. > > Version: 6.0.1.1 (x64) > Build ID: 60bfb1526849283ce2491346ed2aa51c465abfe6 > CPU threads: 8; OS: Windows 6.1; UI render: default; > Locale: nl-BE (nl_BE); Calc: group > > Maybe I should try to record this behavior to give an example. If possible, create and attach a screencast showing the steps. There are various free screencast software available for use, including Camstudio (Windows), Jing (Mac), Simple Screen Recorder (Linux) or screencast-o-matic.com (Web).
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20180903
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20181009