Date   
Re: Build 159

Benny Barber
 

Kosta,
Please do not change the way the full screen keyboard works. Currently it works great. I believe I will always be a full screen user. Thanks for your hard work.
Benny

On Aug 30, 2018, at 1:19 PM, FlickType <@FlickType> wrote:

Thank you all for the helpful feedback, please keep it coming. When posting an issue, please include additional information such as full screen or half screen, iOS 11 or 12, and any iOS typing feedback settings when applicable. Below are my responses to all your points:

- The first word of the sentence being repeated once you start typing the next word. Chuck, is this with the half screen mode? And what are your iOS typing feedback settings and iOS version? Anyone else experiencing that?

- Cannot interact properly with the top half of the screen, for example move the cursor using the rotor. David, what exactly happens when you try that? Note that with half screen mode, any iOS system gesture such as the rotor needs to be performed entirely outside of the FlickType area, in other words it has to be done inside the application area. If one finger is in the application area and another finger is inside FlickType, the rotor gesture will not register.

- Hearing "space" when inserting a period is a known issue and should be fixed soon.

- The voice being too high pitched when reading the typed word: David, what are your iOS typing feedback settings and iOS version? Anyone else experiencing that?

- The new multi-finger setting only affects the two finger single tap to toggle shift. When disabled, that gesture will not trigger a shift change. I will rename the setting to something better. This is more of a bandaid fix for now.

- When double tapping in the text field to move the cursor to the beginning or end of the text, VoiceOver will say the first or last word instead of "beginning of document" or "end of document". This should be fixed soon.

- I can not flick line by line, only word by word. Do you mean using the 3-finger gesture on FlickType? There is a known issue where the cursor will actually move over entire sentences as expected, but only the punctuation marks will be announced.

- When flicking through the text word by word with the iOS gestures, the last word in a sentence is not always announced. This should be fixed soon.

- While trying to reply to a email, I could not access the send button, I lost the email. Chuck, can you please elaborate on not being able to access the send button? And was the email saved as a draft? With the half screen mode, you should not ever experience text loss since all text changes are instantly reflected in the application's text field.

- I tried turning off multi finger gestures which did turn them off, but I tried typing words with a hard press to capitalize the word with no results. The first letter is announced but not typed. Chuck, I was not able to reproduce this.

- FlickType is no longer spelling back words to me, even though I have the setting turned on. David, is this with the half screen mode? Does restarting your device seem to fix it?

Thanks,
Kosta


Re: Build 159

Salman Haider
 

Kosta and Dave,

I would like to confirm that I am experiencing this bug as well. After
manually typing a word, when I swipe right, Voiceover announces
"period", rather than the word that was typed.
I would like to add that I have encountered this not just in the Mail
app like Dave, but also in another app. Namely, Facebook Messenger.
So far...I'll let you know if I encounter it in more apps. It is
consistent across all keyboard heights. I personally use the almost
full screen mode.

I also want to give feedback on the newly introduced one finger tap
and hold gesture (above the top row of keys) to read back typed text.
While I like the idea of a one handed gesture, I am finding this one
to be highly inconvenient and intrusive. Often, this gesture becomes a
problem when attempting to manually type a word, especially one that
involves typing letters that are in the top row. Secondly, I am
noticing that this is also interfering with the one finger swipe up
and hold gesture to switch to the iOS keyboard. One has to be very
precise when performing that gesture, and that too, in the bottom half
of the screen rather than anywhere on the screen, as was the case
previously.
I have had my text read out to me multiple times already when
attempting to switch to the iOS keyboard, or have had a letter
manually typed when attempting to perform the gesture.
Being a full screen mode user, I do have a need to switch to the iOS
keyboard and so definitely do not like this new gesture interfering
with the one finger swipe up and hold.

Needless to say, I'm not a fan and prefer the two finger or three
finger tap and hold gestures for text read back, as those gestures
don't interfere with any of the other one handed and existing
gestures.

Salman

On 8/31/18, David Nason <dnason@...> wrote:
Ah ok, that makes more sense, thanks.
The manual typing bug only seems to be inMail. its not happening in
Messages,Notes, or WhatsApp. It happens with all four keyboard height
options.

