Date   

Re: Cannot upgrade FlickType.

David Nason
 

Yeah I found that inactive label on the upgrade tab a little confusing too at first.

Dave

On 27 Jun 2018, at 17:13, Chuck Dean <cadean329@...> wrote:

OK👌
The upgrade button at the top right did the trick!

Thanks,
Chuck

On Jun 27, 2018, at 9:09 AM, FlickType <@FlickType> wrote:

Hi Chuck,

There’s the upgrade tab option at the bottom, but then there’s also an upgrade button at the top right of that tab’s view, opposite from the restore one. Does that help, or is that button inactive too for some reason?

Kosta

On Jun 27, 2018, at 09:06, Chuck Dean <cadean329@...> wrote:

Cannot upgrade FlickType.
Hi Kosta,
I downloaded the FlickType app from the app store, but the upgrade button is inactive, and when I click on the restore button it says I do not have a subscription.
When I tried to type it said I didn't have a subscription.
Chuck





Re: Cannot upgrade FlickType.

Chuck Dean
 

OK👌
The upgrade button at the top right did the trick!

Thanks,
Chuck

On Jun 27, 2018, at 9:09 AM, FlickType <@FlickType> wrote:

Hi Chuck,

There’s the upgrade tab option at the bottom, but then there’s also an upgrade button at the top right of that tab’s view, opposite from the restore one. Does that help, or is that button inactive too for some reason?

Kosta

On Jun 27, 2018, at 09:06, Chuck Dean <cadean329@...> wrote:

Cannot upgrade FlickType.
Hi Kosta,
I downloaded the FlickType app from the app store, but the upgrade button is inactive, and when I click on the restore button it says I do not have a subscription.
When I tried to type it said I didn't have a subscription.
Chuck




Re: Cannot upgrade FlickType.

 

Hi Chuck,

There’s the upgrade tab option at the bottom, but then there’s also an upgrade button at the top right of that tab’s view, opposite from the restore one. Does that help, or is that button inactive too for some reason?

Kosta

On Jun 27, 2018, at 09:06, Chuck Dean <cadean329@...> wrote:

Cannot upgrade FlickType.
Hi Kosta,
I downloaded the FlickType app from the app store, but the upgrade button is inactive, and when I click on the restore button it says I do not have a subscription.
When I tried to type it said I didn't have a subscription.
Chuck



Cannot upgrade FlickType.

Chuck Dean
 

Cannot upgrade FlickType.
Hi Kosta,
I downloaded the FlickType app from the app store, but the upgrade button is inactive, and when I click on the restore button it says I do not have a subscription.
When I tried to type it said I didn't have a subscription.
Chuck


Re: Checking in

Salman Haider
 

Sounds good, thank you.

On 6/26/18, FlickType <@FlickType> wrote:
Thank you Salman, this will be fixed soon.

- Kosta




On Mon, Jun 25, 2018 at 4:39 AM Salman Haider
<salmanhaider.purdue@...>
wrote:

Hi Kosta,

I also wanted to mention an issue that I have encountered quite often
while attempting to manually enter text. I do believe that it has been
mentioned before; when manually typing, the incorrect letter is
entered sometimes. As in, the adjacent letter to the left or right is
entered rather than the one that you wanted to enter. This can get
very frustrating as one needs to keep deleting and then attempt to
enter the right character again, and it may be multiple times before
the correct one is entered.
Is a fix for this coming soon?

Salman

On 6/25/18, Benny Barber <rebelben@...> wrote:
Kosta,

I am still on build 105 and will be installing 108 within the next
hour.
Yes, I am still having issues with flicking through the alternative
word
list. As stated earlier, sometimes while flicking down through the
list, I
will get the click sound and a single letter will be entered. I then
delete
that letter and continue flicking down through the original word list.
I
think maybe one time I had that occur when flicking with 2 fingers
right
and
left through the typed message word by word, but the issue happens very
often flicking through the alternative word list.

I have not had any text missing on 105 and I will be testing more on
108.
If you can figure out the alternative word list flicking problem, it
sure
would be great. It sure does slow down the typing when I have to
delete
pretty often. Thanks for the great work. I'll let you know if I find
anything else.

Benny

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On
Behalf
Of FlickType
Sent: Sunday, June 24, 2018 11:43 PM
To: alpha@flicktype.groups.io
Subject: [FlickType-alpha] Checking in

