Date   

Custom keyboard, a thought.

Chuck Dean
 

Custom keyboard, a thought.
I was thinking about a replacement for the tap and hole to go to the next keyboard; considering it won't be available once manual input is activated.
I was thinking a three finger tap. Then to go to the next keyboard; do a three finger tap; and to dismiss the keyboard do a three finger swipe down. Three fingers control the keyboard, works for me.


Chuck


Re: Usage thoughts...

Serina Gilbert
 

I would still like to see a half screen option. I think this would especially be helpful when completing online forms.


Re: Build 55

Chuck Dean
 

Hi Kosta, please ignore this email. I removed the emoji keyboard and my shortcuts are intact.

Chuck

On May 4, 2018, at 1:32 PM, Chuck Dean <cadean329@gmail.com> wrote:

Hi Kosta,
Can I remove the emoji keyboard's name from the selection list?
I don't want to remove the keyboard... I have some shortcuts with emoji.

Chuck

On May 4, 2018, at 12:49 PM, FlickType <hello@flicktype.com> wrote:

Thank you Rocco.

When running as a custom keyboard, FlickType has no control over what voiceover will or won’t do, so the only way I’ve found so far to provide the solid experience that you are used to from the main app is to change the typing feedback setting. I know this is not ideal, and I’d love to understand more about how this requirement is bothersome for you. And of course my hope is that once the FlickType custom keyboard becomes more mature, you should need to rely less and less on the standard keyboard, all the way to eventually removing it from your list of keyboards and only keeping FlickType. Did you know you could actually remove the iOS keyboard from the keyboard list? You can always just add it back in case you do, and of course I don’t think it’s a viable option yet. Finally I haven’t tested much with the typing feedback set to characters, maybe that’s ok too?

Kosta

On May 4, 2018, at 12:37, Rocco Fiorentino <roccof466@gmail.com> wrote:

Hi all,

This build is great, thank you so much! I’m curious about something though. In the previous build, build fifty four, the voice over speech issue did not exist in the keyboard extension, and it didn't matter what your typing echo was set to. Is there a way to change back to that behavior, or what changed in this build that no longer allows FlickType to be independent of voice over typing settings? I remember fleksy had a similar issue near the end, so trying to think of ways of preventing that from happening again.

Thanks again, keep up the amazing work. It’s much appreciated. :)

Rocco
On May 4, 2018, at 12:32 AM, FlickType <hello@flicktype.com> wrote:

- Fixed audio latency. Hopefully it should now feel more like the main app, apart from the tap feedback delay. Please note: you must set VoiceOver typing feedback to "Nothing", otherwise the announcements will be laggy and sound like the voice has a cold and a stutter - no kidding. For some reason the iOS announcements are lower-quality as well as delayed, and because of the delay they almost immediately interrupt the FlickType announcements.
- You can now type your custom dictionary words, as well as some additional built-in words. You must run the main app once after updating for your words to carry over.
- Improved memory management. Hopefully you won't get those memory warnings any more, fingers crossed.
- First word in mail app should now be correctly capitalized.






Re: Build 55

Rocco Fiorentino
 

Hi Kosta,

If I only relied solely on the Flicktype keyboard for text entry, I wouldn’t mind changing the feedback settings in VoceOver. But since that’s not the case yet, I use the characters and words setting when I type without Flicktype. In build 54, the custom keyboard, outside of the app, behaved normally with voiceover still set to characters and words. What I’m trying to figure out is what changed, especially if Flicktype seems to have no control of VOiceOver while in the custom keyboard. Strange…
If you need more info from me please don’t hesitate to ask. I haven’t tried with just characters either, but that may be something to experiment with as well.

Thanks,

Rocco

On May 4, 2018, at 2:49 PM, FlickType <hello@flicktype.com> wrote:

Thank you Rocco.

When running as a custom keyboard, FlickType has no control over what voiceover will or won’t do, so the only way I’ve found so far to provide the solid experience that you are used to from the main app is to change the typing feedback setting. I know this is not ideal, and I’d love to understand more about how this requirement is bothersome for you. And of course my hope is that once the FlickType custom keyboard becomes more mature, you should need to rely less and less on the standard keyboard, all the way to eventually removing it from your list of keyboards and only keeping FlickType. Did you know you could actually remove the iOS keyboard from the keyboard list? You can always just add it back in case you do, and of course I don’t think it’s a viable option yet. Finally I haven’t tested much with the typing feedback set to characters, maybe that’s ok too?

Kosta

On May 4, 2018, at 12:37, Rocco Fiorentino <roccof466@gmail.com> wrote:

Hi all,

This build is great, thank you so much! I’m curious about something though. In the previous build, build fifty four, the voice over speech issue did not exist in the keyboard extension, and it didn't matter what your typing echo was set to. Is there a way to change back to that behavior, or what changed in this build that no longer allows FlickType to be independent of voice over typing settings? I remember fleksy had a similar issue near the end, so trying to think of ways of preventing that from happening again.

Thanks again, keep up the amazing work. It’s much appreciated. :)

Rocco
On May 4, 2018, at 12:32 AM, FlickType <hello@flicktype.com> wrote:

- Fixed audio latency. Hopefully it should now feel more like the main app, apart from the tap feedback delay. Please note: you must set VoiceOver typing feedback to "Nothing", otherwise the announcements will be laggy and sound like the voice has a cold and a stutter - no kidding. For some reason the iOS announcements are lower-quality as well as delayed, and because of the delay they almost immediately interrupt the FlickType announcements.
- You can now type your custom dictionary words, as well as some additional built-in words. You must run the main app once after updating for your words to carry over.
- Improved memory management. Hopefully you won't get those memory warnings any more, fingers crossed.
- First word in mail app should now be correctly capitalized.





Re: Build 55

Benny Barber
 

I'll have to agree with David on the keyboard feedback. I need to hear what I am entering on the iOS keyboard. Think about the phone keypad as well. It is cumbersome to enter on the phone keypad without voice feedback. Thanks for your consideration.

Benny

On May 4, 2018, at 12:32 AM, FlickType <hello@flicktype.com> wrote:

- Fixed audio latency. Hopefully it should now feel more like the main app, apart from the tap feedback delay. Please note: you must set VoiceOver typing feedback to "Nothing", otherwise the announcements will be laggy and sound like the voice has a cold and a stutter - no kidding. For some reason the iOS announcements are lower-quality as well as delayed, and because of the delay they almost immediately interrupt the FlickType announcements.
- You can now type your custom dictionary words, as well as some additional built-in words. You must run the main app once after updating for your words to carry over.
- Improved memory management. Hopefully you won't get those memory warnings any more, fingers crossed.
- First word in mail app should now be correctly capitalized.



Re: Build 55

Chuck Dean
 

Hi Kosta,
Can I remove the emoji keyboard's name from the selection list?
I don't want to remove the keyboard... I have some shortcuts with emoji.

Chuck

On May 4, 2018, at 12:49 PM, FlickType <hello@flicktype.com> wrote:

Thank you Rocco.

When running as a custom keyboard, FlickType has no control over what voiceover will or won’t do, so the only way I’ve found so far to provide the solid experience that you are used to from the main app is to change the typing feedback setting. I know this is not ideal, and I’d love to understand more about how this requirement is bothersome for you. And of course my hope is that once the FlickType custom keyboard becomes more mature, you should need to rely less and less on the standard keyboard, all the way to eventually removing it from your list of keyboards and only keeping FlickType. Did you know you could actually remove the iOS keyboard from the keyboard list? You can always just add it back in case you do, and of course I don’t think it’s a viable option yet. Finally I haven’t tested much with the typing feedback set to characters, maybe that’s ok too?

Kosta

On May 4, 2018, at 12:37, Rocco Fiorentino <roccof466@gmail.com> wrote:

Hi all,

This build is great, thank you so much! I’m curious about something though. In the previous build, build fifty four, the voice over speech issue did not exist in the keyboard extension, and it didn't matter what your typing echo was set to. Is there a way to change back to that behavior, or what changed in this build that no longer allows FlickType to be independent of voice over typing settings? I remember fleksy had a similar issue near the end, so trying to think of ways of preventing that from happening again.

