[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-usability
Subject:    Re: Can we* prettyplease do something about the KUrlNavigator?
From:       Matthew Woehlke <mw_triad () users ! sourceforge ! net>
Date:       2009-06-22 21:40:31
Message-ID: h1otog$cp0$1 () ger ! gmane ! org
[Download RAW message or body]

Peter Penz wrote:
> On Monday, 22. June 2009 19:26:01 Matthew Woehlke wrote:
>> Thomas Lübking wrote:
>>> Peter just changed that a bit - now a lineedit frame (no bg) pops up
>>> on hovering the NavigatorBar (the entire widgit including empty
>>> space)
>> That's not too bad, but there seems to be a delay before the frame
>> appears. Can that be fixed?
> 
> The delay has been added on purpose, otherwise there would be a flickering if 
> the user moves the mouse from the view to the toolbar buttons.
> 
> Hmm, should the delay made smaller?

The caret already flickers. The outlines around toolbuttons already 
flicker. Many* hover effects in general already flicker.

IMO these should be consistent; either they should ALL have a delay, or 
none should. Right now it feels (to me, anyway) like a bug, as in "why 
does it take so long to paint?".

(* Depending on style, hover effects may fade in/out... but it should 
still be consistent :-). Is KURLNavigator styled by KStyle yet? If not, 
can it be?)

> Or would it be sufficient to change only 
> the mouse cursor to an I-beam as Matthew suggested?

I'll let others weigh in on that. I somewhat like the frame, but I'm not 
wedded to it.

-- 
Matthew
Please do not quote my e-mail address unobfuscated in message bodies.
-- 
"Have you tried that new mixed drink, 'GDR'"?
"What is it?"
"Gin, Duck and Rum. It tastes fowl."

_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability

[prev in list] [next in list] [prev in thread] [next in thread]