https://bugs.documentfoundation.org/show_bug.cgi?id=90721
Maxim Monastirsky <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.documentfounda | |tion.org/show_bug.cgi?id=46 | |839 --- Comment #5 from Maxim Monastirsky <[email protected]> --- (In reply to Jay Philips from comment #4) > The problem with the black in that .uno:XLineColor acts differently to Fill > Color (.uno:FillColor) While it seems so, in reality it's not the case. .uno:FillColor has blue hardcoded inside it, the same way .uno:XLineColor has black. None of them are showing the actual color (Assuming you are talking about .uno:FillColor when it's placed on a toolbar, not about the sidebar variation). So you're free to propose a different color for .uno:FillColor too. > and Area Style/Filling (.uno:FillStyle) which show > the current insert behaviour and that is the most important thing to show. So you don't want the line color button to be a split button? Back in 2012 UX guys filled bugs to convert all color buttons to split buttons - see the meta-bug at Bug 45671, and that's what I did. > We default highlighting you yellow as that is the most likely color going to > be used for highlight. Defaulting to red for font color is likely something > from that is just used from olden days rather than it having some stats > behind it to show that is the most popular color to change text to. Sure, I'm not defending the red color (nor the black), I'm just referring it as an example that illustrates how split buttons work. And IIRC there were requests to remember the last used color between sessions (for other color buttons too), and in that case the initial color will be different anyway. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
