On Fri, Feb 21, 2014 at 8:49 AM, <Amphitryon@ok.de> wrote:

Just two points I was not able yet to solve on my own:
        self~connectKeyPress('RMC', .VK~MENU)
I wanted the Alt key alone to start RMC(). Alas it does nothing at
all (as far as I can see).

On the face of it, you should get RMC() invoked any time you press the Alt key.  If you don't, I'll take a look at when I'm on a Windows box.

If you want something other than that, you'll need to explain it better to me.  The Alt, Ctrl, and Shift keys are modifier keys. Typically you connect some other key, say 'W' and then add a modifier key to it in a filter to only get your method invoked when the W is pressed and the modifier key is already pressed.  So you could connect maybe Alt-W.

For that to work, the user has to press the Alt key and while holding it down press the W key.  Each key event notification comes in one at a time.  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.

I have a netbook with only one row of F keys, to get F13..24 I
have to press Shift and F1..12. In addition I have set handicaped
support on, so Shift, Ctrl, and Alt keys are 'sticky'. When I set
        self~connectKeyPress('about', .VK~F1, "SHIFT AND")
I get Help with F1 and both, About and Help with Shift-F1 but only
when pressing both keys the same time, the 'sticky' shift does not
work at all. Using .VK~F13 also does nothing at all.

What do I wrong?

I'm not sure that you are doing anything wrong.  F1 is a special system key, there is no way to over-ride its behavior. In Windows, any time you press the F1 key you will get the Help notification.

My advise is to not try and fight the operating system here, but rather pick a different key for your 'about'.  Maybe F14 instead.

Also, I'm not sure how the handicapped support fits in here.

Mark Miesfeld