https://bugs.kde.org/show_bug.cgi?id=384514
Hugo Pereira Da Costa <hugo.pereira.da.co...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hugo.pereira.da.costa@gmail
| |.com
--- Comment #6 from Hugo Pereira Da Costa <hugo.pereira.da.co...@gmail.com> ---
(In reply to Nate Graham from comment #5)
> Created attachment 107772 [details]
> Real segmented control elsewhere in Gwenview
>
> Since making un-pushed toggle buttons visually distinct from pushbuttons
> appears to be more controversial, I'll drop that for now and focus on
> segmented controls. Not having a dedicated segmented control concept/UI
> element is a major problem. But I see that in Gwenview, we actually do use a
> button-based segmented control elsewhere: https://i.imgur.com/pySdLn0.png
>
> Other than the padding issues with text on the middle button, this is ideal,
> and clearly communicates at-a-glance the concept that only one of those
> three states can be chosen at once. We might consider using this instead, or
> even standardizing it.
as far as I know this is a gwenview specific custom widget.
one could move it "upstream" in widgetsAddon or somethign like that, fix the
padding issues, and leave it to applicatiosn to use it or not.
any heuristic at the style level to do the rendering directly will be a kludge
and likely bound to fail
--
You are receiving this mail because:
You are watching all bug changes.
