Welcome!
This is the community forum for my apps Pythonista and Editorial.
For individual support questions, you can also send an email. If you have a very short question or just want to say hello — I'm @olemoritz on Twitter.
A better keyboard?
-
@zipit Interesting, it could be that the keyboard on the iPad Pro behaves differently, I don't have one, and things like this are difficult to test in the iOS simulator. I assume you have the 12" model?
-
FWIW, the Swift Playgrounds keyboard's code completion row suffers from the same "required delay" issue that @omz is describing. When you type and then tap a completion suggestion too quickly, the second tap is ignored. Even worse, if you're like me and then tap faster ("why is this dumb iPad not recognizing my touches") it still doesn't work until you stop tapping for the required time.
I've found this issue more noticeable in Playgrounds than in Pythonista for some reason, and I probably wouldn't have noticed it in Pythonista at all, if I hadn't read the forum discussions about it.
A fully custom keyboard sounds interesting, if it emulates the standard keyboard properly. I wonder how Playgrounds does it, because the Playgrounds keyboard feels like an extension to the standard keyboard (it works on different keyboard layouts for example) and not like a complete replacement. (Yet it somehow gets the shift key behavior slightly wrong, and as a result I mis-capizalize every class name.)
-
@dgelessus said:
I wonder how Playgrounds does it, because the Playgrounds keyboard feels like an extension to the standard keyboard (it works on different keyboard layouts for example) and not like a complete replacement. (Yet it somehow gets the shift key behavior slightly wrong, and as a result I mis-capizalize every class name.)
I'm fairly certain that it uses the system keyboard, and that the extensions are basically a private API.
I'm curious about the shift key behavior you've mentioned. How exactly is it slightly wrong? As I've worked on emulating the system keyboard for a bit, the proper implementation of the shift key was one of hardest things, and I wonder if I'm perhaps also missing something.
-
@omz When typing names with multiple uppercase letters in sequence (such as
NSObject), I use the onscreen shift key like a physical one. That is, I type (shift down)NSO(shift up)bject, and on the normal iOS keyboard it producesNSObjectas expected. In Playgrounds the shift key gets "stuck" if you do that, and the first letter after releasing shift is also uppercased, likeNSOBject. -
@omz Jeah, I a am. But nevermind, I found the problem now too ...
-
It looks like the Playgrounds (coding) keyboard is basically going to be available system-wide in iOS 11. I haven't tried it yet, but I tend to think that this makes my completely custom keyboard (from the latest beta) obsolete, so don't be too surprised if it disappears again...
-
I love the swipe down to get a number approach of your keyboard in the beta. It will be great to get that functionality in all apps.
-
Not sure if this is still relevant, but I am not seeing/feeling any auxiliary row delay on 6s Plus, 10.3.2, non-beta Pythonista 3.
-
@mikael That's expected, the problem only occurs on iPad.
-
I've been playing with the iOS 11 beta for a little bit, and it looks like the issue with touches being ignored in the extra key row is actually fixed. This is the first beta, so things could still change of course.
