On May 8, 2018, at 2:04 PM, Chanelle Allen <chanellem.allen@...> wrote:


Hello Chuck,
Well, now everyone will know what not to do or how to clear themselves out of my situation. I am glad that it did not affect you or anyone else. I was getting concerned about all of the memory warnings that you and other iPhone 8 users were constantly pestered with.
Chanelle

On May 8, 2018, at 14:45, Chuck Dean <cadean329@...> wrote:

👍 Cool Beans! 😎
Glad to hear you are up and running! I was getting worried, all the problems you were having, I was almost I was getting worried, all the problems you were having, I was almost sure that they would eventChanelletl to me! en@...> wrote:

Hello List,
The simple or not so simple VoiceOver setting preventing FlickType from functioning properly was direct touch, which I had turned off for some unknown reason. Flicktype needs direct touch to be on. Even when I reset all settings on my phone, I still experienced the problems described previously until I stumbled upon direct touch an hour ago. I had encountered direct touch in my rotor last night possibly while using FlickType, but I do not remember for certain. I must have not toggled it back on again. I really knew that I had a problem when even the FlickType app in the app store failed to respond on my phone. The fact that direct touch needs to be on for FlickType to work correctly with VoiceOver makes sense.
I am typing this email using the latest version of the FlickType custom keyboard, which is performing as expected. I appreciate that there is no latency after the keyboard has had time to load. Today, I am often retyping words, which probably has nothing to do with the predictive engine.
Thanks for all of your hard work Kosta, and for being patient with me and my false alarms. I hope that I have not set your work back in any way.
Chanelle