Hi,
I think you miss the BackSpace in the "TAdvTouchKeyboard.ItemKeyDown" ...
I've Version 1.2.12.0 but there is no remark for this issue in the Update-Text.
Adding
skBackSpace: Key := VK_Back;
in line 1358 in the AdvTouchKeyboard.pas
work fine for me.
If you look this codeline you will surely agree! :-)
Maybee It's already corrected and you miss the remark in the
Update-Text, but if you do so, ignore this Topic, or maybe add this issue
simply for the next Update-Text, so I can find this! :-)
Greetings from Germany
Gabriele Hillebrandt
Thanks for reporting. We can confirm this will be fixed in the next update.
Hello,
Thanks for this feedback.
You're correct. Backspace makes more sense than Numlock. We'll modify this accordingly for the default. If further customizations are needed, this can always be done by modifying the Keys collection at design-time.
Hi,
I think you miss the some more Keys in the "TAdvTouchKeyboard.ItemKeyDown" ...
Today I add "skSubstract: Key := VK_SUBTRACT;" at line 1355 manually.
I just need skSubstract but it makes more sense to add all missing keys.
Simply look for "TSpecialKey" at line 87 and compare.
Greetings from Germany
Gabriele Hillebrand
This depends on the type of use. The numeric keyboard we provided was more with the intention to create passcode entry on touch screens where things like a subtract key are not wanted.
We'll consider to make an extra calculator keyboard where the add/subtract/divide/multiply keys are also available.
Hi,
sorry, I don't understand. Can you explain this more detailed, please?
In my opinion, if a programmer take the decision to set the setting of a
key to "skSubstract", the key should behave like a substract-key!
If I don't want an substract-key I simply don't add one!
Notice, that I don't ask to add the substract-key to any standard-key-layout.
Greetings from Germany
Gabriele Hillebrand
Sorry, I was confused by your question.