--===============0108406272==
Content-Type: multipart/signed;
  boundary="nextPart31582202.GxCeRv0v1s";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart31582202.GxCeRv0v1s
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hello,

=46or those of you that do not know the features that can be enabled by=20
keyboard gestures I will give a short description:

Sticky Keys: Usefull if you cannot press two keys simultaneously. Basicly=20
the modifier keys work like lock keys. (Keyboard gesture: press Shift 5=20
consecutive times)

Slow keys: Usefull if you have shivery fingers. Here you need to press each=
=20
key a certain time before it gets accepted.  (Keyboard gesture: press=20
Shift for about 8 seconds)

Mouse Keys: You can control your mouse with the keyboard. (Keyboard=20
gesture: depends on your keyboard layout, often it ie Shift+Num Lock)

Bounce keys: Also usefull if you have shivery fingers. Here a key is=20
blocked a certain time after you have released it. In order to press it=20
again, wait until it is not blocked anymore.  (Keyboard gesture: none that=
=20
I know about.)

Both these features and their gestures are defined by X. You often refer to=
=20
them as AccessX features.

On Saturday 08 January 2005 15:23, Anders Lund wrote:
> On Saturday 08 January 2005 14:57, mETz wrote:
> > On Samstag Januar 8 2005 13:46, Anders Lund wrote:
> > > How do i turn that
> > > off completely? I really want to be able to hold my keys down for as
> > > long as i want without worrying about it changing how my keyboard
> > > works!
> >
> > by reading the warning message thoroughly and then go to the kcm it
> > mentions.
> >
> > Bye, Stefan aka mETz
>
> No means for turning it off completely is offered. No matter which
> checkboxes I check there, I may accidentially enable those features.
> [...]

You can prevent that by disabling the checkbox "Use gestures to activate=20
the above features".

> In my opinion it should be possible to prevent that, and even they tried
> to make it hard to toggle those features by accident, they should be
> entirely disabled as default. Those who need them will know to enable
> them I'm sure.=20
=20
Those who need some of the AccessX features do not necessarily know the way=
=20
of starting the KDE Control Center, choosing the=20
Regional&Accessibility/Accessibility tab and finding the features there.=20
Even if they know that way it might be hard for them to do that because=20
they need these features in order to do that.

On the other hand those who do not need these features are can deactivate=20
it without problems.

Maybe we could add a button "Start the Accessibility KCM" in the dialog,=20
though.

Gunnar Schmi Dt
=2D-=20
Co-maintainer of the KDE Accessibility Project
Maintainer of the kdeaccessibility package
http://accessibility.kde.org/

--nextPart31582202.GxCeRv0v1s
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBB3/YIsxZ93p+gHn4RAi00AKD1bEQAJxYtu1X/Sqoi/0lyRYcMiwCdHssb
IN9CLWr9CZZ2382uye1ykDY=
=gkrK
-----END PGP SIGNATURE-----

--nextPart31582202.GxCeRv0v1s--

--===============0108406272==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0108406272==--