Hold Numpad On Quit Working

[jmadison]

Check the thread "Numpad Modifier Chords and (alternative) dual-home-row Number Pads" for the history of this one.

In brief: my Hold Numpad On quit working.

I still have it defined as L4F above home row in the Gesture Editor, and just to make sure, I re-transferred the current version to my TS. Can anyone help?

My config file is attached. I renamed it from *.xml to *.txt so that the file filter would let me post it.

Thanks!

[MrLightTouch]

Are your driver and layout modes still driverContext=" win" layoutContext=" us101"? According to the config file that's the only context you have Hold NumberPad On active in. If you've switched modes without realizing, that could explain the loss.


Also, the TapArea elements at the bottom of the file seem to be missing their macro_name attributes. Not sure how that could have happened--might be messing things up. You might want to try deleting all those elements.

[jmadison]

Are your driver and layout modes still driverContext=" win" layoutContext=" us101"?

You're going a little fast for me :confused:

How do I check that?

Also:
Also, the TapArea elements at the bottom of the file seem to be missing their macro_name attributes.

Is there a way to get this back to some 'normal' mode of operation? Should I start with a new file and recreate my customizations, or should I remove and reinstall the MyGesture Editor?

Thanks...

[fingerworks]

Ignore the previous suggestions. It might have something to do with CapsLock and ScrollLock having snuck on in your UserOptions (ScrollLock can cause arrows instead of numbers). But in any case when we loaded the attached into one of our units your numpad setup worked fine.

[jmadison]

Okay....

I don't think I'm even going to try to understand this one. After reading your reply this morning, I tried using my hold numlock again. It >just worked< and it's monday morning. I guess I've used up all my luck for the week, and I haven't even finished my morning coffee yet. :)

Thanks....
-Jason

[fingerworks]

We were saying...try to keep ScrollLock turned off! That might cause your numpad to be interpreted as cursor keys instead of numbers.

[jmadison]

Okay, okay,

I checked both the scroll lock and caps lock, but in either position everything worked fine. It was the numlock key that was the culprit. If I have the numlock on, it works fine, but with the numlock off, then I have the trouble that started this whole thread...

thanks.... now I got it.