Dave
On 1 Sep 2018, at 00:13, FlickType <@FlickType> wrote:

Ed, thank you for the kind words ☺️

Still trying to reproduce the manual word period issue.

- Kosta




Re: Build 159

George Cham
 

This is  ok.
Its working fine.
I've got half screen mode.
when I tap on the area   where the text is   displayed,  it will read what  I have writen  

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: 32501065340n behalf of
Sent: Saturday, September 1, 2018 10:00 am
To: alpha@flicktype.groups.io; alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 159
 
Hi costa,
I'm using standed keyboard

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: 32061064760n behalf of
Sent: Saturday, September 1, 2018 9:13 am
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 159
 
Ed, thank you for the kind words ☺️

Still trying to reproduce the manual word period issue.

- Kosta



Re: Build 159

Chuck Dean
 

Hi kosta.,
I don't know if this has been mentioned., but in build161., when I flick right to insert Punctuation., FlickType repeats the last word typed., then I must swipe left again to insert the Punctuation..

I just noticed what is happening.
when it announces the last word typed, it is actually inserting a period.
I am using an iPhone 8, running iOS 11.4.1

chuck

On Aug 31, 2018, at 4:58 PM, David Nason <dnason@...> wrote:

Ah ok, that makes more sense, thanks.
The manual typing bug only seems to be inMail. its not happening in Messages,Notes, or WhatsApp. It happens with all four keyboard height options.

Dave
On 1 Sep 2018, at 00:13, FlickType <@FlickType> wrote:

Ed, thank you for the kind words ☺️

Still trying to reproduce the manual word period issue.

- Kosta



Re: Build 159

George Cham
 

Hi costa,
I'm using standed keyboard

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: 32061064760n behalf of
Sent: Saturday, September 1, 2018 9:13 am
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 159
 
Ed, thank you for the kind words ☺️

Still trying to reproduce the manual word period issue.

- Kosta



Re: Build 159

David Nason
 

Ah ok, that makes more sense, thanks.
The manual typing bug only seems to be inMail. its not happening in Messages,Notes, or WhatsApp. It happens with all four keyboard height options.

Dave

On 1 Sep 2018, at 00:13, FlickType <@FlickType> wrote:

Ed, thank you for the kind words ☺️

Still trying to reproduce the manual word period issue.

- Kosta


Re: Build 159

 

Ed, thank you for the kind words ☺️

Still trying to reproduce the manual word period issue.

- Kosta

Re: Build 159

 

Dave, I cannot reproduce the swipe right entering a full stop / period after manually typing a word. What height and app are you experiencing this in? And is it highly reproducible?

Thanks,
- Kosta

Re: Build 159

Ed Worrell
 

Hey David and Kosta?

I too now am seeing the manual entry bug. Just like David said before. Manually enter a word swipe right and flicktype inserts a. period.

Other then this issue it's fantastic!

Thanks,

Ed 


On Aug 31, 2018, at 4:56 PM, David Nason <dnason@...> wrote:

Although actually, that experience is slightly different inMessages and WhatsApp. In those, the only way I can efficiently do it is to tap and hold inside flicktype, then slide up.

Another issue I've just noticed. If I type a word manually, when I swipe right, instead of confirming the word I typed, it enters a full stop.
This is the case no matter what typing feedback setting I have chosen in VoiceOver settings.

Aside from these little niggles, this is now very close to being ready for prime time in my opinion. I'm no longer switching back to the iOS keyboard in apps likeMail as often as I used to☺️

Dave
  


On 31 Aug 2018, at 23:39, David Nason <dnason@...> wrote:

Hi Kosta.

Just thinking, the sooner we can have a gesture to toggle the different keyboard heights the better. Even if its  not the one you settle on long term.
It would help for us testing to be able to easily switch.

The tap to read back is confusing me a bit. If I tap fairly high up the screen, well inside the app area, it does appear to read everything I've typed.
However, if I tap on the keyboard and then slide up as you suggest is possible, it only reads the last sentence.

