[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-core-devel
Subject: Re: [Kde-accessibility] Re: Why do all KMessageBox methods call
From: Olaf Jan Schmidt <ojschmidt () kde ! org>
Date: 2004-10-07 20:14:48
Message-ID: 200410072214.50165 () amen-online ! org
[Download RAW message or body]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
[Frans Englich, Donnerstag, 7. Oktober 2004 21:36]
> 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..
Having this in the API would also allow us to have a global setting for a
minimum timeout, and to reset the timeout whenever a user input is made.
If it is technically possible for kpilot to reset the connection timeout,
and for the job execution Jason described to be delayed if the user
presses a key to navigate within the dialog, then both would be
candidates for using such the extended API. If the KDE screensaver has a
timeout, then it should also use this solution:
http://lists.kde.org/?l=kde-core-devel&m=109717620713867&w=2
Is there someone who would be willing to help us by implementing it (if
people agree this is a good idea)?
Olaf
- --
Olaf Jan Schmidt, KDE Accessibility Project
KDEAP co-maintainer, maintainer of http://accessibility.kde.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iEYEARECAAYFAkFlo7gACgkQoLYC8AehV8eFqwCcCK8PUQu78qLXfR+ilOdV/PiW
6vIAnR0dIkOu4fEw15nyDgX1XFgBRmJm
=LaRH
-----END PGP SIGNATURE-----
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic