Forum Archive

Hey all, am I the only one experiencing weird, missed keyboard input on the top row number keys? All other keys are responsive, but the top row is exhibiting some weird behavior... At least for the way I am typing. I'll be punching in keys no problems, then time to input a number of hit the '=' key, and nothing happens. It seems like the keyboard ignores my first input but accepts subsequent attempts. I can duplicate the behavior about 70% of the time by pressing delete and then '=', and it is repeatable with other button combinations such as alphabetical characters, followed by any numeric character.

I'm on an iPad mini retina (ME279LL/A) running iOS 9.2.1

The reason this happens is that in some iOS update a while ago (I think 8.2, not sure), Apple decided to start ignoring touches that happen "too quickly" after using the on-screen keyboard. This also applies to views that are attached to the keyboard, i.e. the extra rows of keys that Pythonista adds.

If you haven't already, I would recommend that you turn off the 2-row "extended keyboard with numbers" in the settings. In Pythonista 2.0, I've changed the implementation of the single-row extended keyboard to work around this issue (unfortunately not possible for 2 rows of keys), so you'll probably find this to be less of an issue with the smaller variant of the extended keyboard.

Bummer. I sat on iOS 7 forever and finally gave into upgrading when I saw you released the 2.0 update which required a later iOS, only to have overall functionality and usability reduced due to iOS related bugs. I'm grateful for the new functionality, but I would roll back to the old version if it weren't a pain to revert the os as well.

Any hope of fixing this and the other keyboard input bugs?