I do like the idea though. As you know, I'm generally a fan of one finger gestures.

Dave
 
 


On 31 Aug 2018, at 23:27, George Cham <George.cham@...> wrote:

Hi costa,
VoiceOver is now announcing a. After a flick right.
The hold at the top of the half or full screen keyboard works ok, in the demo version. but it takes a bit of practice to get the finger in the right spot.
As I type this reply, I'm trying to  read back what I have written.
However, every time I tap and hold above the top of the keyboard, I hit the
Y.  

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: Saturday, September 1, 2018 8:17:34 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 159
 
Build 161 is out, keeping this in the same thread.

What’s new:
- Fixed incorrect "space" announcement when inserting a period in half screen mode.
- Full screen mode: Added a new one-finger long press gesture above the keyboard area to read back what you've typed. You can also start your long press on the keyboard and then move your finger above the top QWERTY row. This gesture is in addition to the two and three finger long press gestures that can be performed anywhere. Please let us know what you think, so that we consolidate and only keep the best gesture for this action.
- Don't spell word when announcing cursor position.
- Renamed "Standard" keyboard height option to "Minimal".

Thank you for reporting a potential difference with smaller sized devices, we will investigate this. In the meantime, please try both half screen as well as minimal modes and let us know if one is better than the other for you. And thank you all for the continued feedback and discussion, please keep it coming! ☺️

Kosta



Re: Build 159

 

Thank you Dave. The delay in adding the gesture to toggle is less about choosing what the best gesture is, and more about the fact that the full screen mode operates very differently compared to all other modes, and switching them on-the-fly is simply not yet supported in the backend code, so to speak. On-the-fly switching introduces a host of new complexities that I'm hoping to tackle soon. The full screen height uses the delayed textfield interaction mode, whereas all other heights use direct textfield interaction. One idea here is to make the full screen height also use direct textfield interaction, and have the contents immediately reflected on the textfield with all the benefits and drawbacks that would come with this such as the annoying "end of document" announcement when flicking down. And possibly have a setting for advanced users where they can toggle between direct and delayed textfield interaction modes independent of keyboard height. If these two things get decoupled then switching keyboard height on-the-fly would be trivial to implement. Hope that makes some sense.

Regarding tap to read back: This is really only meant for the full screen mode. In all other modes where you can interact with the app above, what happens if you tap inside the application area is completely out of our control as a keyboard. Typically, if you touch the text inside a textfield iOS will read the entire contents back I believe. The new FlickType gesture seems to kind of work in the minimal mode simply because there is a 1-pixel high visual announcement area that you will cross as you drag up, but you should have no reason to use that over the standard iOS way of reading back your text anyway. And regardless of mode, the read back from FlickType still suffers from the issue where iOS does not allow us to know the entire contents of a textfield, only the current sentence or so. In full screen mode, which also has the delayed textfield interaction, you can read back all the text you have written because FlickType keeps track of it all until it's dismissed and then inserts it into the textfield. Also regardless of what gesture you use to invoke the FlickType read back action, the text that will be read back is the same. I am sure my explanation in the change log about this new gesture was not great, and this current long explanation might make things sound much more complicated than they are from a user's perspective. To recap, the new 1-finger gesture is meant for the full screen mode, and you can simply imagine it as being able to sort of touch your text that always sits right above the QWERTY row. Hope that makes sense, and I'm sure someone else will be able to explain it better from a user's point of view 😎

- Kosta

Re: Build 159

David Nason
 

Although actually, that experience is slightly different inMessages and WhatsApp. In those, the only way I can efficiently do it is to tap and hold inside flicktype, then slide up.

Another issue I've just noticed. If I type a word manually, when I swipe right, instead of confirming the word I typed, it enters a full stop.
This is the case no matter what typing feedback setting I have chosen in VoiceOver settings.

Aside from these little niggles, this is now very close to being ready for prime time in my opinion. I'm no longer switching back to the iOS keyboard in apps likeMail as often as I used to☺️

Dave
  


On 31 Aug 2018, at 23:39, David Nason <dnason@...> wrote:

Hi Kosta.

Just thinking, the sooner we can have a gesture to toggle the different keyboard heights the better. Even if its  not the one you settle on long term.
It would help for us testing to be able to easily switch.

The tap to read back is confusing me a bit. If I tap fairly high up the screen, well inside the app area, it does appear to read everything I've typed.
However, if I tap on the keyboard and then slide up as you suggest is possible, it only reads the last sentence.

I do like the idea though. As you know, I'm generally a fan of one finger gestures.

Dave
 
 


On 31 Aug 2018, at 23:27, George Cham <George.cham@...> wrote:

Hi costa,
VoiceOver is now announcing a. After a flick right.
The hold at the top of the half or full screen keyboard works ok, in the demo version. but it takes a bit of practice to get the finger in the right spot.
As I type this reply, I'm trying to  read back what I have written.
However, every time I tap and hold above the top of the keyboard, I hit the
Y.  

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: Saturday, September 1, 2018 8:17:34 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 159
 
Build 161 is out, keeping this in the same thread.

What’s new:
- Fixed incorrect "space" announcement when inserting a period in half screen mode.
- Full screen mode: Added a new one-finger long press gesture above the keyboard area to read back what you've typed. You can also start your long press on the keyboard and then move your finger above the top QWERTY row. This gesture is in addition to the two and three finger long press gestures that can be performed anywhere. Please let us know what you think, so that we consolidate and only keep the best gesture for this action.
- Don't spell word when announcing cursor position.
- Renamed "Standard" keyboard height option to "Minimal".

Thank you for reporting a potential difference with smaller sized devices, we will investigate this. In the meantime, please try both half screen as well as minimal modes and let us know if one is better than the other for you. And thank you all for the continued feedback and discussion, please keep it coming! ☺️

Kosta



Re: Build 159

Ed Worrell
 

hey kosta and Ashley,

I would like to congratulate you guys on another solid build. I am even more in love with this keyboard. The smaller or standard sized keyboard is bringing me back to the original Fleksy days. This is becoming my favorite accessibility application on my iPhone!👍🏻

Ed

On Aug 31, 2018, at 4:38 PM, FlickType <@FlickType> wrote:

Thank you George. What keyboard height are you using? The way to think about this is as if the entire visual announcement area which sits right above the QWERTY row is a giant invisible label which always has your text. The idea is that this would be the easiest area to hit since it is so large, unless you are using half screen mode in which case it would be much smaller, or minimal where there is no visual announcement area.

- Kosta


Re: Build 159

David Nason
 

Hi Kosta.

Just thinking, the sooner we can have a gesture to toggle the different keyboard heights the better. Even if its  not the one you settle on long term.
It would help for us testing to be able to easily switch.

The tap to read back is confusing me a bit. If I tap fairly high up the screen, well inside the app area, it does appear to read everything I've typed.
However, if I tap on the keyboard and then slide up as you suggest is possible, it only reads the last sentence.

I do like the idea though. As you know, I'm generally a fan of one finger gestures.

Dave
 
 


On 31 Aug 2018, at 23:27, George Cham <George.cham@...> wrote:

Hi costa,
VoiceOver is now announcing a. After a flick right.
The hold at the top of the half or full screen keyboard works ok, in the demo version. but it takes a bit of practice to get the finger in the right spot.
As I type this reply, I'm trying to  read back what I have written.
However, every time I tap and hold above the top of the keyboard, I hit the
Y.  

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: Saturday, September 1, 2018 8:17:34 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 159
 
Build 161 is out, keeping this in the same thread.

What’s new:
- Fixed incorrect "space" announcement when inserting a period in half screen mode.
- Full screen mode: Added a new one-finger long press gesture above the keyboard area to read back what you've typed. You can also start your long press on the keyboard and then move your finger above the top QWERTY row. This gesture is in addition to the two and three finger long press gestures that can be performed anywhere. Please let us know what you think, so that we consolidate and only keep the best gesture for this action.
- Don't spell word when announcing cursor position.
- Renamed "Standard" keyboard height option to "Minimal".

Thank you for reporting a potential difference with smaller sized devices, we will investigate this. In the meantime, please try both half screen as well as minimal modes and let us know if one is better than the other for you. And thank you all for the continued feedback and discussion, please keep it coming! ☺️

Kosta



Re: Build 159

 

Thank you George. What keyboard height are you using? The way to think about this is as if the entire visual announcement area which sits right above the QWERTY row is a giant invisible label which always has your text. The idea is that this would be the easiest area to hit since it is so large, unless you are using half screen mode in which case it would be much smaller, or minimal where there is no visual announcement area.

- Kosta

Re: Build 159

Chuck Dean
 

Hi Benny,
Try treating the upper half of the screen as you would if you were using the iOS keyboard.
Double tap until you hear beginning of document. Now, do a two finger swipe gown from the top to read what you typed.
You can also use the rotor to choose to move characters, words, or by line by flicking up or down with one finger.
it works great on my iPhone 8, I hope it works for you too!😎

Chuck

On Aug 31, 2018, at 2:35 PM, Benny Barber <benny.barber55@...> wrote:

I am running version 160. It is a little better with word feedback turned off.. Tapping in the correct place in the upper half is still a challenge. I don't always get feedback from what I have typed. Checking what I have typed sometimes causes FlickType to close. Thanks.
Benny

On Aug 31, 2018, at 3:29 PM, FlickType <@FlickType> wrote:

Thank you Dave. Please try temporarily turning off iOS typing feedback for words and see if that helps with some of the issues you describe. Would love to know if it did help. I'll have to look into our old friend WhatsApp. On the quotation marks, you are correct, the issue is back in the non-full screen modes but should be fixed soon.

Ed, for the magic tap gesture, besides making sure the focus is on the keyboard, you also need to make sure you perform the gesture within the keyboard area for FlickType to capture it.

Benny, can you confirm you are using build 160? Please also try temporarily turning off iOS typing feedback for words and see if that helps. Anyone else experiencing the issues with the Mail app that Benny is describing?

- Kosta



Re: Build 159

George Cham
 

Hi costa,
VoiceOver is now announcing a. After a flick right.
The hold at the top of the half or full screen keyboard works ok, in the demo version. but it takes a bit of practice to get the finger in the right spot.
As I type this reply, I'm trying to  read back what I have written.
However, every time I tap and hold above the top of the keyboard, I hit the
Y.  

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: Saturday, September 1, 2018 8:17:34 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 159
 
Build 161 is out, keeping this in the same thread.

What’s new:
- Fixed incorrect "space" announcement when inserting a period in half screen mode.
- Full screen mode: Added a new one-finger long press gesture above the keyboard area to read back what you've typed. You can also start your long press on the keyboard and then move your finger above the top QWERTY row. This gesture is in addition to the two and three finger long press gestures that can be performed anywhere. Please let us know what you think, so that we consolidate and only keep the best gesture for this action.
- Don't spell word when announcing cursor position.
- Renamed "Standard" keyboard height option to "Minimal".

Thank you for reporting a potential difference with smaller sized devices, we will investigate this. In the meantime, please try both half screen as well as minimal modes and let us know if one is better than the other for you. And thank you all for the continued feedback and discussion, please keep it coming! ☺️

Kosta



Re: Build 159

 

Build 161 is out, keeping this in the same thread.

What’s new:
- Fixed incorrect "space" announcement when inserting a period in half screen mode.
- Full screen mode: Added a new one-finger long press gesture above the keyboard area to read back what you've typed. You can also start your long press on the keyboard and then move your finger above the top QWERTY row. This gesture is in addition to the two and three finger long press gestures that can be performed anywhere. Please let us know what you think, so that we consolidate and only keep the best gesture for this action.
- Don't spell word when announcing cursor position.
- Renamed "Standard" keyboard height option to "Minimal".

Thank you for reporting a potential difference with smaller sized devices, we will investigate this. In the meantime, please try both half screen as well as minimal modes and let us know if one is better than the other for you. And thank you all for the continued feedback and discussion, please keep it coming! ☺️

