Regarding the new area fill options:
A unique characteristic of the colors tab is that only custom colors can be renamed and deleted. But it's possible to rename and delete ALL default and custom Gradients/Bitmaps/Patterns/Hatches.
2 possible suggestions:
1. suggestion: No changes allowed
At default Gradients/Bitmaps/Patterns/Hatches, no context menu should be shown to the user so that they can't be renamed or deleted. Also the modify button should be grayed out (deactivated).
2. suggestion: Restore to default
If bug 106570 is fixed and if then it's possible to rename/modify/delete default entries forever: From a user's perspective, a tool is needed to restore the default set of Gradients/Bitmaps/Patterns/Hatches per tab (not for all tabs at once).
But all custom entries shouldn't be changed or deleted with that tool. The custom entries should still be stored after the default entries as it behaves now.
Change bug title and add meta bug (hope it's the right one).
Option 1: I could life with that.
Option 2: Sounds like an overkill. If we restore factory settings that should be done rather in the safe mode dialog but not at the various places where users in most cases intentionally tweak the configuration.
Option 3: Color is an exception and we keep all as it is.
Option 4a: Color names can be changed for predefined palettes.
Option 4b: Color names and values can be changed for predefined palettes.
For all options except 1: From my point of view as a user, how can I undo a change in default Gradients/Bitmaps/Patterns/Hatches? Maybe a change was a mistake, what can I do? The safe mode (a possible solution) would never come into my mind for that.
For option 1 (my preferred option): Was there an intention why it is possible to delete or change the default sets?
(In reply to Thomas Lendo from comment #3)
> For option 1 (my preferred option): Was there an intention why it is
> possible to delete or change the default sets?
Don't recall an intentional decision. The mockups contain a big add and a small trash button, rename was not taken into consideration at this time. Reason was that users should be able to create own presets and manipulate what we ship by default. The typical workflow for Benjamin is that he just selects what is in the left list.
The question is not only restricted to this feature but also to what comes next (having bullets and numbering in mind). Do we want to add a function to restore factory settings? And what does that mean: a) full restore, where modifications to factory presets are completely undone and also user defined presets deleted, b) "half" restore which affects factory presets only, and c) "specific" restore what is selected. I would understand "factory reset" as a) but the function should be c). In any case it has to be clear for the user. And feasible to implement without too much effort.
Issue is a bit worse as renamed title is not stored. But saving a document takes the current name. So we should disable renaming of inbuilt artwork.
Maybe an easyhack
I don't see the point if an user want to delete an default (system installed) preset.
If you want to delete an preset there is an additional dialog which ask if you really want to delete the preset. So from my point of view it's not possible that an user will delete something by mistake cause there is this additional dialog.
(In reply to andreas_k from comment #6)
> I don't see the point if an user want to delete an default (system
> installed) preset.
> If you want to delete an preset there is an additional dialog which ask if
> you really want to delete the preset. So from my point of view it's not
> possible that an user will delete something by mistake cause there is this
> additional dialog.
Question dialogs never make something really safe. I don't know anybody (including me) who hasn't ever not read the dialog warning text or accidentally clicked at OK in such dialogs. :)
My point is that if you give the user the power to modify single factory settings, the user should be able to restore this stage without discarding the whole user profile at once. This is good usability for me.
Dear Thomas Lendo,
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!
The context menus still here in
Version: 184.108.40.206.alpha0+ (x64) / LibreOffice Community
Build ID: 3ccc4c123f5e78e0204d11abeab2d1a74278ca3e
CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win
Locale: ru-RU (ru_RU); UI: en-US