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

List:       kde-accessibility
Subject:    Re: [Kde-accessibility] Broken Sticky Keys (Bug 41778)
From:       David Parker <david () dkpweb ! net>
Date:       2002-10-22 23:55:40
[Download RAW message or body]

In doing a little research I came across the following info:

http://www.wearable.ethz.ch/projects/research/weararm/linux/x_options.html

Command line options of X servers
The X Keyboard Extension adds the following arguments:
-kb                    disable the X Keyboard Extension
+kb                    enable the X Keyboard Extension
[+-]accessx [ timeout [ timeout_mask [ feedback [ options_mask] ] ] ]
                       enable/disable accessx key sequences
-ar1                   set XKB autorepeat delay
-ar2                   set XKB autorepeat interval
-noloadxkb             don't load XKB keymap description
-xkbdb                 file that contains default XKB keymaps
-xkbmap                XKB keyboard description to load on startup

As a workaround until a KDE Applet can be altered to modify the default 
behaviour, it looks like one can add +accessx to the serverargs parameters in 
the startx script. I've tried this without success. My default runlevel is 5. 
Maybe I don't understand correctly how startx is invoked on Mandrake 9.0. If 
I switch to runlevel 3 and issue startx, I get an error about no xserver 
available. I don't suppose anyone could shed some light on this?

Thanks,
David


On Tuesday 22 October 2002 06:07 pm, Bill Haneman wrote:
> On Tue, 2002-10-22 at 23:17, David Parker wrote:
> > First let me say thanks Bill for your research. I commited the sin of
> > sending an email in frustration. I apologize for the tone of my earlier
> > message.
>
> David:
>
> When you complain below about "calling bugs features", bear in mind that
> I am referring to XKB; XKB is an XServer extension, not an end-user
> API.  Thus I stand confidently by my earlier comment.
>
> However, failing to expose this feature in a reasonable way, or not
> documenting this feature, both qualify as bugs in whatever keyboard
> accessibility UI one offers.  (see a couple of comments below).
>
> best regards,
>
> Bill

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