Using a Nexus One with the stock 2.1 firmware.
Striking keys in quick succession doesn't always work
Striking keys in quick succession doesn't always work
Just like the title says, and it's really easy to reproduce, especially in landscape mode. Pick two keys on the keyboard, for example, S and K. Alternate pressing them very quickly with both thumbs, e.g. sksksksksksksksk. Sometimes one or more of the keys won't register, although I can clearly see them lighting up when I touch them. Also, in this example (using S and K), sometimes I see the "G" key light up for no reason -- my fingers are nowhere near it! 
Using a Nexus One with the stock 2.1 firmware.
Using a Nexus One with the stock 2.1 firmware.
- cyril
- Developer
- Posts: 2079
- Joined: Tue Feb 02, 2010 4:02 pm
- Phone: Nexus One 2.3
- Location: Nice, France
Re: Striking keys in quick succession doesn't always work
The code to register the keypress can be improved, but it's a huge work and not the priority for now.
As for the "G" key pressed by itself, I guess this is another bug of the screen driver which reports wrong events to the app... anyway I have no other explanation
As for the "G" key pressed by itself, I guess this is another bug of the screen driver which reports wrong events to the app... anyway I have no other explanation
Cyril
Re: Striking keys in quick succession doesn't always work
I see, darn. I'm finally becoming proficient enough at using the onscreen keyboard that this is causing me to make a lot of mistakes, at least one per sentence. If you don't mind me asking, what types of other features can we expect in the short term? It seems speed and accuracy should be the most important features of a keyboard 
- cyril
- Developer
- Posts: 2079
- Joined: Tue Feb 02, 2010 4:02 pm
- Phone: Nexus One 2.3
- Location: Nice, France
Re: Striking keys in quick succession doesn't always work
I agree with you.. I was just playing again with the iPhone keyboard yesterday and it's incredibly fast... I don't know if it's due to the use of native code instead of Java, or if the algorithm is better... but anyway my goal is to get something as fast as the iPhone, even if I need to rewrite everything in C++ (though I hope there is an easier solution
)
This and improving the dictionary are the two main challenges
This and improving the dictionary are the two main challenges
Cyril
Re: Striking keys in quick succession doesn't always work
i would looooove to have a keyboard as fast and easy to type on as the iphone. this keyboard is definitely so much faster than the stock for sure tho. keep up the great work and i would love to see the multitouch glitch be improved! thanks
Re: Striking keys in quick succession doesn't always work
Just checking in, have you made any progress with this issue? 
Re: Striking keys in quick succession doesn't always work
Just something to add about the iphone keyboard. The size of the trigger area of a key changes depending on the previous letter. Example: after hitting "t" letters like "b" and "n" would have a smaller area compared to say "h" or "i" thus improving accuracy. Just an dying incase you didn't know.