Thanks again, keep up the amazing work. It’s much appreciated. :)

Rocco
On May 4, 2018, at 12:32 AM, FlickType <hello@flicktype.com> wrote:

- Fixed audio latency. Hopefully it should now feel more like the main app, apart from the tap feedback delay. Please note: you must set VoiceOver typing feedback to "Nothing", otherwise the announcements will be laggy and sound like the voice has a cold and a stutter - no kidding. For some reason the iOS announcements are lower-quality as well as delayed, and because of the delay they almost immediately interrupt the FlickType announcements.
- You can now type your custom dictionary words, as well as some additional built-in words. You must run the main app once after updating for your words to carry over.
- Improved memory management. Hopefully you won't get those memory warnings any more, fingers crossed.
- First word in mail app should now be correctly capitalized.





Re: Build 55

David Nason
 

Hi,

I have never had the memory warning issue. Though I am on iPhone X, so maybe that is the reason.

Until build 55, I did not experience the voice sounding crazy and high pitched, but an experiencing it now in build 55. I appreciate the fix, however I would be very reluctant to set typing feedback to nothing honestly, as I do still need to use the stock iOS keyboard at times and do want that feedback. So I hope you can find a better solution.

Thanks,
Dave

On 4 May 2018, at 20:49, FlickType <hello@flicktype.com> wrote:

Thank you Rocco.

When running as a custom keyboard, FlickType has no control over what voiceover will or won’t do, so the only way I’ve found so far to provide the solid experience that you are used to from the main app is to change the typing feedback setting. I know this is not ideal, and I’d love to understand more about how this requirement is bothersome for you. And of course my hope is that once the FlickType custom keyboard becomes more mature, you should need to rely less and less on the standard keyboard, all the way to eventually removing it from your list of keyboards and only keeping FlickType. Did you know you could actually remove the iOS keyboard from the keyboard list? You can always just add it back in case you do, and of course I don’t think it’s a viable option yet. Finally I haven’t tested much with the typing feedback set to characters, maybe that’s ok too?

Kosta

On May 4, 2018, at 12:37, Rocco Fiorentino <roccof466@gmail.com> wrote:

Hi all,

This build is great, thank you so much! I’m curious about something though. In the previous build, build fifty four, the voice over speech issue did not exist in the keyboard extension, and it didn't matter what your typing echo was set to. Is there a way to change back to that behavior, or what changed in this build that no longer allows FlickType to be independent of voice over typing settings? I remember fleksy had a similar issue near the end, so trying to think of ways of preventing that from happening again.

Thanks again, keep up the amazing work. It’s much appreciated. :)

Rocco
On May 4, 2018, at 12:32 AM, FlickType <hello@flicktype.com> wrote:

- Fixed audio latency. Hopefully it should now feel more like the main app, apart from the tap feedback delay. Please note: you must set VoiceOver typing feedback to "Nothing", otherwise the announcements will be laggy and sound like the voice has a cold and a stutter - no kidding. For some reason the iOS announcements are lower-quality as well as delayed, and because of the delay they almost immediately interrupt the FlickType announcements.
- You can now type your custom dictionary words, as well as some additional built-in words. You must run the main app once after updating for your words to carry over.
- Improved memory management. Hopefully you won't get those memory warnings any more, fingers crossed.
- First word in mail app should now be correctly capitalized.


Re: Build 55

 

Thank you Rocco.

When running as a custom keyboard, FlickType has no control over what voiceover will or won’t do, so the only way I’ve found so far to provide the solid experience that you are used to from the main app is to change the typing feedback setting. I know this is not ideal, and I’d love to understand more about how this requirement is bothersome for you. And of course my hope is that once the FlickType custom keyboard becomes more mature, you should need to rely less and less on the standard keyboard, all the way to eventually removing it from your list of keyboards and only keeping FlickType. Did you know you could actually remove the iOS keyboard from the keyboard list? You can always just add it back in case you do, and of course I don’t think it’s a viable option yet. Finally I haven’t tested much with the typing feedback set to characters, maybe that’s ok too?

Kosta

On May 4, 2018, at 12:37, Rocco Fiorentino <roccof466@gmail.com> wrote:

Hi all,

This build is great, thank you so much! I’m curious about something though. In the previous build, build fifty four, the voice over speech issue did not exist in the keyboard extension, and it didn't matter what your typing echo was set to. Is there a way to change back to that behavior, or what changed in this build that no longer allows FlickType to be independent of voice over typing settings? I remember fleksy had a similar issue near the end, so trying to think of ways of preventing that from happening again.

Thanks again, keep up the amazing work. It’s much appreciated. :)

Rocco
On May 4, 2018, at 12:32 AM, FlickType <hello@flicktype.com> wrote:

- Fixed audio latency. Hopefully it should now feel more like the main app, apart from the tap feedback delay. Please note: you must set VoiceOver typing feedback to "Nothing", otherwise the announcements will be laggy and sound like the voice has a cold and a stutter - no kidding. For some reason the iOS announcements are lower-quality as well as delayed, and because of the delay they almost immediately interrupt the FlickType announcements.
- You can now type your custom dictionary words, as well as some additional built-in words. You must run the main app once after updating for your words to carry over.
- Improved memory management. Hopefully you won't get those memory warnings any more, fingers crossed.
- First word in mail app should now be correctly capitalized.




Re: Build 55

Benny Barber
 

Yes, this is my experience as well, Kosta. Thanks.

On May 4, 2018, at 2:27 PM, FlickType <hello@flicktype.com> wrote:

Thank you Paul, based on your message, I managed to reproduce the missing sentence feedback. It seems to happen in messages but not other applications that I tried. I assume this is the same issue that Benny is experiencing. I will investigate. Thanks, Kosta

On May 4, 2018, at 12:22, Paul Sutton <sutty_p@hotmail.co.uk> wrote:

Hey everyone, I have noticed when I am writing an email and use the three finger swipe left and right, each sentence is spoken. However, when writing a text message nothing happens except when I reach the end or beginning it just simply says beginning or end of document. I just wondered if anyone else had this problem. Paul.
On 4 May 2018, at 19:40, Chuck Dean <cadean329@gmail.com> wrote:

It should also be noted that I am doing an awful lot of typing. Probably more than most people.

Chuck

On May 4, 2018, at 11:29 AM, FlickType <hello@flicktype.com> wrote:

Thanks Chuck. Anyone else getting these memory warnings?

Kosta

On May 4, 2018, at 11:20, Chuck Dean <cadean329@gmail.com> wrote:

I was trying to reply to a post in the ViPhone group, and the custom keyboard locked up and I couldn't do anything with it.

(I had to go to the iOS keyboard, to finish this email because the memory warning keeps coming up. I am dictating this.)

Just now as I was trying to type this with Fliktype custom keyboard, the memory warning came back, and would not let me do anything.
At this time I don’t think I can use the custom keyboard to reliably enter text in any field. When it works, it works great, but it seem to lock up on me a lot.

Chuck




Re: Build 55

Rocco Fiorentino
 

Hi all,

This build is great, thank you so much! I’m curious about something though. In the previous build, build fifty four, the voice over speech issue did not exist in the keyboard extension, and it didn't matter what your typing echo was set to. Is there a way to change back to that behavior, or what changed in this build that no longer allows FlickType to be independent of voice over typing settings? I remember fleksy had a similar issue near the end, so trying to think of ways of preventing that from happening again.

Thanks again, keep up the amazing work. It’s much appreciated. :)

Rocco

On May 4, 2018, at 12:32 AM, FlickType <hello@flicktype.com> wrote:

- Fixed audio latency. Hopefully it should now feel more like the main app, apart from the tap feedback delay. Please note: you must set VoiceOver typing feedback to "Nothing", otherwise the announcements will be laggy and sound like the voice has a cold and a stutter - no kidding. For some reason the iOS announcements are lower-quality as well as delayed, and because of the delay they almost immediately interrupt the FlickType announcements.
- You can now type your custom dictionary words, as well as some additional built-in words. You must run the main app once after updating for your words to carry over.
- Improved memory management. Hopefully you won't get those memory warnings any more, fingers crossed.
- First word in mail app should now be correctly capitalized.



Re: Build 55

 

Thank you Paul, based on your message, I managed to reproduce the missing sentence feedback. It seems to happen in messages but not other applications that I tried. I assume this is the same issue that Benny is experiencing. I will investigate. Thanks, Kosta

On May 4, 2018, at 12:22, Paul Sutton <sutty_p@hotmail.co.uk> wrote:

Hey everyone, I have noticed when I am writing an email and use the three finger swipe left and right, each sentence is spoken. However, when writing a text message nothing happens except when I reach the end or beginning it just simply says beginning or end of document. I just wondered if anyone else had this problem. Paul.
On 4 May 2018, at 19:40, Chuck Dean <cadean329@gmail.com> wrote:

It should also be noted that I am doing an awful lot of typing. Probably more than most people.

Chuck

On May 4, 2018, at 11:29 AM, FlickType <hello@flicktype.com> wrote:

Thanks Chuck. Anyone else getting these memory warnings?

Kosta

On May 4, 2018, at 11:20, Chuck Dean <cadean329@gmail.com> wrote:

I was trying to reply to a post in the ViPhone group, and the custom keyboard locked up and I couldn't do anything with it.

(I had to go to the iOS keyboard, to finish this email because the memory warning keeps coming up. I am dictating this.)

Just now as I was trying to type this with Fliktype custom keyboard, the memory warning came back, and would not let me do anything.
At this time I don’t think I can use the custom keyboard to reliably enter text in any field. When it works, it works great, but it seem to lock up on me a lot.

Chuck



Re: Build 55

 

Thank you Benny. Do you by any chance now get feedback when moving the cursor through entire sentences?

On May 4, 2018, at 12:17, Benny Barber <rebelben@bellsouth.net> wrote:

Kosta,

I noticed a small issue when toggling between the custom keyboard and an editable app. For example, if I open the iOS messages app, then open the custom keyboard, accidentally enter a character, delete everything and then go back to the messages app; a space has been entered into the edit field at the start. No big deal, but something. Thanks.

Benny

On May 4, 2018, at 12:32 AM, FlickType <hello@flicktype.com> wrote:

- Fixed audio latency. Hopefully it should now feel more like the main app, apart from the tap feedback delay. Please note: you must set VoiceOver typing feedback to "Nothing", otherwise the announcements will be laggy and sound like the voice has a cold and a stutter - no kidding. For some reason the iOS announcements are lower-quality as well as delayed, and because of the delay they almost immediately interrupt the FlickType announcements.
- You can now type your custom dictionary words, as well as some additional built-in words. You must run the main app once after updating for your words to carry over.
- Improved memory management. Hopefully you won't get those memory warnings any more, fingers crossed.
- First word in mail app should now be correctly capitalized.





Re: Build 55

Paul Sutton
 

Hey everyone, I have noticed when I am writing an email and use the three finger swipe left and right, each sentence is spoken. However, when writing a text message nothing happens except when I reach the end or beginning it just simply says beginning or end of document. I just wondered if anyone else had this problem. Paul.

On 4 May 2018, at 19:40, Chuck Dean <cadean329@gmail.com> wrote:

It should also be noted that I am doing an awful lot of typing. Probably more than most people.

Chuck

On May 4, 2018, at 11:29 AM, FlickType <hello@flicktype.com> wrote:

Thanks Chuck. Anyone else getting these memory warnings?

Kosta

On May 4, 2018, at 11:20, Chuck Dean <cadean329@gmail.com> wrote:

I was trying to reply to a post in the ViPhone group, and the custom keyboard locked up and I couldn't do anything with it.

(I had to go to the iOS keyboard, to finish this email because the memory warning keeps coming up. I am dictating this.)

Just now as I was trying to type this with Fliktype custom keyboard, the memory warning came back, and would not let me do anything.
At this time I don’t think I can use the custom keyboard to reliably enter text in any field. When it works, it works great, but it seem to lock up on me a lot.

