h1xkbd sometimes produces wrong characters

[webmeister]

Sometimes when writing text or commands the h1xkbd keyboard produces the uppercase version of the selected letter without shift/caps lock being activated. Not only letters are affected, but every other key too. The number of wrong characters seems to increase with the typing speed.

To reproduce, start the editor and tap as fast as you can on different letters on the keyboard. In your text you should see several special characters normally hidden on the Mult page, but on the same position as the key you selected. I do not know why in this test the wrong characters are taken from Mult while during my normal usage I end up with characters from the shift page (I can only guess that this has to do with the typing speed too).

Using user-rev5rc1.

[tomageeni]

I think it's a feature, not a bug :-)

When you press any key and slide your finger/touchpen up about 1cm or more, you get the same key as shift pressed down (e.g. h -> H, 4 -> $). Same effect happens when you slide your finger left, but instead of capital letter, you'll get the special letter on same place (equal to Mult pressed down), e.g. press j -> slide finger left -> you get {.

This actually improves your writing speed when you learn to use those. And when you learn not to slide your fingers when you want to get normal letter. :-)

[webmeister]

"The only difference between a bug and a feature is the documentation." It behaves exactly as you described it, but I found no explanation of this behaviour. Perhaps Shift and Mult should be removed from the keyboard, so that users are confused in the beginning ("Where do I get uppercase letters?") instead of later on ("Where do these stange characters come from?"). ;-)

But there might be another improvement that could keep this behaviour (at least for uppercase letters this seems really useful, because you do not have to learn the mapping between the characters) while reducing my errors: At the moment, I get an uppercase letter whenever I leave the key to the top. It makes no difference whether I slide my finger ten pixels upwards or hundred as long as I leave the original key. So in case I hit the key not in the middle but at the top a small slide is enough to get an uppercase letter though maybe I didn't want it. I'd suggest to use the sliding distance instead, so only when you slide your finger more than x pixel upwards you get the uppercase version. x could then be user-configurable so people (like me) who want to avoid errors at all costs can set it to a high value and thus reduce the chance of accidentally activating this feature.

[zecrazytux]

David, can you write a bit of documentation about this behaviour in you new "user manual", and consider webmeister ideas ?

thanks ;)

[Deubeuliou]

documentation written.
But the behaviour you suggest, webmeister, could be useful to implement. Feel free to submit a patch ;)