Note: groups.io will be down for maintenance on Monday, September 26th, starting at 9AM Pacific Time (4PM Monday September 26, 2022 UTC), for approximately one hour.
|
Re: 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
From: hello@flicktype.groups.io <hello@flicktype.groups.io> On Behalf Of Chuck Dean 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 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. 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 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! 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 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. 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
|
|
|
Re: 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 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! 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 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. 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
|
|
|
Re: Caution against updating to iOS 16 for those using FlickType Classic
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
From: hello@flicktype.groups.io <hello@flicktype.groups.io> On Behalf Of Daniel McGee 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 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.
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 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! 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 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. 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
|
|
|
Re: 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 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! 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 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. 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
|
|
|
Re: Caution against updating to iOS 16 for those using FlickType Classic
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 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! 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 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. 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
|
|
|
Re: Caution against updating to iOS 16 for those using FlickType Classic
Hello Alan, I have found that overall my iPhone 13 is more sensitive and a little harder for me to operate accurately. I do not know if this is because my old fingers are not as stable as in the past, but using my old iPhone 8 is more positive. 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 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. 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
|
|
|
Re: Caution against updating to iOS 16 for those using FlickType Classic
Thanks, Alan. I appreciate the reply.
toggle quoted messageShow quoted text
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
|
|
|
Re: 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 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. 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
|
|
|
Re: Caution against updating to iOS 16 for those using FlickType Classic
Hello, I agree with Alan, after the whole debacle with Fliktype and it was gone for a while and then came back as the “watch app“ I had nothing but problems with it. It was never very stable. The Fliktype classic app always worked perfectly, and even though you have to copy and paste the text out of it, it still was, in my opinion, the very best version of Fliktype. The other problem I have even testing with the FlickType watch app, is that when I loaded onto my phone it seems to have the dictionary that was on that particular app loaded into my phone someplace, and it bogs down FlickType Classic with a bunch of unnecessary words.
Chuck (mobile) Pleez x cuze enny tie ping or spelin air ores.
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
|
|
|
Re: Caution against updating to iOS 16 for those using FlickType Classic
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
toggle quoted messageShow quoted text
-----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
|
|
|
Re: Caution against updating to iOS 16 for those using FlickType Classic
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 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. 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
|
|
|
Re: 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
|
|
|
Re: 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
|
|
|
Caution against updating to iOS 16 for those using FlickType Classic
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
|
|
|
Re: Clearing the dictionary
Hi Daniel,
I believe this issue with the dictionary is another problem with FlickType
no longer being adequately maintained by Kosta. I was never able to keep my
3000+ custom dictionary entries from returning without removing the
FlickType Watch app from my iPhone. I'm just thankful I still have access to
FlickType Classic which works much better than the old FlickType Keyboard
ever did.
Alan Lemly
toggle quoted messageShow quoted text
-----Original Message-----
From: hello@flicktype.groups.io <hello@flicktype.groups.io> On Behalf Of
Daniel McGee
Sent: Monday, January 31, 2022 4:54 PM
To: hello@flicktype.groups.io
Subject: [FlickType] Clearing the dictionary
Hello all
I have 1 thousand words in my flicktype dictionary. If I use the clear all
button. I have noticed, that for the duration of the time FlickType is
running in the app switcher. All the words in the dictionary remain cleared.
However, if I close the app and Re-launch it again. All my dictionary
entries suddenly appear back.
Does anyone know of a way to if not clear all words then at least trim down
the dictionary. Because it does have an impact on how long the app takes to
load up. Especially, when using low power mode.
iPhone XR Software Version 14.8.1
Regards
Daniel
|
|
|
Hello all
I have 1 thousand words in my flicktype dictionary. If I use the clear all button. I have noticed, that for the duration of the time FlickType is running in the app switcher. All the words in the dictionary remain cleared.
However, if I close the app and Re-launch it again. All my dictionary entries suddenly appear back.
Does anyone know of a way to if not clear all words then at least trim down the dictionary. Because it does have an impact on how long the app takes to load up. Especially, when using low power mode.
iPhone XR Software Version 14.8.1
Regards
Daniel
|
|
|
Re: My experience with FlickType Watch app post iOS 15.3 update
Hi All,
When I first began with FlickType, I had the original classic version. However, when the Apple Watch version was released, it installed over the classic version. Frown!! So, when experts on this list suggested to change the settings to have the text copy to the clipboard and assign a gesture to paste it where I wanted it to go, I hopped on it immediately. Thanks Chuck and others for that solution. It works like a charm and a great work around. I too would like the classic version to be once again in the app store, so I could download it again. Will take your advice Chuck and will email Kosla. It just may take a village to convince him to do it.
Thanks in advance.
|
|
|
Re: My experience with FlickType Watch app post iOS 15.3 update
Hello Samantha, I’m sorry, but the FlickType Classic app is no longer available. As the name implies, it was the original version of FlickType, and app that you could type and export text to various other text fields. When Kosta developed the FlickType that would work in various text fields, most people moved to it. For a short period of time however, and I don’t remember exactly what happened, he gave us a FlickType Classic as a stopgap measure for when the Fliktype extension was not working well. I think it was only in App Store for about a month or two.
In my opinion, and I did a lot of typing on FlickType, it is by far the best incarnation of Fliktype. It works perfectly every time! It works with every iOS!, And it is actually a faster typing keyboard than any of the other versions of Fliktype! Flicktype extension keyboard worked in about 99% of all text fields, but there were a few that it did not work in well. But Fliktype classic works perfectly all the time! There are a few gestures that are different in FlickType Classic, for example you cannot insert a line by swiping right and holding, you have to hit the new line button in the lower right hand corner, and a few other things are different, but as far as I’m concerned, it’s the best!
My suggestion is anybody who wants to get Fliktype classic right to Kosta at hello@..., and perhaps if enough people will ask, maybe he can put it back into the App Store as a stopgap measure. I’ve sent a few emails to Kosta asking him to restore it in the App Store, and even offered to buy it from him and rebrand it as something else, but for some reason he doesn’t want to. It’s his baby, it’s his prerogative! Chuck (mobile) Pleez x cuze enny tie ping or spelin air ores.
On Jan 27, 2022, at 2:16 PM, Samanthia Farthing via groups.io <sammy_farthing@...> wrote:
Actually I have never been able to find the FlickType classic app. I was a beta tester for a long time, so I thought that version was the same as the classic app you've talked about, but it doesn't show up in my purchased apps, and I can't find it when I just search for it in the app store either. If anyone can provide a link to FlickType classic. I'd really appreciate it. On Jan 27, 2022, at 3:58 PM, Chuck Dean <cadean329@...> wrote:
Another problem I had with the FlickType watch app is every time I opened it, it took over two minutes to load and then populated my FlickType Classic app with a three thousand word custom dictionary which also made FlickType Classic load very slowly. Also the iPhone got hot while each app loaded. After many attempts I finally was able to clear the dictionary, which cleared on both apps. I deleted the FlickType watch app and only use my favorite version of FlickType... FlickType Classic. It should be in the app store! Chuck (mobile) Pleez x cuze enny tie ping or spelin air ores.
On Jan 27, 2022, at 10:36 AM, Alan Lemly <walemly@...> wrote:
Hi List, I agree that the FlickType Watch app is better after the iOS 15.3 upgrade on my iPhone 13 Mini. However, I still noticed that the first typed word using it isn’t pronounced correctly and it doesn’t speak the period typed at the end of any sentence. It does speak later words correctly and any that are announced as predictive alternatives as you single finger flick down. It seemed much slower on my iPhone than FlickType Classic and its keyboard for typing did not seem to appear as quickly or as reliably as I would like. I uninstalled it after testing it. Alan Lemly
|
|
|
Re: My experience with FlickType Watch app post iOS 15.3 update
Actually I have never been able to find the FlickType classic app. I was a beta tester for a long time, so I thought that version was the same as the classic app you've talked about, but it doesn't show up in my purchased apps, and I can't find it when I just search for it in the app store either. If anyone can provide a link to FlickType classic. I'd really appreciate it.
On Jan 27, 2022, at 3:58 PM, Chuck Dean <cadean329@...> wrote:
Another problem I had with the FlickType watch app is every time I opened it, it took over two minutes to load and then populated my FlickType Classic app with a three thousand word custom dictionary which also made FlickType Classic load very slowly. Also the iPhone got hot while each app loaded. After many attempts I finally was able to clear the dictionary, which cleared on both apps. I deleted the FlickType watch app and only use my favorite version of FlickType... FlickType Classic. It should be in the app store! Chuck (mobile) Pleez x cuze enny tie ping or spelin air ores.
On Jan 27, 2022, at 10:36 AM, Alan Lemly <walemly@...> wrote:
Hi List, I agree that the FlickType Watch app is better after the iOS 15.3 upgrade on my iPhone 13 Mini. However, I still noticed that the first typed word using it isn’t pronounced correctly and it doesn’t speak the period typed at the end of any sentence. It does speak later words correctly and any that are announced as predictive alternatives as you single finger flick down. It seemed much slower on my iPhone than FlickType Classic and its keyboard for typing did not seem to appear as quickly or as reliably as I would like. I uninstalled it after testing it. Alan Lemly
|
|
|
Re: My experience with FlickType Watch app post iOS 15.3 update
Another problem I had with the FlickType watch app is every time I opened it, it took over two minutes to load and then populated my FlickType Classic app with a three thousand word custom dictionary which also made FlickType Classic load very slowly. Also the iPhone got hot while each app loaded. After many attempts I finally was able to clear the dictionary, which cleared on both apps. I deleted the FlickType watch app and only use my favorite version of FlickType... FlickType Classic. It should be in the app store! Chuck (mobile) Pleez x cuze enny tie ping or spelin air ores.
On Jan 27, 2022, at 10:36 AM, Alan Lemly <walemly@...> wrote:
Hi List, I agree that the FlickType Watch app is better after the iOS 15.3 upgrade on my iPhone 13 Mini. However, I still noticed that the first typed word using it isn’t pronounced correctly and it doesn’t speak the period typed at the end of any sentence. It does speak later words correctly and any that are announced as predictive alternatives as you single finger flick down. It seemed much slower on my iPhone than FlickType Classic and its keyboard for typing did not seem to appear as quickly or as reliably as I would like. I uninstalled it after testing it. Alan Lemly
|
|
|
