toggle quoted messageShow quoted text
Okay so I've just recently updated to the latest version.
First of all, nice job. A lot of the latancy is gone, and the custom
dictionary thing helps a whole lot.
However, I am still getting this weird freezing issue.
So when I go to say send a text message, and I switch to the flicktype
keyboard, everything just freezes up. Voice over isn't frozen, but I
get absolutely no feedback.
I end up having to wait for about five seconds, make random gestures,
till I know flicktype is engaged by the feedback I'm receiving. I'm
not sure why this is happening, but it is no good for the soul. lol :d
Otherwise though, it is a whole lot better.
Out of sheer curiosity though, why is there a latency with the tap
sounds? is that something that can be fixed in future?
Thank you all so much, I truly appreciate all the work that's being put in.
On 5/4/18, George Cham <George.firstname.lastname@example.org> wrote:
Just testing with typing feedback set to nothing. In build55. When will we
be able to add numbers using the system keyboard? Oh! No memory warning
when using FlickType on I pad.
From: email@example.com <firstname.lastname@example.org> on behalf of
Sent: Friday, May 4, 2018 4:56:33 PM
Subject: Re: [FlickType-alpha] Build 55
Alex, the laggy tap feedback and the missed taps when typing fast
should be resolved
sometime next week, using a new custom gesture recognizer.
Macky, I have also experienced hearing the word just before the
punctuation, and this also happened when I switched to the iOS keyboard.
Also changing the VoiceOver typing feedback setting seemed to sometimes not
take effect until I restarted either the app or the entire device. I think
there are some iOS bugs at play here, although I am not 100% sure at this
point. I have tried way too many combinations of things over the last few
days and I'm only now starting to understand VoiceOver a little bit better,
in terms of how to get it to say what I want, as well as when and how I
want it to say it. VoiceOver definitely seems to misbehave a lot from my
By the way, I made a few improvements to the custom keyboard instructions
finally put them in this wiki page <https://flicktype.groups.io/
g/alpha/wiki/FlickType-Custom-Keyboard>. This will be the place to
reference first, and if your question is not covered there please let me
know when you post to the group so that I can also add the missing
information there. It seems that the exact wording on how and why to turn
typing feedback to "Nothing" will be critical to get right for new users.
Happy to hear any suggestions you may have in that area too.
Thank you all,
- To join our beta, please send an email here
- Browse all our forum topics <https://flicktype.groups.io/g/hello/topics>
- Post to our forum <email@example.com>
- Join our forum <firstname.lastname@example.org>
- Help & support <http://www.flicktype.com/help>
- Follow us on Twitter <https://twitter.com/FlickType>
On Thu, May 3, 2018 at 11:39 PM, Macster <email@example.com>
Hi Kosta, yet another quick update. I'm delighted to have the dictionary
available and happy to say it works very well indeed.
There is an error in the announcement of the full stop again however. If
type a sentence and flick right at the end, a full stop is entered but it
announces the last word of the sentence again. Its the same situation for
adding a question mark for example, if I typed how are you then flicked
right and then down 3 times, a question mark would be entered at the end
but I would hear the word you announced three times during said flicks.
Also, the pitch change... I noticed George said it works well with the
feedback set to nothing. I have noticed that this helps with the delay as
you said, but I still get the higher pitch whilst typing. Ironically
however, I get the normal pitch whilst deleting! I have use pitch change
for deleting set to on in my settings, is it possible that somehow this
inverting the expected behaviour?
Regarding the memory warning, I'm happy to report that I've yet to
experience this, and I'm running iOS 11.3.1 on my iPhone SE.