Hi Benny, Dan and Paul, I just wanted to check in and see if you have
an
update on any of the major issues you reported.
Thank you,
Kosta











Re: Build 111 flick and hold not working as well.

Chuck Dean
 

Hi Kosta,
I tried to duplicate the flick and hold problem in 110, but could not.
I updated to Build 111 and I still haven't seen the odd behavior.
Perhaps it was just a fluke.
Chuck

On Jun 26, 2018, at 7:26 PM, Chuck Dean <cadean329@...> wrote:


Hi Kosta,
I reverted to Build 110. I haven't seen the problem, however, I haven't seen the problem with the flick and hold since this morning. It only happened a couple of times, and I haven't been able to reproduce since.
I'll run 110 for a while and see what happens.
Chuck

On Jun 26, 2018, at 7:05 PM, FlickType <@FlickType> wrote:

Thank you Chuck. If it's not too much trouble, can you please switch
back to build 110 and confirm that the issue is definitely not present
there? I'm only asking because these gesture issues have been very
hard to reproduce here, and everyone has their own unique way of
performing the gestures.

- Kosta




Re: Build 111 flick and hold not working as well.

Chuck Dean
 

Hi Kosta,
I reverted to Build 110. I haven't seen the problem, however, I haven't seen the problem with the flick and hold since this morning. It only happened a couple of times, and I haven't been able to reproduce since.
I'll run 110 for a while and see what happens.
Chuck

On Jun 26, 2018, at 7:05 PM, FlickType <@FlickType> wrote:

Thank you Chuck. If it's not too much trouble, can you please switch
back to build 110 and confirm that the issue is definitely not present
there? I'm only asking because these gesture issues have been very
hard to reproduce here, and everyone has their own unique way of
performing the gestures.

- Kosta



Re: Build 111 flick and hold not working as well.

George Cham
 

I found that when performing the gestured, it will depend on if my finger is wet from water, or the  surface of the device.

Kind Regards,

George Cham

‘May the Lord bless you and protect you. May the Lord smile on you and be gracious to you. May the Lord show you his favor and give you his peace.’
Numbers 6:24-26
Get Outlook for iOS


From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Chuck Dean <cadean329@...>
Sent: Wednesday, June 27, 2018 12:02:33 PM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 111 flick and hold not working as well.
 

I never had any issues before 111.

> On Jun 26, 2018, at 6:17 PM, FlickType <hello@...> wrote:
>
> Do you think the flick and hold gesture issue is definitely new with build 111?
>
> - Kosta
>
>
>> On Tue, Jun 26, 2018 at 1:21 PM Chuck Dean <cadean329@...> wrote:
>>
>>
>> Hi Kosta.
>> Yes, it was like I was manually entering letters, when I flicked down.
>> When I did a flick up and hold, it didn't do anything. I had to perform the gesture a couple of times.
>>
>> Chuck
>>
>>> On Jun 26, 2018, at 1:12 PM, FlickType <hello@...> wrote:
>>>
>>> Thank you Chuck. When you say the flick and hold is not working well,
>>> what does it do instead? Does it enter a character? Let us know if you
>>> figure out any pattern.
>>>
>>> - Kosta
>>>> On Tue, Jun 26, 2018 at 10:41 AM Chuck Dean <cadean329@...> wrote:
>>>>
>>>>
>>>> Hi Kosta,
>>>> I also noticed the flick and hold is not working well all the time. I have had it not work both when dismissing the keyboard and changing to the iOS keyboard.
>>>> I am not sure what it is doing, and I cannot duplicate the problem.
>>>> Chuck
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>
>
>




Re: Build 111 flick and hold not working as well.

 

Thank you Chuck. If it's not too much trouble, can you please switch
back to build 110 and confirm that the issue is definitely not present
there? I'm only asking because these gesture issues have been very
hard to reproduce here, and everyone has their own unique way of
performing the gestures.

- Kosta


Re: Build 111 flick and hold not working as well.

Chuck Dean
 

I never had any issues before 111.

On Jun 26, 2018, at 6:17 PM, FlickType <@FlickType> wrote:

Do you think the flick and hold gesture issue is definitely new with build 111?

- Kosta