Kosta

Re: Build 159

Benny Barber
 

Hello Salman,
You are correct. I am using a 5S.
Benny

On Aug 31, 2018, at 4:48 PM, Salman Haider <salmanhaider.purdue@...> wrote:

Hi Benny, I’m very curious to know, what iPhone model do you have? Is it one of the smaller size ones? I seem to be encountering some of the same issues as you are describing with the half screen keyboard and I have an iPhone SE. I don’t know if this has anything to do with the size of the phone, but I’m just curious because I remember reading one time in one of your emails that you are an iPhone 5s user.
Salman

On Aug 31, 2018, at 5:35 PM, Benny Barber <benny.barber55@...> wrote:

I am running version 160. It is a little better with word feedback turned off.. Tapping in the correct place in the upper half is still a challenge. I don't always get feedback from what I have typed. Checking what I have typed sometimes causes FlickType to close. Thanks.
Benny

On Aug 31, 2018, at 3:29 PM, FlickType <@FlickType> wrote:

Thank you Dave. Please try temporarily turning off iOS typing feedback for words and see if that helps with some of the issues you describe. Would love to know if it did help. I'll have to look into our old friend WhatsApp. On the quotation marks, you are correct, the issue is back in the non-full screen modes but should be fixed soon.

Ed, for the magic tap gesture, besides making sure the focus is on the keyboard, you also need to make sure you perform the gesture within the keyboard area for FlickType to capture it.

Benny, can you confirm you are using build 160? Please also try temporarily turning off iOS typing feedback for words and see if that helps. Anyone else experiencing the issues with the Mail app that Benny is describing?

- Kosta






Re: Build 159

Salman Haider
 

Hi Benny, I’m very curious to know, what iPhone model do you have? Is it one of the smaller size ones? I seem to be encountering some of the same issues as you are describing with the half screen keyboard and I have an iPhone SE. I don’t know if this has anything to do with the size of the phone, but I’m just curious because I remember reading one time in one of your emails that you are an iPhone 5s user.
Salman

On Aug 31, 2018, at 5:35 PM, Benny Barber <benny.barber55@...> wrote:

I am running version 160. It is a little better with word feedback turned off.. Tapping in the correct place in the upper half is still a challenge. I don't always get feedback from what I have typed. Checking what I have typed sometimes causes FlickType to close. Thanks.
Benny

On Aug 31, 2018, at 3:29 PM, FlickType <@FlickType> wrote:

Thank you Dave. Please try temporarily turning off iOS typing feedback for words and see if that helps with some of the issues you describe. Would love to know if it did help. I'll have to look into our old friend WhatsApp. On the quotation marks, you are correct, the issue is back in the non-full screen modes but should be fixed soon.

Ed, for the magic tap gesture, besides making sure the focus is on the keyboard, you also need to make sure you perform the gesture within the keyboard area for FlickType to capture it.

Benny, can you confirm you are using build 160? Please also try temporarily turning off iOS typing feedback for words and see if that helps. Anyone else experiencing the issues with the Mail app that Benny is describing?

- Kosta


Re: Build 159

Benny Barber
 

I am running version 160. It is a little better with word feedback turned off.. Tapping in the correct place in the upper half is still a challenge. I don't always get feedback from what I have typed. Checking what I have typed sometimes causes FlickType to close. Thanks.
Benny

On Aug 31, 2018, at 3:29 PM, FlickType <@FlickType> wrote:

Thank you Dave. Please try temporarily turning off iOS typing feedback for words and see if that helps with some of the issues you describe. Would love to know if it did help. I'll have to look into our old friend WhatsApp. On the quotation marks, you are correct, the issue is back in the non-full screen modes but should be fixed soon.

Ed, for the magic tap gesture, besides making sure the focus is on the keyboard, you also need to make sure you perform the gesture within the keyboard area for FlickType to capture it.

Benny, can you confirm you are using build 160? Please also try temporarily turning off iOS typing feedback for words and see if that helps. Anyone else experiencing the issues with the Mail app that Benny is describing?

- Kosta