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

List:       kde-accessibility
Subject:    [Kde-accessibility] Re: Why do all KMessageBox methods call exec()?
From:       Frans Englich <frans.englich () telia ! com>
Date:       2004-10-07 19:36:12
Message-ID: 200410071936.12838.frans.englich () telia ! com
[Download RAW message or body]

On Thursday 07 October 2004 11:04, Olaf Jan Schmidt wrote:
> [Adriaan de Groot, Donnerstag, 7. Oktober 2004 00:45]
>
> > I need a KMessageBox with a timeout
>
> What do you need it for?
>
> Timeouts are always a potential accessibility problem, because you cannot
> know how fast people are reading, typing and clicking. If you have low
> vision, or a motoric handicap, then having a message box with a timeout
> is a real obstacle.
>
> Is there no other solution rather than a timeout?

It's also done without feedback, and an action which isn't user initiated(the 
canceling).W while perhaps the most critical for accessibility, it also is 
generic usability issues. For example, one can be reading the message box, 
and then suddenly it disappear without knowing why. The screen resolution KCM 
has an indicator which tells it will disappear unless the user selects a 
choice.

Couldn't the API be extended to have this timeout functionality incorporated? 
Centralization is good, but most of all is consistency. It would allow 
feedback to be implemented(countdown). Dunno how to do it in a API-clean way 
though..


Cheers,

	Frans


_______________________________________________
kde-accessibility mailing list
kde-accessibility@kde.org
https://mail.kde.org/mailman/listinfo/kde-accessibility
[prev in list] [next in list] [prev in thread] [next in thread]