On Tue, Feb 25, 2014 at 10:23 PM, <Amphitryon@ok.de> wrote:
>   You can't connect the Alt key and then set up any way to say I only want
> the Alt key when no other key is pressed after it.

Well, on Windows XP and 7 (others I do not know) you may activate
a 'key snap-in function' (Einrastfunktion in German) for easy
typing. As such you may press Ctrl+Alt+Del one after the other
(not simultanously) to restart.
> Also, I'm not sure how the handicapped support fits in here.

Normaly it fits quite well, at least for me. 

What I meant is how the handicapped support fits in with what ooDialog does, how it may effect what ooDialog does.

The connectKeyPress() method is relatively simple.  Each time a key is pressed down, the operating system sends a message to the window with the current keyboard focus.  That message essentially says "key[x]" was pressed down.  ooDialog intercepts that message and, if the key was one that is connected, checks the physical state of the Alt, Ctrl, and Shift keys, noting if there are currently down or not. Then ooDialog checks to see if the current state matches what you connected.

If you have other programs running that change things around in the keystroke buffer, or otherwise change the basic way keys are processed, then connectKeyPress() may no longer work as you want.

It is quite possible that either the handicapped support or the Einrastfunktion work by changing the basic way keys are processed.  If that is so, then connectKeyPress() might not work well on your system.

conectKeyPress() is intended to be a simple way of connecting something like F8 to clear a multi-line edit control.  Or to connect Alt-X to close the dialog, or connect F5 to scroll 3 pages in a multi-line edit control.  It is not intended or designed to work with any, or every, other keyboard utility that might be out there.

Mark Miesfeld