On Tue, Jun 26, 2018 at 1:21 PM Chuck Dean <cadean329@...> wrote:


Hi Kosta.
Yes, it was like I was manually entering letters, when I flicked down.
When I did a flick up and hold, it didn't do anything. I had to perform the gesture a couple of times.

Chuck

On Jun 26, 2018, at 1:12 PM, FlickType <@FlickType> wrote:

Thank you Chuck. When you say the flick and hold is not working well,
what does it do instead? Does it enter a character? Let us know if you
figure out any pattern.

- Kosta
On Tue, Jun 26, 2018 at 10:41 AM Chuck Dean <cadean329@...> wrote:


Hi Kosta,
I also noticed the flick and hold is not working well all the time. I have had it not work both when dismissing the keyboard and changing to the iOS keyboard.
I am not sure what it is doing, and I cannot duplicate the problem.
Chuck





Re: Build 111 flick and hold not working as well.

 

Thank you Benny. The question was for everyone. I also agree that the
flick and hold gestures can be tricky to perform as reliably as other
gestures. If anyone can confirm that the issue with those gestures is
new to a particular build, I can investigate further. Otherwise it
might be better to wait until there's more user reports, since the
investigation can take a lot of time that might be better spent
elsewhere. Please let me know, and thank you for all the reports.

- Kosta


Re: Build 111 flick and hold not working as well.

Benny Barber
 

If this question was intended for only Chuck, I apologize. To me the gestures seem to be about the same. With that said, all of the flick and hold gestures are a little tricky. I occasionally will activate the touch typing mode. I can deal with them, but they are my least favorite gestures. Thanks.
Benny

On Jun 26, 2018, at 8:17 PM, FlickType <@FlickType> wrote:

Do you think the flick and hold gesture issue is definitely new with build 111?

- Kosta


On Tue, Jun 26, 2018 at 1:21 PM Chuck Dean <cadean329@...> wrote:


Hi Kosta.
Yes, it was like I was manually entering letters, when I flicked down.
When I did a flick up and hold, it didn't do anything. I had to perform the gesture a couple of times.

Chuck

On Jun 26, 2018, at 1:12 PM, FlickType <@FlickType> wrote:

Thank you Chuck. When you say the flick and hold is not working well,
what does it do instead? Does it enter a character? Let us know if you
figure out any pattern.

- Kosta
On Tue, Jun 26, 2018 at 10:41 AM Chuck Dean <cadean329@...> wrote:


Hi Kosta,
I also noticed the flick and hold is not working well all the time. I have had it not work both when dismissing the keyboard and changing to the iOS keyboard.
I am not sure what it is doing, and I cannot duplicate the problem.
Chuck





Re: Build 111 flick and hold not working as well.

George Cham
 

costa, I've had no problems with the flick down and hold gesture.

Kind Regards,

George Cham

‘May the Lord bless you and protect you. May the Lord smile on you and be gracious to you. May the Lord show you his favor and give you his peace.’
Numbers 6:24-26
Get Outlook for iOS


From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of FlickType <hello@...>
Sent: Wednesday, June 27, 2018 11:17:35 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 111 flick and hold not working as well.
 
Do you think the flick and hold gesture issue is definitely new with build 111?

- Kosta


On Tue, Jun 26, 2018 at 1:21 PM Chuck Dean <cadean329@...> wrote:
>
>
> Hi Kosta.
>  Yes, it was like I was manually entering letters, when I flicked down.
>  When I did a flick up and hold, it didn't do anything. I had to perform the gesture a couple of times.
>
>  Chuck
>
> > On Jun 26, 2018, at 1:12 PM, FlickType <hello@...> wrote:
> >
> > Thank you Chuck. When you say the flick and hold is not working well,
> > what does it do instead? Does it enter a character? Let us know if you
> > figure out any pattern.
> >
> > - Kosta
> >> On Tue, Jun 26, 2018 at 10:41 AM Chuck Dean <cadean329@...> wrote:
> >>
> >>
> >> Hi Kosta,
> >> I also noticed the flick and hold is not working well all the time. I have had it not work both when dismissing the keyboard and changing to the iOS keyboard.
> >> I am not sure what it is doing, and I cannot duplicate the problem.
> >> Chuck
> >>
> >>
> >
> >
> >
>
>
>