Chuck


Re: Build 55

Benny Barber
 

Kosta,

I noticed a small issue when toggling between the custom keyboard and an editable app. For example, if I open the iOS messages app, then open the custom keyboard, accidentally enter a character, delete everything and then go back to the messages app; a space has been entered into the edit field at the start. No big deal, but something. Thanks.

Benny

On May 4, 2018, at 12:32 AM, FlickType <hello@flicktype.com> wrote:

- Fixed audio latency. Hopefully it should now feel more like the main app, apart from the tap feedback delay. Please note: you must set VoiceOver typing feedback to "Nothing", otherwise the announcements will be laggy and sound like the voice has a cold and a stutter - no kidding. For some reason the iOS announcements are lower-quality as well as delayed, and because of the delay they almost immediately interrupt the FlickType announcements.
- You can now type your custom dictionary words, as well as some additional built-in words. You must run the main app once after updating for your words to carry over.
- Improved memory management. Hopefully you won't get those memory warnings any more, fingers crossed.
- First word in mail app should now be correctly capitalized.



Re: Build 55 problem with financial App

Chuck Dean
 

FYI: I was curious if this problem was due to the update build 55, so I reverted to the previous build, the problem was also present in build 54.

Chuck

On May 4, 2018, at 10:27 AM, Chuck Dean <cadean329@gmail.com> wrote:

I found that I could go back to the iOS keyboard if I did a three finger flick down to dismiss the FlickType keyboard; then double tap in another text field, then the tap and hold would work.

Chuck

On May 4, 2018, at 10:02 AM, Chuck Dean <cadean329@gmail.com> wrote:

Fyi I tried this on another App that has a text field for entering dollar amounts, and had the same problem. The three finger swipe down would work, but the tap and hold would not. This is only a check register App and is not a secure App like a financial App, so, I think it will probably miss behave in all amount fields.

Chuck

On May 4, 2018, at 9:52 AM, Chuck Dean <cadean329@gmail.com> wrote:

Build 55 problem with financial App
Hello, I went to pay a bill on my UBS bank App; when I needed to enter the amount, the FlickType keyboard was present and a one finger tap and hold would not switch to the iOS keyboard. I tried every gesture I know, but nothing would happen.
I had to exit the App, go to notes where I could bring up a text field, then I could switch to the iOS keyboard.
While I was flicking around on the FlickType keyboard trying to dismiss it, numbers were being entered into the text field, the number keypad must have been present under the FlickType custom keyboard. I really didn't want to send AT&T ten million dollars. :)
I had some other difficulties with the App when trying to enter my pin number and had to turn voice over off. I am not sure if this was FlickType related.


Chuck




Re: Build 55

Chuck Dean
 

It should also be noted that I am doing an awful lot of typing. Probably more than most people.

Chuck

On May 4, 2018, at 11:29 AM, FlickType <hello@flicktype.com> wrote:

Thanks Chuck. Anyone else getting these memory warnings?

Kosta

On May 4, 2018, at 11:20, Chuck Dean <cadean329@gmail.com> wrote:

I was trying to reply to a post in the ViPhone group, and the custom keyboard locked up and I couldn't do anything with it.

(I had to go to the iOS keyboard, to finish this email because the memory warning keeps coming up. I am dictating this.)

Just now as I was trying to type this with Fliktype custom keyboard, the memory warning came back, and would not let me do anything.
At this time I don’t think I can use the custom keyboard to reliably enter text in any field. When it works, it works great, but it seem to lock up on me a lot.

Chuck




Re: Build 55

 

Thanks Chuck. Anyone else getting these memory warnings?

Kosta

On May 4, 2018, at 11:20, Chuck Dean <cadean329@gmail.com> wrote:

I was trying to reply to a post in the ViPhone group, and the custom keyboard locked up and I couldn't do anything with it.

(I had to go to the iOS keyboard, to finish this email because the memory warning keeps coming up. I am dictating this.)

