Topics

Build 111

 

- Fixed gesture issue where short flicks would sometimes be erroneously interpreted as long presses, which caused a single character to be entered, or a space if the spacebar row was enabled and the flick happened near the spacebar area. Please let us know if you are still experiencing any gesture issues at all.
- Slightly increased the word spelling delay. We are trying to find a happy medium where you can leave the spelling setting turned on, and the spelling announcement doesn't get in the way of your regular typing flow.

Thank you for testing!

Paul Sutton
 

Hi, just a little suggestion regarding the spelling feedback. If you didn't want the spelling feature constantly turned on perhaps a 2 finger hold on the screen could spell back the word that you want?
Regards, paul.

On 26 Jun 2018, at 06:41, FlickType <@FlickType> wrote:

- Fixed gesture issue where short flicks would sometimes be erroneously interpreted as long presses, which caused a single character to be entered, or a space if the spacebar row was enabled and the flick happened near the spacebar area. Please let us know if you are still experiencing any gesture issues at all.
- Slightly increased the word spelling delay. We are trying to find a happy medium where you can leave the spelling setting turned on, and the spelling announcement doesn't get in the way of your regular typing flow.

Thank you for testing!


 

Thank you Paul. We are currently reserving this gesture for future
use, but assigning it to spelling of the word is a good idea. We will
definitely consider it.
- Kosta

On Mon, Jun 25, 2018 at 11:43 PM Paul Sutton <sutty_p@...> wrote:

Hi, just a little suggestion regarding the spelling feedback. If you didn't want the spelling feature constantly turned on perhaps a 2 finger hold on the screen could spell back the word that you want?
Regards, paul.
On 26 Jun 2018, at 06:41, FlickType <@FlickType> wrote:

- Fixed gesture issue where short flicks would sometimes be erroneously interpreted as long presses, which caused a single character to be entered, or a space if the spacebar row was enabled and the flick happened near the spacebar area. Please let us know if you are still experiencing any gesture issues at all.
- Slightly increased the word spelling delay. We are trying to find a happy medium where you can leave the spelling setting turned on, and the spelling announcement doesn't get in the way of your regular typing flow.

Thank you for testing!



Paul Sutton
 

😎

On 26 Jun 2018, at 07:45, FlickType <@FlickType> wrote:

Thank you Paul. We are currently reserving this gesture for future
use, but assigning it to spelling of the word is a good idea. We will
definitely consider it.
- Kosta



On Mon, Jun 25, 2018 at 11:43 PM Paul Sutton <sutty_p@...> wrote:

Hi, just a little suggestion regarding the spelling feedback. If you didn't want the spelling feature constantly turned on perhaps a 2 finger hold on the screen could spell back the word that you want?
Regards, paul.
On 26 Jun 2018, at 06:41, FlickType <@FlickType> wrote:

- Fixed gesture issue where short flicks would sometimes be erroneously interpreted as long presses, which caused a single character to be entered, or a space if the spacebar row was enabled and the flick happened near the spacebar area. Please let us know if you are still experiencing any gesture issues at all.
- Slightly increased the word spelling delay. We are trying to find a happy medium where you can leave the spelling setting turned on, and the spelling announcement doesn't get in the way of your regular typing flow.

Thank you for testing!




Benny Barber
 

Kosta,
I have been testing for the gesture problem that I have had and so far so good. Flicking through the alternative word list is working very good. I have had no entry of a single letter as I am flicking through the list. Thanks for the fix.
On the down side, the 3 finger hole for read back will not always read the entire text that is typed.
Benny

On Jun 26, 2018, at 12:41 AM, FlickType <@FlickType> wrote:

- Fixed gesture issue where short flicks would sometimes be erroneously interpreted as long presses, which caused a single character to be entered, or a space if the spacebar row was enabled and the flick happened near the spacebar area. Please let us know if you are still experiencing any gesture issues at all.
- Slightly increased the word spelling delay. We are trying to find a happy medium where you can leave the spelling setting turned on, and the spelling announcement doesn't get in the way of your regular typing flow.

Thank you for testing!


 

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

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



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
>
>
>
>




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
>
>
>
>