Re: Build 111 flick and hold not working as well.

 

Do you think the flick and hold gesture issue is definitely new with build 111?

- Kosta

On Tue, Jun 26, 2018 at 1:21 PM Chuck Dean <cadean329@...> wrote:


Hi Kosta.
Yes, it was like I was manually entering letters, when I flicked down.
When I did a flick up and hold, it didn't do anything. I had to perform the gesture a couple of times.

Chuck

On Jun 26, 2018, at 1:12 PM, FlickType <@FlickType> wrote:

Thank you Chuck. When you say the flick and hold is not working well,
what does it do instead? Does it enter a character? Let us know if you
figure out any pattern.

- Kosta
On Tue, Jun 26, 2018 at 10:41 AM Chuck Dean <cadean329@...> wrote:


Hi Kosta,
I also noticed the flick and hold is not working well all the time. I have had it not work both when dismissing the keyboard and changing to the iOS keyboard.
I am not sure what it is doing, and I cannot duplicate the problem.
Chuck




Re: Build 111

George Cham
 

Ok. Looks like I'm wrong. I have the extra emoji on my I phone. And they are still there. However, it seems like I did not add the emoji into settings on I pad

Kind regards,

George Cham

‘May the Lord bless you and protect you. May the Lord smile on you and be gracious to you. May the Lord show you his favor and give you his peace.’
Numbers 6:24-26
Get Outlook for iOS


From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of George Cham <George.cham@...>
Sent: Wednesday, June 27, 2018 9:38:31 AM
To: alpha@flicktype.groups.io; alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 111
 
Costa, the emoji that I said that I had lost in previous builds have gone again☹️

Kind Regards,

George Cham

‘May the Lord bless you and protect you. May the Lord smile on you and be gracious to you. May the Lord show you his favor and give you his peace.’
Numbers 6:24-26
Get Outlook for iOS

From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Benny Barber <rebelben@...>
Sent: Wednesday, June 27, 2018 6:31:54 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 111
 

 Kosta,
 This problem is occurring while never leaving FlickType. It seems to happen on lengthy messages and checking the text with the 3 finger hole multiple times. Thanks.
 Benny

> On Jun 26, 2018, at 3:20 PM, FlickType <hello@...> wrote:
>
> Thank you Benny. On the 3 finger hold to read back, there are some limitations that we hope to overcome in the future. FlickType will only be able to read back text that it knows is there, and if you happen to switch keyboards or more generally switch to FlickType to edit or append existing text, iOS will not tell us what the entire contents of the text field are. Instead, we will only get the one or two sentences nearest to where the cursor is. This is the same reason why sometimes you might be unable to move the cursor past a sentence boundary, even though there might be more text in the underlying textfield. From this it also follows that the text that you read back is also the text that you can move the FlickType cursor through.
>
> And if, for example, you start typing with FlickType on a blank textfield, and never switch out of FlickType until you are done, you should always be able to read back everything that you have typed.
>
> Hope this makes some sense, and please let us know if you are still experiencing something unexpected.
>
> Thanks,
> Kosta
>
>
>
>





Re: Build 111

George Cham
 

Costa, the emoji that I said that I had lost in previous builds have gone again☹️

Kind Regards,

George Cham

‘May the Lord bless you and protect you. May the Lord smile on you and be gracious to you. May the Lord show you his favor and give you his peace.’
Numbers 6:24-26
Get Outlook for iOS


From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Benny Barber <rebelben@...>
Sent: Wednesday, June 27, 2018 6:31:54 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 111
 

 Kosta,
 This problem is occurring while never leaving FlickType. It seems to happen on lengthy messages and checking the text with the 3 finger hole multiple times. Thanks.
 Benny

> On Jun 26, 2018, at 3:20 PM, FlickType <hello@...> wrote:
>
> Thank you Benny. On the 3 finger hold to read back, there are some limitations that we hope to overcome in the future. FlickType will only be able to read back text that it knows is there, and if you happen to switch keyboards or more generally switch to FlickType to edit or append existing text, iOS will not tell us what the entire contents of the text field are. Instead, we will only get the one or two sentences nearest to where the cursor is. This is the same reason why sometimes you might be unable to move the cursor past a sentence boundary, even though there might be more text in the underlying textfield. From this it also follows that the text that you read back is also the text that you can move the FlickType cursor through.
>
> And if, for example, you start typing with FlickType on a blank textfield, and never switch out of FlickType until you are done, you should always be able to read back everything that you have typed.
>
> Hope this makes some sense, and please let us know if you are still experiencing something unexpected.
>
> Thanks,
> Kosta
>
>
>
>





