As far as I know, the FW pads just do what normal keyboards would do. I think you're asking about the numerical decimal point key on the iGesture Numpad, right? If you have your main keyboard in CAPS LOCK then it will not affect punctuation, but if you hold SHIFT then punctuation will be affected -- both on your keyboard and the iGesture.
Unfortunately the MyGesture Editor only allows mapping of entire keys to a surface area -- it would be handy sometimes to be able to map distinct lower- and uppercase characters.

I'm sorry Petrov, did you not hear? There will not *be* a future version of MyGestureEditor (unless we code it ourselves!). It's not at all likely that whoever bought FW is going to continue to support this product line. We have to make do with what we have.

It contains the following entry:
<pre> <TapArea xcenter="9.9" ycenter="0.1" isRectangular="true" width="1.9" height="1.9"
macro_name=" . " layoutContext="NumLock ScrollLock">
<KeyEvent keyCode="Numpad." />
</TapArea></pre> You can try to redefine this key without the layoutContext="NumLock ScrollLock" atttribute in your configuration file.
This restriction will not apply any more when you enter some other context...

good morning, Ivanw!
thank you for your answer.
i dont have experience enough in programming to understand what you suggest. i didn't find the FW_igesture_numpadkeys.xml so i couldn't try it out.
can you or somebody else give me some further explanations.
thank you!
peter

@Torben
no i didn't know that the fingerworks products probably will not be developed any longer. what a pity!

Good morning, petrov!
Here are some details about how to understand my programing small talk:
First you have to save some customization file of yours with the MyGesture editor program.
- If you did not play with this one, some starter advice could be worth here too...

The result of doing that is a file you will find here:

You have to modify the xml file you created there. You can do that with Notepad. Just insert the THREE extra lines before the closing </MTS_config> tag on the last line. This will override the default internal definition of the punctuation key.
- Just ignore the FW_igesture_numpadkeys.xml file, it is out of sight in the FW_defaults.jar Fingerworks library file. I've mentioned it only for those interested with editor initialization.

As we do not have the same device, this gives me an extra key Anyway, here is what I get:

Note that this may do the trick or not, whether I am right or wrong on both understanding the problem and giving an effective -untested- solution.
Let us know if this is still unclear. As I am still a programmer, I may use strange ways when I explain things I pretend to know about

hello Ivanv!
thanks a lot for your extensive answer!
it has helped me to accomplish to make the dot-key independent of the shift-key, but there has been a side effect that i don't understand.
now the dot-key produces a comma and whatever i've tried i can't get back the dot also if i manually define it via the myGestureEditor or reset to factory defaults!
but the side effect itself has had the side effect again that my numpad now behaves like my main keyboard which i have modified insofar that i have installed a tool which adds a keyboard layout to the system that differs from the default layout just in a single point. it changes the comma-key on the numerical block to a dot-key. and if i set this active then also the numpad has a dot on the dot-key independent of the shift-key setting on the main keyboard. but only if i've changed the .xml-file in the way you suggested it.
so finally i've been successful in the end thanks to your help.
thank you very much!
peter

The macro_name="." part does not comply with the observable syntax by a very faint detail that may be the issue:

The dot character should be preceded by ONE space and followed by TWO spaces as follows: " . "

Here is the original entry from the default file FW_igesture_numpadkeys.xml:
<pre><TapArea xcenter="9.9" ycenter="0.1" isRectangular="true" width="1.9" height="1.9"
macro_name=" . " layoutContext="NumLock ScrollLock">
<KeyEvent keyCode="Numpad." />
</TapArea></pre>As this character string is an identifier delimited by the surrounding double quotes, spaces should be considered significant here.
Anyway, this is worth a try if you are not too bored yet

Rqyteqto, I believe that anything valuable is such because of the details. Even great ideas like Westerman's must be followed by an incredible amount of work on countless details. That makes me sense the urge to be as smart and patient as possible while exploring this subject.

I am so sure that we should experiment all the topics brought by this forum members to learn about the unexplored possibilities. This is why I am willing to post on any issue on which I can have some "valuable" input. Involvements brings me more insight whether I happen to be helpful or not

This post is mainly motivated by my will to encourage those who have less technical insight about FW devices. Please, share anything you have in mind that could be achieved through customization. I would even welcome funny ideas, those happen to be the best ones at the end I am really happy about how I could eliminate ALL reaches thanks to left hand modifier gestures. I am curious about how far we can go with ideas like these...