Caution against updating to iOS 16 for those using FlickType Classic
Many thanks, Chuck. Now I see what you were saying. The single finger double tap and hold causes a blurp sound and brings up what I’ll call context options and single finger swiping left will take you to paste and double tapping on it did result in a successful paste without confirmation when the source was FlickType. I’ll add that for those not liking the single finger double tap and hold to do this, you can also do a single finger triple tap.
I do believe this is a tad faster than using my customized gesture paste and having to confirm it.
Alan
Sent: Friday, September 23, 2022 4:45 PM
To: hello@flicktype.groups.io
Subject: Re: [FlickType] Caution against updating to iOS 16 for those using FlickType Classic
Hello Alan,
After I copied this text from FlickType by closing the app, I selected the reply option and then did a double tap and hold until I heard the pass through sound. I lifted my finger, and flicked left through the commands until I heard paste, then I did a double tap to insert the text.
A few more taps then the two finger quadruple tap but still workable.
Chuck (mobile)
Pleez x cuze enny tie ping or spelin air ores.
On Sep 23, 2022, at 12:12 PM, Alan Lemly <walemly@...> wrote:
Hi Chuck,
I’m a bit confused by what you’re calling paste in the normal manner. If I paste by calling up the rotor, selecting edit and single finger swiping to paste followed by a double tap, the typed info from FlickType Classic pastes just fine without any confirmation of the paste. I believe the 2 finger double tap and hold you referenced is used to custom label an element but I’ve been known to confuse my gestures. Doing the rotor thing requires more gestures than simply using my custom paste gesture and approving the confirmation.
I’m getting the paste confirmation every time I do so with my custom gesture when the source text is coming from FlickType. However, I did just note that when I go to a text in process of being composed, use the rotor edit gesture to select all the text and copy it, and then paste it into a new text message using my custom paste gesture, I’m not prompted for the confirmation. But if I then jump back to FlickType, type something new, and go back to the text being composed, I’m again prompted for confirmation when using my custom paste gesture.
As I said before, I’ll keep playing with alternatives to see if I can ferret out a quicker workaround. All ideas are welcome.
Alan
From: hello@flicktype.groups.io <hello@flicktype.groups.io> On Behalf Of Chuck Dean
Sent: Friday, September 23, 2022 1:28 PM
To: hello@flicktype.groups.io
Subject: Re: [FlickType] Caution against updating to iOS 16 for those using FlickType Classic
Hello Alan,
You may want to try to paste in the normal manner without using the two finger quadruple tap. For example when after typing on FlickType, close the app, and then open what you want to paste it into double tap and hold until you hear the pass through gesture sound, and then flick right until you hear paste and then double tap. See if that stops the confirmation, and if it does then you’ll know it’s the two finger quadruple tap that’s causing the problem.
I also use the two finger quadruple tap for pasting, it works excellent!
Chuck (mobile)
Pleez x cuze enny tie ping or spelin air ores.
On Sep 23, 2022, at 10:55 AM, Alan Lemly <walemly@...> wrote:
Hi Chuck,
I agree about the decreasing stability of FlickType Classic with newer devices. I am happy to report that after I upgraded to iOS 16.0.2 this morning, FlickType Classic’s stability seems much closer to what it was under iOS 15.6.1. Regrettably, the confirmation prompt about allowing paste is appearing every time I paste into an app regardless of approving it the first time. This was a known iOS 16 bug that was supposed to have been corrected with 16.0.2, but it was not corrected for me when pasting from FlickType Classic which we must do quite often as you know. I’ll deal with this minor annoyance until it is corrected or I figure out some sort of workaround. I will add that I have a customized paste gesture of a 2 finger quadruple tap and I’ve read something on one of the lists that seemed to indicate those customized paste gestures might have contributed to the original bug. Who knows.
Take care and stay safe.
Alan
From: hello@flicktype.groups.io <hello@flicktype.groups.io> On Behalf Of Chuck Dean
Sent: Friday, September 23, 2022 11:35 AM
To: hello@flicktype.groups.io
Subject: Re: [FlickType] Caution against updating to iOS 16 for those using FlickType Classic
Hello Alan,
Thanks for that information. I haven't updated to 16 because I have heard about some bugs and there isn't anything the new iOS is offering that I am anxious to use.
I have noticed that FlickType classic is not as stable on my iPhone 13 as it is on my old iPhone 8.
Chuck (mobile)
Pleez x cuze enny tie ping or spelin air ores.
On Sep 23, 2022, at 9:11 AM, Alan Lemly <walemly@...> wrote:
Hi List,
I know this message will apply to very few considering FlickType Classic is no longer available. I was having great success using FlickType Classic on my iPhone 13 Mini running iOS 15.6.1. I upgraded to iOS 16 on 9/21/22 and this is no longer the case. I’m still able to open FlickType Classic and type into it but it is constantly doing things like changing the previously accepted word when I’ve started typing the next word. And its predictive engine doesn’t seem nearly as reliable as it was under iOS 15.6.1. I’m finding since the upgrade that it’s much faster to dictate and correct any errors than it is trying to successfully type the message with FlickType Classic.
This is very disappointing but I wanted others who might have not yet updated to iOS 16 to know.
Alan Lemly
On Sep 23, 2022, at 12:12 PM, Alan Lemly <walemly@...> wrote:
Hi Chuck,
I’m a bit confused by what you’re calling paste in the normal manner. If I paste by calling up the rotor, selecting edit and single finger swiping to paste followed by a double tap, the typed info from FlickType Classic pastes just fine without any confirmation of the paste. I believe the 2 finger double tap and hold you referenced is used to custom label an element but I’ve been known to confuse my gestures. Doing the rotor thing requires more gestures than simply using my custom paste gesture and approving the confirmation.
I’m getting the paste confirmation every time I do so with my custom gesture when the source text is coming from FlickType. However, I did just note that when I go to a text in process of being composed, use the rotor edit gesture to select all the text and copy it, and then paste it into a new text message using my custom paste gesture, I’m not prompted for the confirmation. But if I then jump back to FlickType, type something new, and go back to the text being composed, I’m again prompted for confirmation when using my custom paste gesture.
As I said before, I’ll keep playing with alternatives to see if I can ferret out a quicker workaround. All ideas are welcome.
Alan
From: hello@flicktype.groups.io <hello@flicktype.groups.io> On Behalf Of Chuck Dean
Sent: Friday, September 23, 2022 1:28 PM
To: hello@flicktype.groups.io
Subject: Re: [FlickType] Caution against updating to iOS 16 for those using FlickType Classic
Hello Alan,
You may want to try to paste in the normal manner without using the two finger quadruple tap. For example when after typing on FlickType, close the app, and then open what you want to paste it into double tap and hold until you hear the pass through gesture sound, and then flick right until you hear paste and then double tap. See if that stops the confirmation, and if it does then you’ll know it’s the two finger quadruple tap that’s causing the problem.
I also use the two finger quadruple tap for pasting, it works excellent!
Chuck (mobile)
Pleez x cuze enny tie ping or spelin air ores.
On Sep 23, 2022, at 10:55 AM, Alan Lemly <walemly@...> wrote:
Hi Chuck,
I agree about the decreasing stability of FlickType Classic with newer devices. I am happy to report that after I upgraded to iOS 16.0.2 this morning, FlickType Classic’s stability seems much closer to what it was under iOS 15.6.1. Regrettably, the confirmation prompt about allowing paste is appearing every time I paste into an app regardless of approving it the first time. This was a known iOS 16 bug that was supposed to have been corrected with 16.0.2, but it was not corrected for me when pasting from FlickType Classic which we must do quite often as you know. I’ll deal with this minor annoyance until it is corrected or I figure out some sort of workaround. I will add that I have a customized paste gesture of a 2 finger quadruple tap and I’ve read something on one of the lists that seemed to indicate those customized paste gestures might have contributed to the original bug. Who knows.
Take care and stay safe.
Alan
From: hello@flicktype.groups.io <hello@flicktype.groups.io> On Behalf Of Chuck Dean
Sent: Friday, September 23, 2022 11:35 AM
To: hello@flicktype.groups.io
Subject: Re: [FlickType] Caution against updating to iOS 16 for those using FlickType Classic
Hello Alan,
Thanks for that information. I haven't updated to 16 because I have heard about some bugs and there isn't anything the new iOS is offering that I am anxious to use.
I have noticed that FlickType classic is not as stable on my iPhone 13 as it is on my old iPhone 8.
Chuck (mobile)
Pleez x cuze enny tie ping or spelin air ores.
On Sep 23, 2022, at 9:11 AM, Alan Lemly <walemly@...> wrote:
Hi List,
I know this message will apply to very few considering FlickType Classic is no longer available. I was having great success using FlickType Classic on my iPhone 13 Mini running iOS 15.6.1. I upgraded to iOS 16 on 9/21/22 and this is no longer the case. I’m still able to open FlickType Classic and type into it but it is constantly doing things like changing the previously accepted word when I’ve started typing the next word. And its predictive engine doesn’t seem nearly as reliable as it was under iOS 15.6.1. I’m finding since the upgrade that it’s much faster to dictate and correct any errors than it is trying to successfully type the message with FlickType Classic.
This is very disappointing but I wanted others who might have not yet updated to iOS 16 to know.
Alan Lemly
Hi Daniel,
I think the problem is that Apple never bought anything from Kosta. As I understand it, they possibly copied some of his keyboard ingenuity especially where the watch is concerned and neglected to oversee bogus reviews of his app while allowing a wealth of inflated reviews of much less inferior competitor watch keyboards. That is why Kosta sued them which was recently settled as I understand things.
Alan Lemly
Sent: Friday, September 23, 2022 3:18 PM
To: hello@flicktype.groups.io
Subject: Re: [FlickType] Caution against updating to iOS 16 for those using FlickType Classic
Hi all
To be honest, since Apple brought the keyboard from Kosta and ported it to there watch 7th generation. I wish they would just now implement the keyboard Natively into IOS. So that we do have a quicker typing method across the system like we did a few years back.
Just my thoughts.
On 23 Sep 2022, at 20:12, Alan Lemly <walemly@...> wrote:
Hi Chuck,
I’m a bit confused by what you’re calling paste in the normal manner. If I paste by calling up the rotor, selecting edit and single finger swiping to paste followed by a double tap, the typed info from FlickType Classic pastes just fine without any confirmation of the paste. I believe the 2 finger double tap and hold you referenced is used to custom label an element but I’ve been known to confuse my gestures. Doing the rotor thing requires more gestures than simply using my custom paste gesture and approving the confirmation.
I’m getting the paste confirmation every time I do so with my custom gesture when the source text is coming from FlickType. However, I did just note that when I go to a text in process of being composed, use the rotor edit gesture to select all the text and copy it, and then paste it into a new text message using my custom paste gesture, I’m not prompted for the confirmation. But if I then jump back to FlickType, type something new, and go back to the text being composed, I’m again prompted for confirmation when using my custom paste gesture.
As I said before, I’ll keep playing with alternatives to see if I can ferret out a quicker workaround. All ideas are welcome.
Alan
From: hello@flicktype.groups.io <hello@flicktype.groups.io> On Behalf Of Chuck Dean
Sent: Friday, September 23, 2022 1:28 PM
To: hello@flicktype.groups.io
Subject: Re: [FlickType] Caution against updating to iOS 16 for those using FlickType Classic
Hello Alan,
You may want to try to paste in the normal manner without using the two finger quadruple tap. For example when after typing on FlickType, close the app, and then open what you want to paste it into double tap and hold until you hear the pass through gesture sound, and then flick right until you hear paste and then double tap. See if that stops the confirmation, and if it does then you’ll know it’s the two finger quadruple tap that’s causing the problem.
I also use the two finger quadruple tap for pasting, it works excellent!
Chuck (mobile)
Pleez x cuze enny tie ping or spelin air ores.
On Sep 23, 2022, at 10:55 AM, Alan Lemly <walemly@...> wrote:
Hi Chuck,
I agree about the decreasing stability of FlickType Classic with newer devices. I am happy to report that after I upgraded to iOS 16.0.2 this morning, FlickType Classic’s stability seems much closer to what it was under iOS 15.6.1. Regrettably, the confirmation prompt about allowing paste is appearing every time I paste into an app regardless of approving it the first time. This was a known iOS 16 bug that was supposed to have been corrected with 16.0.2, but it was not corrected for me when pasting from FlickType Classic which we must do quite often as you know. I’ll deal with this minor annoyance until it is corrected or I figure out some sort of workaround. I will add that I have a customized paste gesture of a 2 finger quadruple tap and I’ve read something on one of the lists that seemed to indicate those customized paste gestures might have contributed to the original bug. Who knows.
Take care and stay safe.
Alan
From: hello@flicktype.groups.io <hello@flicktype.groups.io> On Behalf Of Chuck Dean
Sent: Friday, September 23, 2022 11:35 AM
To: hello@flicktype.groups.io
Subject: Re: [FlickType] Caution against updating to iOS 16 for those using FlickType Classic
Hello Alan,
Thanks for that information. I haven't updated to 16 because I have heard about some bugs and there isn't anything the new iOS is offering that I am anxious to use.
I have noticed that FlickType classic is not as stable on my iPhone 13 as it is on my old iPhone 8.
Chuck (mobile)
Pleez x cuze enny tie ping or spelin air ores.
On Sep 23, 2022, at 9:11 AM, Alan Lemly <walemly@...> wrote:
Hi List,
I know this message will apply to very few considering FlickType Classic is no longer available. I was having great success using FlickType Classic on my iPhone 13 Mini running iOS 15.6.1. I upgraded to iOS 16 on 9/21/22 and this is no longer the case. I’m still able to open FlickType Classic and type into it but it is constantly doing things like changing the previously accepted word when I’ve started typing the next word. And its predictive engine doesn’t seem nearly as reliable as it was under iOS 15.6.1. I’m finding since the upgrade that it’s much faster to dictate and correct any errors than it is trying to successfully type the message with FlickType Classic.
This is very disappointing but I wanted others who might have not yet updated to iOS 16 to know.
Alan Lemly
On 23 Sep 2022, at 20:12, Alan Lemly <walemly@...> wrote:
Hi Chuck,
I’m a bit confused by what you’re calling paste in the normal manner. If I paste by calling up the rotor, selecting edit and single finger swiping to paste followed by a double tap, the typed info from FlickType Classic pastes just fine without any confirmation of the paste. I believe the 2 finger double tap and hold you referenced is used to custom label an element but I’ve been known to confuse my gestures. Doing the rotor thing requires more gestures than simply using my custom paste gesture and approving the confirmation.
I’m getting the paste confirmation every time I do so with my custom gesture when the source text is coming from FlickType. However, I did just note that when I go to a text in process of being composed, use the rotor edit gesture to select all the text and copy it, and then paste it into a new text message using my custom paste gesture, I’m not prompted for the confirmation. But if I then jump back to FlickType, type something new, and go back to the text being composed, I’m again prompted for confirmation when using my custom paste gesture.
As I said before, I’ll keep playing with alternatives to see if I can ferret out a quicker workaround. All ideas are welcome.
Alan
From: hello@flicktype.groups.io <hello@flicktype.groups.io> On Behalf Of Chuck Dean
Sent: Friday, September 23, 2022 1:28 PM
To: hello@flicktype.groups.io
Subject: Re: [FlickType] Caution against updating to iOS 16 for those using FlickType Classic
Hello Alan,
You may want to try to paste in the normal manner without using the two finger quadruple tap. For example when after typing on FlickType, close the app, and then open what you want to paste it into double tap and hold until you hear the pass through gesture sound, and then flick right until you hear paste and then double tap. See if that stops the confirmation, and if it does then you’ll know it’s the two finger quadruple tap that’s causing the problem.
I also use the two finger quadruple tap for pasting, it works excellent!
Chuck (mobile)
Pleez x cuze enny tie ping or spelin air ores.
On Sep 23, 2022, at 10:55 AM, Alan Lemly <walemly@...> wrote:
Hi Chuck,
I agree about the decreasing stability of FlickType Classic with newer devices. I am happy to report that after I upgraded to iOS 16.0.2 this morning, FlickType Classic’s stability seems much closer to what it was under iOS 15.6.1. Regrettably, the confirmation prompt about allowing paste is appearing every time I paste into an app regardless of approving it the first time. This was a known iOS 16 bug that was supposed to have been corrected with 16.0.2, but it was not corrected for me when pasting from FlickType Classic which we must do quite often as you know. I’ll deal with this minor annoyance until it is corrected or I figure out some sort of workaround. I will add that I have a customized paste gesture of a 2 finger quadruple tap and I’ve read something on one of the lists that seemed to indicate those customized paste gestures might have contributed to the original bug. Who knows.
Take care and stay safe.
Alan
From: hello@flicktype.groups.io <hello@flicktype.groups.io> On Behalf Of Chuck Dean
Sent: Friday, September 23, 2022 11:35 AM
To: hello@flicktype.groups.io
Subject: Re: [FlickType] Caution against updating to iOS 16 for those using FlickType Classic
Hello Alan,
Thanks for that information. I haven't updated to 16 because I have heard about some bugs and there isn't anything the new iOS is offering that I am anxious to use.
I have noticed that FlickType classic is not as stable on my iPhone 13 as it is on my old iPhone 8.
Chuck (mobile)
Pleez x cuze enny tie ping or spelin air ores.
On Sep 23, 2022, at 9:11 AM, Alan Lemly <walemly@...> wrote:
Hi List,
I know this message will apply to very few considering FlickType Classic is no longer available. I was having great success using FlickType Classic on my iPhone 13 Mini running iOS 15.6.1. I upgraded to iOS 16 on 9/21/22 and this is no longer the case. I’m still able to open FlickType Classic and type into it but it is constantly doing things like changing the previously accepted word when I’ve started typing the next word. And its predictive engine doesn’t seem nearly as reliable as it was under iOS 15.6.1. I’m finding since the upgrade that it’s much faster to dictate and correct any errors than it is trying to successfully type the message with FlickType Classic.
This is very disappointing but I wanted others who might have not yet updated to iOS 16 to know.
Alan Lemly
Hi Chuck,
I’m a bit confused by what you’re calling paste in the normal manner. If I paste by calling up the rotor, selecting edit and single finger swiping to paste followed by a double tap, the typed info from FlickType Classic pastes just fine without any confirmation of the paste. I believe the 2 finger double tap and hold you referenced is used to custom label an element but I’ve been known to confuse my gestures. Doing the rotor thing requires more gestures than simply using my custom paste gesture and approving the confirmation.
I’m getting the paste confirmation every time I do so with my custom gesture when the source text is coming from FlickType. However, I did just note that when I go to a text in process of being composed, use the rotor edit gesture to select all the text and copy it, and then paste it into a new text message using my custom paste gesture, I’m not prompted for the confirmation. But if I then jump back to FlickType, type something new, and go back to the text being composed, I’m again prompted for confirmation when using my custom paste gesture.
As I said before, I’ll keep playing with alternatives to see if I can ferret out a quicker workaround. All ideas are welcome.
Alan
Sent: Friday, September 23, 2022 1:28 PM
To: hello@flicktype.groups.io
Subject: Re: [FlickType] Caution against updating to iOS 16 for those using FlickType Classic
Hello Alan,
You may want to try to paste in the normal manner without using the two finger quadruple tap. For example when after typing on FlickType, close the app, and then open what you want to paste it into double tap and hold until you hear the pass through gesture sound, and then flick right until you hear paste and then double tap. See if that stops the confirmation, and if it does then you’ll know it’s the two finger quadruple tap that’s causing the problem.
I also use the two finger quadruple tap for pasting, it works excellent!
Chuck (mobile)
Pleez x cuze enny tie ping or spelin air ores.
On Sep 23, 2022, at 10:55 AM, Alan Lemly <walemly@...> wrote:
Hi Chuck,
I agree about the decreasing stability of FlickType Classic with newer devices. I am happy to report that after I upgraded to iOS 16.0.2 this morning, FlickType Classic’s stability seems much closer to what it was under iOS 15.6.1. Regrettably, the confirmation prompt about allowing paste is appearing every time I paste into an app regardless of approving it the first time. This was a known iOS 16 bug that was supposed to have been corrected with 16.0.2, but it was not corrected for me when pasting from FlickType Classic which we must do quite often as you know. I’ll deal with this minor annoyance until it is corrected or I figure out some sort of workaround. I will add that I have a customized paste gesture of a 2 finger quadruple tap and I’ve read something on one of the lists that seemed to indicate those customized paste gestures might have contributed to the original bug. Who knows.
Take care and stay safe.
Alan
From: hello@flicktype.groups.io <hello@flicktype.groups.io> On Behalf Of Chuck Dean
Sent: Friday, September 23, 2022 11:35 AM
To: hello@flicktype.groups.io
Subject: Re: [FlickType] Caution against updating to iOS 16 for those using FlickType Classic
Hello Alan,
Thanks for that information. I haven't updated to 16 because I have heard about some bugs and there isn't anything the new iOS is offering that I am anxious to use.
I have noticed that FlickType classic is not as stable on my iPhone 13 as it is on my old iPhone 8.
Chuck (mobile)
Pleez x cuze enny tie ping or spelin air ores.
On Sep 23, 2022, at 9:11 AM, Alan Lemly <walemly@...> wrote:
Hi List,
I know this message will apply to very few considering FlickType Classic is no longer available. I was having great success using FlickType Classic on my iPhone 13 Mini running iOS 15.6.1. I upgraded to iOS 16 on 9/21/22 and this is no longer the case. I’m still able to open FlickType Classic and type into it but it is constantly doing things like changing the previously accepted word when I’ve started typing the next word. And its predictive engine doesn’t seem nearly as reliable as it was under iOS 15.6.1. I’m finding since the upgrade that it’s much faster to dictate and correct any errors than it is trying to successfully type the message with FlickType Classic.
This is very disappointing but I wanted others who might have not yet updated to iOS 16 to know.
Alan Lemly
On Sep 23, 2022, at 10:55 AM, Alan Lemly <walemly@...> wrote:
Hi Chuck,
I agree about the decreasing stability of FlickType Classic with newer devices. I am happy to report that after I upgraded to iOS 16.0.2 this morning, FlickType Classic’s stability seems much closer to what it was under iOS 15.6.1. Regrettably, the confirmation prompt about allowing paste is appearing every time I paste into an app regardless of approving it the first time. This was a known iOS 16 bug that was supposed to have been corrected with 16.0.2, but it was not corrected for me when pasting from FlickType Classic which we must do quite often as you know. I’ll deal with this minor annoyance until it is corrected or I figure out some sort of workaround. I will add that I have a customized paste gesture of a 2 finger quadruple tap and I’ve read something on one of the lists that seemed to indicate those customized paste gestures might have contributed to the original bug. Who knows.
Take care and stay safe.
Alan
From: hello@flicktype.groups.io <hello@flicktype.groups.io> On Behalf Of Chuck Dean
Sent: Friday, September 23, 2022 11:35 AM
To: hello@flicktype.groups.io
Subject: Re: [FlickType] Caution against updating to iOS 16 for those using FlickType Classic
Hello Alan,
Thanks for that information. I haven't updated to 16 because I have heard about some bugs and there isn't anything the new iOS is offering that I am anxious to use.
I have noticed that FlickType classic is not as stable on my iPhone 13 as it is on my old iPhone 8.
Chuck (mobile)
Pleez x cuze enny tie ping or spelin air ores.
On Sep 23, 2022, at 9:11 AM, Alan Lemly <walemly@...> wrote:
Hi List,
I know this message will apply to very few considering FlickType Classic is no longer available. I was having great success using FlickType Classic on my iPhone 13 Mini running iOS 15.6.1. I upgraded to iOS 16 on 9/21/22 and this is no longer the case. I’m still able to open FlickType Classic and type into it but it is constantly doing things like changing the previously accepted word when I’ve started typing the next word. And its predictive engine doesn’t seem nearly as reliable as it was under iOS 15.6.1. I’m finding since the upgrade that it’s much faster to dictate and correct any errors than it is trying to successfully type the message with FlickType Classic.
This is very disappointing but I wanted others who might have not yet updated to iOS 16 to know.
Alan Lemly
On Sep 23, 2022, at 1:20 PM, Alan Lemly <walemly@...> wrote:
Hi Benny,
I quit with the standard FlickType or FlickType Watch app or whatever they
started calling it after I found I was still able to get the FlickType
Classic app. I never had anything but problems with the standard app so it's
no longer on my iPhone. Sorry.
Alan
-----Original Message-----
From: hello@flicktype.groups.io <hello@flicktype.groups.io> On Behalf Of
Benny Barber
Sent: Friday, September 23, 2022 12:53 PM
To: hello@flicktype.groups.io
Subject: Re: [FlickType] Caution against updating to iOS 16 for those using
FlickType Classic
Alan,
Have you tried the standard FlickType app with iOS 16? If so, what was the
results? Thanks.
Benny
On Sep 23, 2022, at 10:55 AM, Alan Lemly <walemly@...> wrote:
Hi Chuck,
I agree about the decreasing stability of FlickType Classic with newer devices. I am happy to report that after I upgraded to iOS 16.0.2 this morning, FlickType Classic’s stability seems much closer to what it was under iOS 15.6.1. Regrettably, the confirmation prompt about allowing paste is appearing every time I paste into an app regardless of approving it the first time. This was a known iOS 16 bug that was supposed to have been corrected with 16.0.2, but it was not corrected for me when pasting from FlickType Classic which we must do quite often as you know. I’ll deal with this minor annoyance until it is corrected or I figure out some sort of workaround. I will add that I have a customized paste gesture of a 2 finger quadruple tap and I’ve read something on one of the lists that seemed to indicate those customized paste gestures might have contributed to the original bug. Who knows.
Take care and stay safe.
Alan
From: hello@flicktype.groups.io <hello@flicktype.groups.io> On Behalf Of Chuck Dean
Sent: Friday, September 23, 2022 11:35 AM
To: hello@flicktype.groups.io
Subject: Re: [FlickType] Caution against updating to iOS 16 for those using FlickType Classic
Hello Alan,
Thanks for that information. I haven't updated to 16 because I have heard about some bugs and there isn't anything the new iOS is offering that I am anxious to use.
I have noticed that FlickType classic is not as stable on my iPhone 13 as it is on my old iPhone 8.
Chuck (mobile)
Pleez x cuze enny tie ping or spelin air ores.
On Sep 23, 2022, at 9:11 AM, Alan Lemly <walemly@...> wrote:
Hi List,
I know this message will apply to very few considering FlickType Classic is no longer available. I was having great success using FlickType Classic on my iPhone 13 Mini running iOS 15.6.1. I upgraded to iOS 16 on 9/21/22 and this is no longer the case. I’m still able to open FlickType Classic and type into it but it is constantly doing things like changing the previously accepted word when I’ve started typing the next word. And its predictive engine doesn’t seem nearly as reliable as it was under iOS 15.6.1. I’m finding since the upgrade that it’s much faster to dictate and correct any errors than it is trying to successfully type the message with FlickType Classic.
This is very disappointing but I wanted others who might have not yet updated to iOS 16 to know.
Alan Lemly
On Sep 23, 2022, at 11:20 AM, Alan Lemly <walemly@...> wrote:
Hi Benny,
I quit with the standard FlickType or FlickType Watch app or whatever they
started calling it after I found I was still able to get the FlickType
Classic app. I never had anything but problems with the standard app so it's
no longer on my iPhone. Sorry.
Alan
-----Original Message-----
From: hello@flicktype.groups.io <hello@flicktype.groups.io> On Behalf Of
Benny Barber
Sent: Friday, September 23, 2022 12:53 PM
To: hello@flicktype.groups.io
Subject: Re: [FlickType] Caution against updating to iOS 16 for those using
FlickType Classic
Alan,
Have you tried the standard FlickType app with iOS 16? If so, what was the
results? Thanks.
Benny
I quit with the standard FlickType or FlickType Watch app or whatever they
started calling it after I found I was still able to get the FlickType
Classic app. I never had anything but problems with the standard app so it's
no longer on my iPhone. Sorry.
Alan
From: hello@flicktype.groups.io <hello@flicktype.groups.io> On Behalf Of
Benny Barber
Sent: Friday, September 23, 2022 12:53 PM
To: hello@flicktype.groups.io
Subject: Re: [FlickType] Caution against updating to iOS 16 for those using
FlickType Classic
Alan,
Have you tried the standard FlickType app with iOS 16? If so, what was the
results? Thanks.
Benny
Hi Chuck,
I agree about the decreasing stability of FlickType Classic with newer devices. I am happy to report that after I upgraded to iOS 16.0.2 this morning, FlickType Classic’s stability seems much closer to what it was under iOS 15.6.1. Regrettably, the confirmation prompt about allowing paste is appearing every time I paste into an app regardless of approving it the first time. This was a known iOS 16 bug that was supposed to have been corrected with 16.0.2, but it was not corrected for me when pasting from FlickType Classic which we must do quite often as you know. I’ll deal with this minor annoyance until it is corrected or I figure out some sort of workaround. I will add that I have a customized paste gesture of a 2 finger quadruple tap and I’ve read something on one of the lists that seemed to indicate those customized paste gestures might have contributed to the original bug. Who knows.
Take care and stay safe.
Alan
Sent: Friday, September 23, 2022 11:35 AM
To: hello@flicktype.groups.io
Subject: Re: [FlickType] Caution against updating to iOS 16 for those using FlickType Classic
Hello Alan,
Thanks for that information. I haven't updated to 16 because I have heard about some bugs and there isn't anything the new iOS is offering that I am anxious to use.
I have noticed that FlickType classic is not as stable on my iPhone 13 as it is on my old iPhone 8.
Chuck (mobile)
Pleez x cuze enny tie ping or spelin air ores.
On Sep 23, 2022, at 9:11 AM, Alan Lemly <walemly@...> wrote:
Hi List,
I know this message will apply to very few considering FlickType Classic is no longer available. I was having great success using FlickType Classic on my iPhone 13 Mini running iOS 15.6.1. I upgraded to iOS 16 on 9/21/22 and this is no longer the case. I’m still able to open FlickType Classic and type into it but it is constantly doing things like changing the previously accepted word when I’ve started typing the next word. And its predictive engine doesn’t seem nearly as reliable as it was under iOS 15.6.1. I’m finding since the upgrade that it’s much faster to dictate and correct any errors than it is trying to successfully type the message with FlickType Classic.
This is very disappointing but I wanted others who might have not yet updated to iOS 16 to know.
Alan Lemly
On Sep 23, 2022, at 9:11 AM, Alan Lemly <walemly@...> wrote:
Hi List,
I know this message will apply to very few considering FlickType Classic is no longer available. I was having great success using FlickType Classic on my iPhone 13 Mini running iOS 15.6.1. I upgraded to iOS 16 on 9/21/22 and this is no longer the case. I’m still able to open FlickType Classic and type into it but it is constantly doing things like changing the previously accepted word when I’ve started typing the next word. And its predictive engine doesn’t seem nearly as reliable as it was under iOS 15.6.1. I’m finding since the upgrade that it’s much faster to dictate and correct any errors than it is trying to successfully type the message with FlickType Classic.
This is very disappointing but I wanted others who might have not yet updated to iOS 16 to know.
Alan Lemly
Hi List,
I know this message will apply to very few considering FlickType Classic is no longer available. I was having great success using FlickType Classic on my iPhone 13 Mini running iOS 15.6.1. I upgraded to iOS 16 on 9/21/22 and this is no longer the case. I’m still able to open FlickType Classic and type into it but it is constantly doing things like changing the previously accepted word when I’ve started typing the next word. And its predictive engine doesn’t seem nearly as reliable as it was under iOS 15.6.1. I’m finding since the upgrade that it’s much faster to dictate and correct any errors than it is trying to successfully type the message with FlickType Classic.
This is very disappointing but I wanted others who might have not yet updated to iOS 16 to know.
Alan Lemly