Re: Build 111

Benny Barber
 

Kosta,
This problem is occurring while never leaving FlickType. It seems to happen on lengthy messages and checking the text with the 3 finger hole multiple times. Thanks.
Benny

On Jun 26, 2018, at 3:20 PM, FlickType <@FlickType> wrote:

Thank you Benny. On the 3 finger hold to read back, there are some limitations that we hope to overcome in the future. FlickType will only be able to read back text that it knows is there, and if you happen to switch keyboards or more generally switch to FlickType to edit or append existing text, iOS will not tell us what the entire contents of the text field are. Instead, we will only get the one or two sentences nearest to where the cursor is. This is the same reason why sometimes you might be unable to move the cursor past a sentence boundary, even though there might be more text in the underlying textfield. From this it also follows that the text that you read back is also the text that you can move the FlickType cursor through.

And if, for example, you start typing with FlickType on a blank textfield, and never switch out of FlickType until you are done, you should always be able to read back everything that you have typed.

Hope this makes some sense, and please let us know if you are still experiencing something unexpected.

Thanks,
Kosta




Re: Build 111, working well

David Nason
 

Great, thanks Kosta.

On 26 Jun 2018, at 21:11, FlickType <@FlickType> wrote:

Thank you David, I was able to reproduce the problem and a fix should
be out to alpha soon.

- Kosta



On Tue, Jun 26, 2018 at 12:08 PM David Nason <dnason@...> wrote:

I agree. With the delay as it is now, I am happy to leave the feature switched on. It doesn't interupt me too often, but I know it is there when I do need it.

I've noticed a little bug by the way. It is happening in WhatsApp and the native Messages app, but not in Mail.
If I type a sentence, then dismiss or switch the keyboard. Then bring the cursor back to the start of the text field, in order to type something that I want to appear before the text I've already typed.
Any text I type there with FlickType will not successfully appear in the text field. It is just lost.
The work around is to insert a space between the cursor and the original text.

Hope that makes sense!

Dave
On 26 Jun 2018, at 18:13, Chuck Dean <cadean329@...> wrote:

Hi Kosta,
I have been playing with the spelling and phonetics. I think you have the delay set perfectly. Normally I would turn off the spelling, but there is enough delay so my typing is not interrupted.
Good work, as usual!
Chuck




Re: Build 111 flick and hold not working as well.

Chuck Dean
 

Hi Kosta.
Yes, it was like I was manually entering letters, when I flicked down.
When I did a flick up and hold, it didn't do anything. I had to perform the gesture a couple of times.

Chuck

On Jun 26, 2018, at 1:12 PM, FlickType <@FlickType> wrote:

Thank you Chuck. When you say the flick and hold is not working well,
what does it do instead? Does it enter a character? Let us know if you
figure out any pattern.

- Kosta
On Tue, Jun 26, 2018 at 10:41 AM Chuck Dean <cadean329@...> wrote:


Hi Kosta,
I also noticed the flick and hold is not working well all the time. I have had it not work both when dismissing the keyboard and changing to the iOS keyboard.
I am not sure what it is doing, and I cannot duplicate the problem.
Chuck



Re: Build 111

 

Thank you Benny. On the 3 finger hold to read back, there are some limitations that we hope to overcome in the future. FlickType will only be able to read back text that it knows is there, and if you happen to switch keyboards or more generally switch to FlickType to edit or append existing text, iOS will not tell us what the entire contents of the text field are. Instead, we will only get the one or two sentences nearest to where the cursor is. This is the same reason why sometimes you might be unable to move the cursor past a sentence boundary, even though there might be more text in the underlying textfield. From this it also follows that the text that you read back is also the text that you can move the FlickType cursor through.

And if, for example, you start typing with FlickType on a blank textfield, and never switch out of FlickType until you are done, you should always be able to read back everything that you have typed.

Hope this makes some sense, and please let us know if you are still experiencing something unexpected.

Thanks,
Kosta