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

List:       kde-devel
Subject:    Re: KDE Window Focus Behaviour
From:       James Richard Tyrer <tyrerj () acm ! org>
Date:       2004-07-04 20:01:47
Message-ID: 40E8622B.6080205 () acm ! org
[Download RAW message or body]

Thomas Lübking wrote:
> Maybe a call to redesign software could rather be usefull.
> Another foreign browser project i.e. (about something like a dragon :) delays 
> the appereance of critical buttons like "yes please execute this virus on my 
> system" (the browser runs on strange OS like bluescreen collections as 
> well :)
> 
> So maybe ask authors (design guideline, part of any std. kde app) to delay 
> appereance (or enabling, but i think appereance is better) of buttons that 
> cause some real action (so where you should have a choice and do not simply 
> clickawa a message) for a very short time (half a second should be enough - 
> as the user needs to read the dialog message anyway)
> This would imho prevent unwanted actions by not messing up with focussing 
> stuff and dosn't slow down work process at all.
> (e.g. if i choose along run action, the app starts, i change to some other 
> stuff, i don not want to notice about an hour later, that the lr app stopped 
> after five minutes, presenting a dialog i missed)

I'm not sure about this.

It is really annoying if you are typing something and KGet interrupts you to 
tell you that there is a problem with your download.

But, OTOH, you do need to know that there is something wrong with your download.

Perhaps a useful idea is that the items in the: TaskBar could change color to 
indicate that another window has opened in the application that doesn't have 
focus.  Ideally, this should normally just turn Blue till you open the new 
window, but if it is an error message it should turn Red.  Additional, either 
audio or visual, methods of alerting the user without taking focus could also be 
considered.

--
JRT
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]