Just now as I was trying to type this with Fliktype custom keyboard, the memory warning came back, and would not let me do anything.
At this time I don’t think I can use the custom keyboard to reliably enter text in any field. When it works, it works great, but it seem to lock up on me a lot.

Chuck



Build 55

Chuck Dean
 

I was trying to reply to a post in the ViPhone group, and the custom keyboard locked up and I couldn't do anything with it.

(I had to go to the iOS keyboard, to finish this email because the memory warning keeps coming up. I am dictating this.)

Just now as I was trying to type this with Fliktype custom keyboard, the memory warning came back, and would not let me do anything.
At this time I don’t think I can use the custom keyboard to reliably enter text in any field. When it works, it works great, but it seem to lock up on me a lot.

Chuck


Re: Build55

Chuck Dean
 

Ok, so this is a diagnostic tool and not a warning from my iPhone. I had to do a reboot in order to write this email. I got the memory warning! That wouldn't go away. When I restarted this email there was a large lag while typing. I remember Fleksy doing this, so I turned off voice over and turned it back on; now there is no lag. Using iPhone eight running iOS eleven point three point one.

Chuck

On May 4, 2018, at 12:04 AM, FlickType <hello@flicktype.com> wrote:

A little more information on the memory warnings:

Unlike an app, when a keyboard crashes for whatever reason, the system
quickly relaunches it so you might not even notice that a crash has
occurred. Crashes can happen if the keyboard uses more memory than the
frugal amount that iOS allows. Previously, I didn't announce the memory
warnings, but the keyboard still crashed way too frequently. By adding the
warnings, I can at least get a sense from your reports about how many of
the crashes are due to memory limits, and if my attempts to improve memory
usage are having any impact. Once I add some analytics code, those warnings
can be reported directly through that system instead, so you will not have
to ever endure the message. Of course the keyboard might still be crashing
until the root cause is addressed and the memory usage becomes acceptable
by iOS.

- Kosta

- To join our beta, please send an email here
<beta+subscribe@flicktype.groups.io?subject=Subscribe&body=empty>
- Browse all our forum topics <https://flicktype.groups.io/g/hello/topics>
- Post to our forum <hello@flicktype.groups.io>
- Join our forum <hello+subscribe@flicktype.groups.io>
- Help & support <http://www.flicktype.com/help>
- Follow us on Twitter <https://twitter.com/FlickType>

http://flicktype.com



On Thu, May 3, 2018 at 11:54 PM, Chuck Dean <cadean329@gmail.com> wrote:

Hi Kosta, I just got the memory warning again, but if I continue to type
it seems to be ok. Oops, I spoke too soon. I just got the message two more
times, but I can keep on typing. It usually appears after I flick down to
select another prediction. Otherwise, this is typing great!

Chuck





Re: Build 55 problem with financial App

Chuck Dean
 

I found that I could go back to the iOS keyboard if I did a three finger flick down to dismiss the FlickType keyboard; then double tap in another text field, then the tap and hold would work.

Chuck

On May 4, 2018, at 10:02 AM, Chuck Dean <cadean329@gmail.com> wrote:

Fyi I tried this on another App that has a text field for entering dollar amounts, and had the same problem. The three finger swipe down would work, but the tap and hold would not. This is only a check register App and is not a secure App like a financial App, so, I think it will probably miss behave in all amount fields.

Chuck

On May 4, 2018, at 9:52 AM, Chuck Dean <cadean329@gmail.com> wrote:

Build 55 problem with financial App
Hello, I went to pay a bill on my UBS bank App; when I needed to enter the amount, the FlickType keyboard was present and a one finger tap and hold would not switch to the iOS keyboard. I tried every gesture I know, but nothing would happen.
I had to exit the App, go to notes where I could bring up a text field, then I could switch to the iOS keyboard.
While I was flicking around on the FlickType keyboard trying to dismiss it, numbers were being entered into the text field, the number keypad must have been present under the FlickType custom keyboard. I really didn't want to send AT&T ten million dollars. :)
I had some other difficulties with the App when trying to enter my pin number and had to turn voice over off. I am not sure if this was FlickType related.


Chuck



1721 - 1740 of 2168