The drop-down dialog buttons used in AutoFilters are not native UI widgets; we draw them - and we provide the graphic. It seems that graphic has not changed for the past 20 years, if not more, when screen resolution was half what it is typically these days. Now, a more fundamental solution would probably be to use native widgets somehow (bug 163017) - but in the mean time, we should at least: * Increase the resolution of the button images * Apply a bit of anti-aliasing and perhaps even: * Make the images VCL-dependent to sort-of-emulate actual native widgets. although just the first two would be an improvement.
Created attachment 202465 [details] Autofilter drop-down dialogs - notice the buttons with the downward triangular arrow
Created attachment 203254 [details] Arrow button on PivotTable controls - LO 26.2 nightly Screenshot illustrates what our current situation is; and it ain't pretty - literally: * Aliasing / low resolution * Inappropriate foreground color * Inappropriate background color * Solid backround square rendered in wrong place * The 3 horizontal lines look very much out of place.
Created attachment 203485 [details] How the arrow looks with a background color
@Heiko, is it intended that the icon's background is white? it looks a bit weird when the cell has a background, at least it should have a border I think
(In reply to Xisco Faulí from comment #4) > it looks a bit weird when the cell has a background Polite understatement of the year. Even a simple reversion of the change would be an improvement at this point I'm afraid :-(
(In reply to Eyal Rozenberg from comment #5) > (In reply to Xisco Faulí from comment #4) > > it looks a bit weird when the cell has a background > > Polite understatement of the year. > > Even a simple reversion of the change would be an improvement at this point > I'm afraid :-( I apologize for my lack of coding skills. It's indeed perhaps better if I abstain and leave this work for developers.
(In reply to Heiko Tietze from comment #6) > I apologize for my lack of coding skills. It's indeed perhaps better if I > abstain and leave this work for developers. You made a valiant effort to try to affect some change, and that's good. Absolutely no criticism from me for having tried this. I remember you were hesitant even when we discussed it at the design meeting. So, while I am critical of how the this looks right now - I am very appreciate of the effort, and of the willingness to experiment.