Created attachment 74627 [details] Ideas Context: I am part of a small project opensource technology integration in a school of psychology at a local university. Right now is in the process of integration of LibreOffice 4.0 (and the use of ODF in the institution) and the installation of a small server (which will be the basis for the integration of collaborative technologies as sparkleshare). This has me very happy, because it integrates academics, workers and students. Not all use GNU / Linux as the default OS, but some teachers and support this, and this is installed on computers in the classroom (media-handlers). Despite having a driving medium / medium advanced with the basic programs, I have done some feedbacks LO Impress presentation tool you use every day, and whose experience as end users cite as justification for this error. Problem Description: More than a "bug" would define it as a "non-bug" because the point is not that something is not working well, just does not work (as expected). The function to be mentioned, is the selection of a custom color for the slide background. Teachers made me see that the menu is something hidden (menu: slide / Page Setup / background) in which you have to open a menu to choose a color ... and Surprise. You can only choose the colors on the palette of the program. When I mentioned how they could add new colors, they were surprised because they had to make a very long process and that affected the whole suit (compared with the counterpart in MS Office), considering an advanced feature (targeting the home user). I think they are right. I have managed to create a varied color palette, but if there is one, the menu is not designed to display simple colors (because it's a list!). From the 3.5 that there is a good color picker, would be a great idea to integrate instances requiring color selection and not necessarily added to the color palette (as it is a selection for that file, nothing else). Finally, the choice of color for the background of slides could be improved, and that based on the experience of teachers, I say it is very impractical. They mentioned that usually, rather than using a template, create their own presentations. This is done in a simple, focused on content, using no more than 2 ideas per slide, "representative colors" and good typography, because as presentations with many sheets, and lighten its weight. For now they have accepted my proposal for the color palette, but that does not mean they are right. I offer it as an error because it's "core" that could be running (hey, that's just the choice of custom colors, no transparencies, gradients, strokes or dropper for color and Office 2013) thanks
I would agree, that this would be a very good enhancement, because the current solution is really annoying. I hope such a function will be integrated soon. In my view this is an enhancement and therefore I have marked it as enhancement and increased the importance. @Thorsten: Could this maybe be an issue for you?
The same problem also happens for gradients, but worse. At least colors can be edited from Tools/Options, but gradients don't have that. Is there a meta-bug that lists all the places where colors/gradients can be selected, but not edited?
(This is an automated message.) LibreOffice development currently prioritizes bugs with the so called MAB (most annoying bugs) -- as this bug has not run through that process (including writing a short rationale for this bug being a candidate and other who are watching the tracker bug silently approving that rationale etc.) its priority is set to high. Note this is effectively no change in the urgency assigned to this bug, as we are currently not making a difference between high and highest and severity is untouched. You can find out more about MABs and how the process works by contacting libreoffice qa on irc: http://webchat.freenode.net/?channels=libreoffice-qa The QA wiki page also gives you hints on how to get in contact with the team (if IRC fails you, your next best choice is the mailing list): https://wiki.documentfoundation.org/QA
This was fixed with bug 94551.