[PATCH] Permanent clear button for KLineEdit
Aaron J. Seigo
aseigo at kde.org
Wed Mar 25 18:09:53 GMT 2009
On Wednesday 25 March 2009, Oswald Buddenhagen wrote:
> On Wed, Mar 25, 2009 at 10:26:32AM -0600, Aaron J. Seigo wrote:
> > On Wednesday 25 March 2009, Oswald Buddenhagen wrote:
> > > On Wed, Mar 25, 2009 at 12:01:30PM +0100, Michael Leupold wrote:
> > > > attached patch makes it possible to set the clear button on
> > > > KLineEdits permanently shown (not hidden if there's no content).
> > >
> > > when this came up a few weeks ago, several people agreed that the
> > > disappearing clear button in bad ui design.
> > can you explain more, please?
> > here's the rational for the appearing/disappearing button:
> > * it signals when there is something it can actually do; no text? it
> > doesn't do anything. why be there
> why? because changing uis are *bad*,
you're misapplying the principle.
> > * it cuts down on visual noise. when they are always on and you have a
> > dialog with a bunch of blank text fields is looks a lot worse and the
> > user is confronted with a lot more visual noise for no reason at all
> i don't buy into that. following that logic we could make *a lot* of ui
> elements jump and hide on each state transition.
radio buttons, checkboxes, etc.: we do engage in state transitioning widget
what we don't do is hide/show widgets that adjust layouts making spatial
memory formation impossible or hiding information on possible selections and
neither is the case here.
> the usual approach to
> signalling a n/a state is disabling the widget (if we go that route,
> michael's api extension would make sense again).
see my other email on that.
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43
KDE core developer sponsored by Qt Software
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 197 bytes
Desc: This is a digitally signed message part.
More information about the kde-core-devel