Re: Build 34 is out to alpha
Andrew McKay <awmckay@...>
Kosta,toggle quoted messageShow quoted text
With regard to the swipe right gesture--Not sure its any worse than the previous build so probably no reason to say this build is worse. I will say that from around build 30 )I can't be 100% it was that build as I wasn't paying that close attention to build numbers before getting more involved), it did seem to get worse.
With regard to the home gesture on an iPhone X--that would be a definitely frustrating IOS bug if it carried over to every app once you get to an integrated third party keyboard as it is really hard to gage your gestures without the haptic feedback. DO you think it would reverberate across apps in those circumstances? You mention how low the keyboard is on an iPhone X, I do think there is some weird behavior in which the z, x, and c characters extend all the way to the bottom of the screen to the left of the spacebar.
From: email@example.com <firstname.lastname@example.org> On Behalf Of FlickType
Sent: Wednesday, April 11, 2018 4:21 AM
Subject: Re: [FlickType-alpha] Build 34 is out to alpha
Thank you, Andrew.
On the keyboard being low on an iPhone X: there seems to be an iOS bug where any view utilizing Direct Touch will consume touches when VoiceOver is on and interfere with the home and app switching gestures. We have not yet found a workaround, and haptic feedback as you say is not provided. The actual keyboard placement, however, should be roughly where the standard keyboard is, so hopefully it does not affect typing accuracy. You can confirm the placement by examining the position of the bottom row keys, eg z x c v, by doing a tap and hold gesture.
On swiping right adding characters instead of the end of a word: the current flick recognizer is far from perfect and this may sometimes happen in all directions, as well as when using 2 fingers for a new line, to switch layouts or to invoke the menu. Please do let us know though if this seems to be considerably worse than in previous builds.