Date   

Re: Build 63 and beta release plan

George Cham
 

Sure does.

Kind Regards,

George Cham


________________________________
From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of FlickType <@FlickType>
Sent: Thursday, May 10, 2018 1:18:34 PM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 63 and beta release plan

Thank you George. The message to open the main app is only announced if you update from an old build which doesn't have the custom keyboard, to a build that includes it. If you've already opened the main app at least once since then, you won't get that message. Does that make sense?

I will add you as a moderator to the beta group, thanks again.

- Kosta


Re: Build 63 and beta release plan

 

Thank you George. The message to open the main app is only announced if you update from an old build which doesn't have the custom keyboard, to a build that includes it. If you've already opened the main app at least once since then, you won't get that message. Does that make sense?

I will add you as a moderator to the beta group, thanks again.

- Kosta


Re: Build 63 and beta release plan

George Cham
 

Hi costa, I've just updated to build63. When I launched the custom keyboard, I did not get a message to open the main App. I would be happy to answer any questions in the beta group.

Kind Regards,

George Cham


________________________________
From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of FlickType <@FlickType>
Sent: Thursday, May 10, 2018 12:16:34 PM
To: alpha@flicktype.groups.io
Subject: [FlickType-alpha] Build 63 and beta release plan

Hi all,

The only change in this build, apart from some internal code reshuffling, is to announce the need to open the main FlickType app before the first use of the custom keyboard. As you can probably guess, we are very eager to share this build with the larger beta group, smile. To do this, we need to cover three things:

First, we need to make sure that there's no major usability issues, apart from the functionality that's still missing. If something is majorly broken, or if things are working perfectly, please let us know either way.
Second, we need to make sure that the experience for new users is acceptable, keeping in mind this is still very much in beta. To ensure a good on-boarding experience, we'd love your input on the updated instructions here: https://flicktype.groups.io/g/alpha/wiki/FlickType-custom-keyboard . If there's anything that doesn't make sense, is missing, or could otherwise be expressed more clearly, please let us know. And if there's any issues you notice with the update flow from the App Store build to this build, we'd love to know that as well.
Finally, we expect a large number of questions to come from the beta group during the first few days. If anyone would like to help us answer the common questions, please let us know so we can make you a moderator in the beta group. We'd love to have as much help there as possible, smile.

And if there's anything else you want to bring up regarding the upcoming beta release, we'd love to hear. In the event that everything is ready and working smoothly, we'd love to release to beta as soon as tomorrow, smile.

Thank you,
Kosta & Ashley

PS: I will shortly answer your questions and comments from the last day or so in a separate email.


Build 63 and beta release plan

 

Hi all,

The only change in this build, apart from some internal code reshuffling, is to announce the need to open the main FlickType app before the first use of the custom keyboard. As you can probably guess, we are very eager to share this build with the larger beta group, smile. To do this, we need to cover three things:

First, we need to make sure that there's no major usability issues, apart from the functionality that's still missing. If something is majorly broken, or if things are working perfectly, please let us know either way.
Second, we need to make sure that the experience for new users is acceptable, keeping in mind this is still very much in beta. To ensure a good on-boarding experience, we'd love your input on the updated instructions here: https://flicktype.groups.io/g/alpha/wiki/FlickType-custom-keyboard . If there's anything that doesn't make sense, is missing, or could otherwise be expressed more clearly, please let us know. And if there's any issues you notice with the update flow from the App Store build to this build, we'd love to know that as well.
Finally, we expect a large number of questions to come from the beta group during the first few days. If anyone would like to help us answer the common questions, please let us know so we can make you a moderator in the beta group. We'd love to have as much help there as possible, smile.

And if there's anything else you want to bring up regarding the upcoming beta release, we'd love to hear. In the event that everything is ready and working smoothly, we'd love to release to beta as soon as tomorrow, smile.

Thank you,
Kosta & Ashley

PS: I will shortly answer your questions and comments from the last day or so in a separate email.


Re: FlickType 1.1.62

Michael Maslo
 

Ok great thanks for that.



Sincerely,, mike


On May 9, 2018 at 17:31, <Chuck Dean (mailto:cadean329@...)> wrote:





In the future, when we can manually input text on the custom keyboard, we should be able to insert these text replacements. In the old Fleksy app all I had to do is manually insert each letter of the shortcut, and then flick right. The letters would be the first prediction, and the text replacement was usually the second or third.

On May 9, 2018, at 3:13 PM, David Nason <dnason@...> wrote:

Hi Mike. No emoji cannot, as yet at least, be done in the FlickType keyboard. We were discussing the best ways to type emoji using the regular keyboard and the emoji keyboard.
Thanks to Apple's terrible implementation of switching between multiple keyboards, having three active keyboards is no fun in my opinion. So I am trying out Chuck's method of using text replacement shortcuts instead of the emoji keyboard, allowing me to disable the emoji keyboard altogether, and so have only the standard English keyboard and FlickType active.

Dave
On 9 May 2018, at 23:00, Michael Maslo <michaelmaslo04@...> wrote:




Hello list, maybe I missed this thread but was wondering how to Do emotes. any help will be greatly appreciated.



Sincerely,, mike





On May 9, 2018 at 15:34, <Chuck Dean (mailto:cadean329@...)> wrote:




Looks like someone has figured out the emoji shortcuts. 😎

On May 9, 2018, at 1:24 PM, David Nason <dnason@...> wrote:

So far so good ☺️
On 9 May 2018, at 20:33, Paul Sutton <sutty_p@...> wrote:


All things seen to be working for me in this latest build but have only been testing for a few minutes. Here's hoping that everything will be ok. Keep up the good work, Paul.
On 9 May 2018, at 20:14, Chanelle Allen <chanellem.allen@...> wrote:


Hello,
The newest version of FlickType version 1.1.62 is working perfectly on my phone though I have not experienced the issues addressed in this update. Thank you, Kosta, for your amazing work and quick app releases!
Chanelle











Re: FlickType 1.1.62

Chuck Dean
 

In the future, when we can manually input text on the custom keyboard, we should be able to insert these text replacements. In the old Fleksy app all I had to do is manually insert each letter of the shortcut, and then flick right. The letters would be the first prediction, and the text replacement was usually the second or third.

On May 9, 2018, at 3:13 PM, David Nason <dnason@...> wrote:

Hi Mike. No emoji cannot, as yet at least, be done in the FlickType keyboard. We were discussing the best ways to type emoji using the regular keyboard and the emoji keyboard.
Thanks to Apple's terrible implementation of switching between multiple keyboards, having three active keyboards is no fun in my opinion. So I am trying out Chuck's method of using text replacement shortcuts instead of the emoji keyboard, allowing me to disable the emoji keyboard altogether, and so have only the standard English keyboard and FlickType active.

Dave
On 9 May 2018, at 23:00, Michael Maslo <michaelmaslo04@...> wrote:




Hello list, maybe I missed this thread but was wondering how to Do emotes. any help will be greatly appreciated.



Sincerely,, mike





On May 9, 2018 at 15:34, <Chuck Dean (mailto:cadean329@...)> wrote:




Looks like someone has figured out the emoji shortcuts. 😎

On May 9, 2018, at 1:24 PM, David Nason <dnason@...> wrote:

So far so good ☺️
On 9 May 2018, at 20:33, Paul Sutton <sutty_p@...> wrote:


All things seen to be working for me in this latest build but have only been testing for a few minutes. Here's hoping that everything will be ok. Keep up the good work, Paul.
On 9 May 2018, at 20:14, Chanelle Allen <chanellem.allen@...> wrote:


Hello,
The newest version of FlickType version 1.1.62 is working perfectly on my phone though I have not experienced the issues addressed in this update. Thank you, Kosta, for your amazing work and quick app releases!
Chanelle









Re: FlickType 1.1.62

David Nason
 

Hi Mike. No emoji cannot, as yet at least, be done in the FlickType keyboard. We were discussing the best ways to type emoji using the regular keyboard and the emoji keyboard.
Thanks to Apple's terrible implementation of switching between multiple keyboards, having three active keyboards is no fun in my opinion. So I am trying out Chuck's method of using text replacement shortcuts instead of the emoji keyboard, allowing me to disable the emoji keyboard altogether, and so have only the standard English keyboard and FlickType active.

Dave

On 9 May 2018, at 23:00, Michael Maslo <michaelmaslo04@...> wrote:




Hello list, maybe I missed this thread but was wondering how to Do emotes. any help will be greatly appreciated.



Sincerely,, mike





On May 9, 2018 at 15:34, <Chuck Dean (mailto:cadean329@...)> wrote:




Looks like someone has figured out the emoji shortcuts. 😎

On May 9, 2018, at 1:24 PM, David Nason <dnason@...> wrote:

So far so good ☺️
On 9 May 2018, at 20:33, Paul Sutton <sutty_p@...> wrote:


All things seen to be working for me in this latest build but have only been testing for a few minutes. Here's hoping that everything will be ok. Keep up the good work, Paul.
On 9 May 2018, at 20:14, Chanelle Allen <chanellem.allen@...> wrote:


Hello,
The newest version of FlickType version 1.1.62 is working perfectly on my phone though I have not experienced the issues addressed in this update. Thank you, Kosta, for your amazing work and quick app releases!
Chanelle








Re: FlickType 1.1.62

Michael Maslo
 

Hello list, maybe I missed this thread but was wondering how to Do emotes. any help will be greatly appreciated.



Sincerely,, mike


On May 9, 2018 at 15:34, <Chuck Dean (mailto:cadean329@...)> wrote:




Looks like someone has figured out the emoji shortcuts. 😎

On May 9, 2018, at 1:24 PM, David Nason <dnason@...> wrote:

So far so good ☺️
On 9 May 2018, at 20:33, Paul Sutton <sutty_p@...> wrote:


All things seen to be working for me in this latest build but have only been testing for a few minutes. Here's hoping that everything will be ok. Keep up the good work, Paul.
On 9 May 2018, at 20:14, Chanelle Allen <chanellem.allen@...> wrote:


Hello,
The newest version of FlickType version 1.1.62 is working perfectly on my phone though I have not experienced the issues addressed in this update. Thank you, Kosta, for your amazing work and quick app releases!
Chanelle







Re: Build 62

Chuck Dean
 

Another way would be to use a two finger swipe up and down to scroll through the keyboards.

On May 9, 2018, at 2:18 PM, Chuck Dean <cadean329@...> wrote:

Build 62
Hello,
I was wondering if the two buttons on the lower left and lower right could be used to switch keyboards. For example. If I am in the custom keyboard and I hit the lower right button, I would go to the iOS keyboard. If I hit it again I would go to the numbers keyboard. If I hit it again I would go to the symbols keyboard, and if I hit it again I would go to the emoji keyboard.
Then using the lower left button would reverse the sequence.
So if I was in the custom keyboard and hit the lower left button, I would go to the emoji keyboard, and if I hit it again I would go to the symbols keyboard, etc.
So, is this a good or bad idea?
Chuck


Build 62

Chuck Dean
 

Build 62
Hello,
I was wondering if the two buttons on the lower left and lower right could be used to switch keyboards. For example. If I am in the custom keyboard and I hit the lower right button, I would go to the iOS keyboard. If I hit it again I would go to the numbers keyboard. If I hit it again I would go to the symbols keyboard, and if I hit it again I would go to the emoji keyboard.
Then using the lower left button would reverse the sequence.
So if I was in the custom keyboard and hit the lower left button, I would go to the emoji keyboard, and if I hit it again I would go to the symbols keyboard, etc.
So, is this a good or bad idea?
Chuck


Re: FlickType 1.1.62

Chuck Dean
 

Looks like someone has figured out the emoji shortcuts. 😎

On May 9, 2018, at 1:24 PM, David Nason <dnason@...> wrote:

So far so good ☺️
On 9 May 2018, at 20:33, Paul Sutton <sutty_p@...> wrote:


All things seen to be working for me in this latest build but have only been testing for a few minutes. Here's hoping that everything will be ok. Keep up the good work, Paul.
On 9 May 2018, at 20:14, Chanelle Allen <chanellem.allen@...> wrote:


Hello,
The newest version of FlickType version 1.1.62 is working perfectly on my phone though I have not experienced the issues addressed in this update. Thank you, Kosta, for your amazing work and quick app releases!
Chanelle





Re: FlickType 1.1.62

David Nason
 

So far so good ☺️

On 9 May 2018, at 20:33, Paul Sutton <sutty_p@...> wrote:


All things seen to be working for me in this latest build but have only been testing for a few minutes. Here's hoping that everything will be ok. Keep up the good work, Paul.
On 9 May 2018, at 20:14, Chanelle Allen <chanellem.allen@...> wrote:


Hello,
The newest version of FlickType version 1.1.62 is working perfectly on my phone though I have not experienced the issues addressed in this update. Thank you, Kosta, for your amazing work and quick app releases!
Chanelle




Build 62

Chuck Dean
 

Build 62
Hello, I like the new look of the keyboard, it is not so in my face. But it did take almost two minutes to get used to. :)
Everything else is running good.


Chuck


Re: FlickType 1.1.62

Paul Sutton
 

All things seen to be working for me in this latest build but have only been testing for a few minutes. Here's hoping that everything will be ok. Keep up the good work, Paul.

On 9 May 2018, at 20:14, Chanelle Allen <chanellem.allen@...> wrote:


Hello,
The newest version of FlickType version 1.1.62 is working perfectly on my phone though I have not experienced the issues addressed in this update. Thank you, Kosta, for your amazing work and quick app releases!
Chanelle



Re: FlickType 1.1.62

George Cham
 

Wow! That's a big change.

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<https://aka.ms/qtex0l> for iOS
________________________________
From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Chanelle Allen <chanellem.allen@...>
Sent: Thursday, May 10, 2018 5:14:05 AM
To: alpha@flicktype.groups.io
Subject: [FlickType-alpha] FlickType 1.1.62


Hello,
The newest version of FlickType version 1.1.62 is working perfectly on my phone though I have not experienced the issues addressed in this update. Thank you, Kosta, for your amazing work and quick app releases!
Chanelle


Re: Build 61.

George Cham
 

Was just listening to eyes on success and FlickType. I then started thinking, is it possible to make FlickType the The

Kind Regards,

George Cham

Defult keyboard?
________________________________
From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Chuck Dean <cadean329@...>
Sent: Thursday, May 10, 2018 1:27:07 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 61.

No, I can type any word with double s.
Some of my shortcuts are the beginning of other words like s t for the phrase have a safe trip. So, when I type the word street, after I type the s and t, I will hear the tone indicating the shortcut, but the next letter will negate the operation.
I hope this makes sense, its a little hard to explain.

Chuck

On May 9, 2018, at 7:07 AM, Alan Lemly <@walemly> wrote:

Hi Chuck,

Thanks for providing the details of your emoji shortcut using text replacement. I'm just curious what happens with your smiley face with sunglasses example when you're entering a word that contains a double s. Do you get a smiley sunglasses replacement in such a case?

Alan Lemly

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf Of Salman Haider
Sent: Tuesday, May 08, 2018 11:37 PM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 61.

Thanks for your input guys.
It sounds like I wasn't the only one and there indeed is a bug in iOS as far as that is concerned. Removing the Emoji keyboard, definitely is one workaround.

Salman

On 5/8/18, Chuck Dean <cadean329@...> wrote:
Go to settings: general: keyboards: and select text replacement, which
used to be called shortcuts.


Now tap add.
In the phrase text field, you can put any thing you want to enter
quickly, such as; addresses, emails, phone numbers, words or sentences
you use frequently. And also emoji.

Once you have entered the text or emoji, go to the next text box
called shortcuts... Optional.
I usually use a two letter shortcut; for example my smiley face with
sunglasses is s s..
Now go to the upper right and tap save.
Now when you enter your two letter shortcut and then hit space. The
phrase will be entered.
Good luck.


Chuck

On May 8, 2018, at 4:40 PM, Chanelle Allen
<chanellem.allen@...>
wrote:


Hello,
My problems with switching keyboards were resolved after removing the
emoji keyboard as chuck did. When I switch between keyboards, I am
still not confident that my cursor will be in the correct location,
but FlickType is consistent. Alternating between keyboards while
typing is quick and nearly seamless. When I switch to the iOS
keyboard for editing and VoiceOver begins reading aloud, I worry that
the insertion point will change unless I am quick enough to set the
rotor to characters or words and begin flicking. I am just
discovering how easy it is to use the VoiceOver rotor while reading
through the message contents, switch to FlickType keyboard, and immediately begin typing at the cursor location.
Sometimes, when I switch between keyboards I forget to add a space
manually on the iOS keyboard before typing out a word. In
transitioning between the iOS keyboard and FlickType, however, a
space is automatically inserted. If I have entered something manually
on the iOS keyboard, I press space before switching back to
FlickType, but if I am inserting text, typing a space before
switching keyboards is not needed. By the way, chuck, how did you create emoji replacements?
I am so glad to be typing with the FlickType keyboard in responding
to this and other emails. Thanks again, Kosta.
Chanelle

On May 8, 2018, at 17:55, Chuck Dean <cadean329@...> wrote:

I was having similar problems switching keyboards, so I remove the
emoji keyboard from the list completely. I had a bunch of text
replacement shortcuts with emoji s in them, and they have been
retained. Considering that I don t use the emoji keyboard anyways
anymore. I don t think I need it on my list. Now I only have
Fliktype and the English US keyboard in the list. Works much better!

Chuck

On May 8, 2018, at 3:43 PM, Salman Haider
<salmanhaider.purdue@...> wrote:

I do want to add that the new release is working quite well for me
otherwise. Especially from the standpoint of prediction. It is as
good as the app itself, for me anyway. The only reason that I
refrain from using the FlickType custom keyboard generally is, the
one I explained in my previous email. The unpredictability and
inconsistency of switching back and forth between keyboards that
is. Especially when I need to edit text or add words that are not
in the FlickType dictionary. Great job to the FlickType team on
making such good progress with every update. If only this keyboard
switching issue could be resolved somehow. And again, it probably has nothing to do with FlickType. Its probably an iOS bug.
Salman



On May 8, 2018, at 6:35 PM, Salman Haider
<salmanhaider.purdue@...> wrote:

One of the issues that I consistently encounter is, when I perform
the tap and hold gesture to return to the iOS keyboard, sometimes I
get the emoji keyboard instead of the iOS keyboard. Other times, I
get back to the iOS keyboard like I should. I do not know why this
is, but it certainly causes a lot of irritation. Also, sometimes
when I double tap the next keyboard option on the iOS keyboard, it
switches to the emoji keyboard, even though the FlickType keyboard
is the one that should come up as that is next in the order of
keyboards I have. I do not think that these behaviors have anything
to do with FlickType itself, rather the implementation of custom
keyboards in iOS. But I am curious to know if others are having
this issue as well. Once again, I just want to reiterate that I
have changed the order of the keyboards in the iOS settings as
well. Yet, the tap and hold gesture continues to sometimes bring up
the emoji keyboard rather than the iOS keyboard. Not every single
time, but a lot of times. And also, the next keyboard, FlickType
button also sometimes brings up the emoji keyboard rather than the
FlickType keyboard. These behaviors have existed pretty much from
the first day that I installed the FlickType custom keyboard, so
its not version specific. If anyone can shed any light on this, or even has a possible workaround or solution, it would be much appreciated.
Salman


On May 8, 2018, at 3:07 PM, Chuck Dean <cadean329@...> wrote:


Hi Paul, I do that now by switching to the iOS keyboard with a
single tap and hold. Once I am in the iOS keyboard I can review my
text utilizing the the normal iPhone gestures. Then when I am ready
to type, I return to FlickType custom keyboard. The two keyboards
play well together.

Chuck

On May 8, 2018, at 11:50 AM, Paul Sutton <sutty_p@...>
wrote:

Hi everyone, build 61 is working really well for me. Obviously
their are the problem's that people have already addressed but for
me it's been a pretty good release. I would like to put an idea
out there. I don't know if it would work for everyone and to be
honest I don't even know if it is possible but I would love to
hear other peoples views on it. Its to do with reading back the
text you have written. I was thinking would it be possible to have
some sort of gesture which when performed, would then place
FlickType in some sort of review mode. With in this mode, other
previous gestures that you use for FlickType would now be used for
other purposes. Just for example instead of a single flick down
accessing the suggestion list, you could be able to flick between
lines, words, sentences and things like that and when you are
finished you perform another gesture to return back to the
standard FlickType keyboard. As I said, I don't know if it would work but I would find something like that useful.
Hi everyone, build 6 1 is working really well for me. Obviously
their are the problem's that people have already addressed but for
me it's been a pretty good release. I would like to put an idea
out there. I don't know if it would work for everyone and to be
honest I don't even know if it is possible but I would love to
hear other peoples views on it. Its to do with reading back the
text you have written. I was thinking would it be possible to have
some sort of gesture which when performed, would then place
FlickType in some sort of review mode. With in this mode, other
traveler previous gestures that you use for FlickType would now be
used for other purposes. Just for example instead of a single
flick down accessing the suggestion list, you could be able to
flick between lines, words, sentences and things like that and
when you are finished you perform another gesture to return back
to the standard FlickType keyboard. As I said, I don't know if it would work but I would find something like that useful.
Cheers, Paul. Hi everyone, build 6 1 is working really well for me.
Obviously their are the problem's that people have already
addressed but for me it's been a pretty good release. I would like
to put an idea out there. I don't know if it would work for
everyone and to be honest I don't even know if it is possible but
I would love to hear other peoples views on it. Its to do with
reading back the text you have written. I was thinking would it be
possible to have some sort of gesture which when performed, would
then place FlickType in some sort of review mode. With in this
mode, other traveler previous gestures that you use for FlickType
would now be used for other purposes. Just for example instead of
a single flick down accessing the suggestion list, you could be
able to flick between lines, words, sentences and things like that
and when you are finished you perform another gesture to return
back to the standard FlickType keyboard. As I said, I don't know if it would work but I would find something like that useful.
Cheers, Paul. Cheers, Paul.
On 8 May 2018, at 19:00, David Nason <dnason@...> wrote:

I'm seeing a huge improvement in the predictive engine in this
build, many thanks for getting to it sooner than I expected.

I experienced some strange behaviour earlier today when trying to
switch between my three keyboards, standard, emoji and FlickType.
VoiceOver would announce one keyboard, but that one was not on screen.
I had one instance of FlickType appearing to be on screen
visually to me, but not operating properly, and reading out
letters as I tapped, as if it were the standard keyboard on
screen. However I cannot reproduce any of this behavior now, so maybe it was just an anomaly.

Dave
On 8 May 2018, at 16:44, Chuck Dean <cadean329@...> wrote:

Build 61.
Hi Kosta,
The custom keyboard has started to crash when I write a long email.
It looks like it does when it does a slow start.
The only way I found to fix it is to hit the home button, then
every thing is lost.


Chuck
















--
Muhammad Salman Haider
(765) 586-6840






FlickType 1.1.62

Chanelle Allen
 

Hello,
The newest version of FlickType version 1.1.62 is working perfectly on my phone though I have not experienced the issues addressed in this update. Thank you, Kosta, for your amazing work and quick app releases!
Chanelle


Re: Build 61.

Chuck Dean
 

No, I can type any word with double s.
Some of my shortcuts are the beginning of other words like s t for the phrase have a safe trip. So, when I type the word street, after I type the s and t, I will hear the tone indicating the shortcut, but the next letter will negate the operation.
I hope this makes sense, its a little hard to explain.

Chuck

On May 9, 2018, at 7:07 AM, Alan Lemly <@walemly> wrote:

Hi Chuck,

Thanks for providing the details of your emoji shortcut using text replacement. I'm just curious what happens with your smiley face with sunglasses example when you're entering a word that contains a double s. Do you get a smiley sunglasses replacement in such a case?

Alan Lemly

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf Of Salman Haider
Sent: Tuesday, May 08, 2018 11:37 PM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 61.

Thanks for your input guys.
It sounds like I wasn't the only one and there indeed is a bug in iOS as far as that is concerned. Removing the Emoji keyboard, definitely is one workaround.

Salman

On 5/8/18, Chuck Dean <cadean329@...> wrote:
Go to settings: general: keyboards: and select text replacement, which
used to be called shortcuts.


Now tap add.
In the phrase text field, you can put any thing you want to enter
quickly, such as; addresses, emails, phone numbers, words or sentences
you use frequently. And also emoji.

Once you have entered the text or emoji, go to the next text box
called shortcuts... Optional.
I usually use a two letter shortcut; for example my smiley face with
sunglasses is s s..
Now go to the upper right and tap save.
Now when you enter your two letter shortcut and then hit space. The
phrase will be entered.
Good luck.


Chuck

On May 8, 2018, at 4:40 PM, Chanelle Allen
<chanellem.allen@...>
wrote:


Hello,
My problems with switching keyboards were resolved after removing the
emoji keyboard as chuck did. When I switch between keyboards, I am
still not confident that my cursor will be in the correct location,
but FlickType is consistent. Alternating between keyboards while
typing is quick and nearly seamless. When I switch to the iOS
keyboard for editing and VoiceOver begins reading aloud, I worry that
the insertion point will change unless I am quick enough to set the
rotor to characters or words and begin flicking. I am just
discovering how easy it is to use the VoiceOver rotor while reading
through the message contents, switch to FlickType keyboard, and immediately begin typing at the cursor location.
Sometimes, when I switch between keyboards I forget to add a space
manually on the iOS keyboard before typing out a word. In
transitioning between the iOS keyboard and FlickType, however, a
space is automatically inserted. If I have entered something manually
on the iOS keyboard, I press space before switching back to
FlickType, but if I am inserting text, typing a space before
switching keyboards is not needed. By the way, chuck, how did you create emoji replacements?
I am so glad to be typing with the FlickType keyboard in responding
to this and other emails. Thanks again, Kosta.
Chanelle

On May 8, 2018, at 17:55, Chuck Dean <cadean329@...> wrote:

I was having similar problems switching keyboards, so I remove the
emoji keyboard from the list completely. I had a bunch of text
replacement shortcuts with emoji s in them, and they have been
retained. Considering that I don t use the emoji keyboard anyways
anymore. I don t think I need it on my list. Now I only have
Fliktype and the English US keyboard in the list. Works much better!

Chuck

On May 8, 2018, at 3:43 PM, Salman Haider
<salmanhaider.purdue@...> wrote:

I do want to add that the new release is working quite well for me
otherwise. Especially from the standpoint of prediction. It is as
good as the app itself, for me anyway. The only reason that I
refrain from using the FlickType custom keyboard generally is, the
one I explained in my previous email. The unpredictability and
inconsistency of switching back and forth between keyboards that
is. Especially when I need to edit text or add words that are not
in the FlickType dictionary. Great job to the FlickType team on
making such good progress with every update. If only this keyboard
switching issue could be resolved somehow. And again, it probably has nothing to do with FlickType. Its probably an iOS bug.
Salman



On May 8, 2018, at 6:35 PM, Salman Haider
<salmanhaider.purdue@...> wrote:

One of the issues that I consistently encounter is, when I perform
the tap and hold gesture to return to the iOS keyboard, sometimes I
get the emoji keyboard instead of the iOS keyboard. Other times, I
get back to the iOS keyboard like I should. I do not know why this
is, but it certainly causes a lot of irritation. Also, sometimes
when I double tap the next keyboard option on the iOS keyboard, it
switches to the emoji keyboard, even though the FlickType keyboard
is the one that should come up as that is next in the order of
keyboards I have. I do not think that these behaviors have anything
to do with FlickType itself, rather the implementation of custom
keyboards in iOS. But I am curious to know if others are having
this issue as well. Once again, I just want to reiterate that I
have changed the order of the keyboards in the iOS settings as
well. Yet, the tap and hold gesture continues to sometimes bring up
the emoji keyboard rather than the iOS keyboard. Not every single
time, but a lot of times. And also, the next keyboard, FlickType
button also sometimes brings up the emoji keyboard rather than the
FlickType keyboard. These behaviors have existed pretty much from
the first day that I installed the FlickType custom keyboard, so
its not version specific. If anyone can shed any light on this, or even has a possible workaround or solution, it would be much appreciated.
Salman


On May 8, 2018, at 3:07 PM, Chuck Dean <cadean329@...> wrote:


Hi Paul, I do that now by switching to the iOS keyboard with a
single tap and hold. Once I am in the iOS keyboard I can review my
text utilizing the the normal iPhone gestures. Then when I am ready
to type, I return to FlickType custom keyboard. The two keyboards
play well together.

Chuck

On May 8, 2018, at 11:50 AM, Paul Sutton <sutty_p@...>
wrote:

Hi everyone, build 61 is working really well for me. Obviously
their are the problem's that people have already addressed but for
me it's been a pretty good release. I would like to put an idea
out there. I don't know if it would work for everyone and to be
honest I don't even know if it is possible but I would love to
hear other peoples views on it. Its to do with reading back the
text you have written. I was thinking would it be possible to have
some sort of gesture which when performed, would then place
FlickType in some sort of review mode. With in this mode, other
previous gestures that you use for FlickType would now be used for
other purposes. Just for example instead of a single flick down
accessing the suggestion list, you could be able to flick between
lines, words, sentences and things like that and when you are
finished you perform another gesture to return back to the
standard FlickType keyboard. As I said, I don't know if it would work but I would find something like that useful.
Hi everyone, build 6 1 is working really well for me. Obviously
their are the problem's that people have already addressed but for
me it's been a pretty good release. I would like to put an idea
out there. I don't know if it would work for everyone and to be
honest I don't even know if it is possible but I would love to
hear other peoples views on it. Its to do with reading back the
text you have written. I was thinking would it be possible to have
some sort of gesture which when performed, would then place
FlickType in some sort of review mode. With in this mode, other
traveler previous gestures that you use for FlickType would now be
used for other purposes. Just for example instead of a single
flick down accessing the suggestion list, you could be able to
flick between lines, words, sentences and things like that and
when you are finished you perform another gesture to return back
to the standard FlickType keyboard. As I said, I don't know if it would work but I would find something like that useful.
Cheers, Paul. Hi everyone, build 6 1 is working really well for me.
Obviously their are the problem's that people have already
addressed but for me it's been a pretty good release. I would like
to put an idea out there. I don't know if it would work for
everyone and to be honest I don't even know if it is possible but
I would love to hear other peoples views on it. Its to do with
reading back the text you have written. I was thinking would it be
possible to have some sort of gesture which when performed, would
then place FlickType in some sort of review mode. With in this
mode, other traveler previous gestures that you use for FlickType
would now be used for other purposes. Just for example instead of
a single flick down accessing the suggestion list, you could be
able to flick between lines, words, sentences and things like that
and when you are finished you perform another gesture to return
back to the standard FlickType keyboard. As I said, I don't know if it would work but I would find something like that useful.
Cheers, Paul. Cheers, Paul.
On 8 May 2018, at 19:00, David Nason <dnason@...> wrote:

I'm seeing a huge improvement in the predictive engine in this
build, many thanks for getting to it sooner than I expected.

I experienced some strange behaviour earlier today when trying to
switch between my three keyboards, standard, emoji and FlickType.
VoiceOver would announce one keyboard, but that one was not on screen.
I had one instance of FlickType appearing to be on screen
visually to me, but not operating properly, and reading out
letters as I tapped, as if it were the standard keyboard on
screen. However I cannot reproduce any of this behavior now, so maybe it was just an anomaly.

Dave
On 8 May 2018, at 16:44, Chuck Dean <cadean329@...> wrote:

Build 61.
Hi Kosta,
The custom keyboard has started to crash when I write a long email.
It looks like it does when it does a slow start.
The only way I found to fix it is to hit the home button, then
every thing is lost.


Chuck
















--
Muhammad Salman Haider
(765) 586-6840






Re: Build 61.

 

Hi Chuck,

Thanks for providing the details of your emoji shortcut using text replacement. I'm just curious what happens with your smiley face with sunglasses example when you're entering a word that contains a double s. Do you get a smiley sunglasses replacement in such a case?

Alan Lemly

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf Of Salman Haider
Sent: Tuesday, May 08, 2018 11:37 PM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 61.

Thanks for your input guys.
It sounds like I wasn't the only one and there indeed is a bug in iOS as far as that is concerned. Removing the Emoji keyboard, definitely is one workaround.

Salman

On 5/8/18, Chuck Dean <cadean329@...> wrote:
Go to settings: general: keyboards: and select text replacement, which
used to be called shortcuts.


Now tap add.
In the phrase text field, you can put any thing you want to enter
quickly, such as; addresses, emails, phone numbers, words or sentences
you use frequently. And also emoji.

Once you have entered the text or emoji, go to the next text box
called shortcuts... Optional.
I usually use a two letter shortcut; for example my smiley face with
sunglasses is s s..
Now go to the upper right and tap save.
Now when you enter your two letter shortcut and then hit space. The
phrase will be entered.
Good luck.


Chuck

On May 8, 2018, at 4:40 PM, Chanelle Allen
<chanellem.allen@...>
wrote:


Hello,
My problems with switching keyboards were resolved after removing the
emoji keyboard as chuck did. When I switch between keyboards, I am
still not confident that my cursor will be in the correct location,
but FlickType is consistent. Alternating between keyboards while
typing is quick and nearly seamless. When I switch to the iOS
keyboard for editing and VoiceOver begins reading aloud, I worry that
the insertion point will change unless I am quick enough to set the
rotor to characters or words and begin flicking. I am just
discovering how easy it is to use the VoiceOver rotor while reading
through the message contents, switch to FlickType keyboard, and immediately begin typing at the cursor location.
Sometimes, when I switch between keyboards I forget to add a space
manually on the iOS keyboard before typing out a word. In
transitioning between the iOS keyboard and FlickType, however, a
space is automatically inserted. If I have entered something manually
on the iOS keyboard, I press space before switching back to
FlickType, but if I am inserting text, typing a space before
switching keyboards is not needed. By the way, chuck, how did you create emoji replacements?
I am so glad to be typing with the FlickType keyboard in responding
to this and other emails. Thanks again, Kosta.
Chanelle

On May 8, 2018, at 17:55, Chuck Dean <cadean329@...> wrote:

I was having similar problems switching keyboards, so I remove the
emoji keyboard from the list completely. I had a bunch of text
replacement shortcuts with emoji s in them, and they have been
retained. Considering that I don t use the emoji keyboard anyways
anymore. I don t think I need it on my list. Now I only have
Fliktype and the English US keyboard in the list. Works much better!

Chuck

On May 8, 2018, at 3:43 PM, Salman Haider
<salmanhaider.purdue@...> wrote:

I do want to add that the new release is working quite well for me
otherwise. Especially from the standpoint of prediction. It is as
good as the app itself, for me anyway. The only reason that I
refrain from using the FlickType custom keyboard generally is, the
one I explained in my previous email. The unpredictability and
inconsistency of switching back and forth between keyboards that
is. Especially when I need to edit text or add words that are not
in the FlickType dictionary. Great job to the FlickType team on
making such good progress with every update. If only this keyboard
switching issue could be resolved somehow. And again, it probably has nothing to do with FlickType. Its probably an iOS bug.
Salman



On May 8, 2018, at 6:35 PM, Salman Haider
<salmanhaider.purdue@...> wrote:

One of the issues that I consistently encounter is, when I perform
the tap and hold gesture to return to the iOS keyboard, sometimes I
get the emoji keyboard instead of the iOS keyboard. Other times, I
get back to the iOS keyboard like I should. I do not know why this
is, but it certainly causes a lot of irritation. Also, sometimes
when I double tap the next keyboard option on the iOS keyboard, it
switches to the emoji keyboard, even though the FlickType keyboard
is the one that should come up as that is next in the order of
keyboards I have. I do not think that these behaviors have anything
to do with FlickType itself, rather the implementation of custom
keyboards in iOS. But I am curious to know if others are having
this issue as well. Once again, I just want to reiterate that I
have changed the order of the keyboards in the iOS settings as
well. Yet, the tap and hold gesture continues to sometimes bring up
the emoji keyboard rather than the iOS keyboard. Not every single
time, but a lot of times. And also, the next keyboard, FlickType
button also sometimes brings up the emoji keyboard rather than the
FlickType keyboard. These behaviors have existed pretty much from
the first day that I installed the FlickType custom keyboard, so
its not version specific. If anyone can shed any light on this, or even has a possible workaround or solution, it would be much appreciated.
Salman


On May 8, 2018, at 3:07 PM, Chuck Dean <cadean329@...> wrote:


Hi Paul, I do that now by switching to the iOS keyboard with a
single tap and hold. Once I am in the iOS keyboard I can review my
text utilizing the the normal iPhone gestures. Then when I am ready
to type, I return to FlickType custom keyboard. The two keyboards
play well together.

Chuck

On May 8, 2018, at 11:50 AM, Paul Sutton <sutty_p@...>
wrote:

Hi everyone, build 61 is working really well for me. Obviously
their are the problem's that people have already addressed but for
me it's been a pretty good release. I would like to put an idea
out there. I don't know if it would work for everyone and to be
honest I don't even know if it is possible but I would love to
hear other peoples views on it. Its to do with reading back the
text you have written. I was thinking would it be possible to have
some sort of gesture which when performed, would then place
FlickType in some sort of review mode. With in this mode, other
previous gestures that you use for FlickType would now be used for
other purposes. Just for example instead of a single flick down
accessing the suggestion list, you could be able to flick between
lines, words, sentences and things like that and when you are
finished you perform another gesture to return back to the
standard FlickType keyboard. As I said, I don't know if it would work but I would find something like that useful.
Hi everyone, build 6 1 is working really well for me. Obviously
their are the problem's that people have already addressed but for
me it's been a pretty good release. I would like to put an idea
out there. I don't know if it would work for everyone and to be
honest I don't even know if it is possible but I would love to
hear other peoples views on it. Its to do with reading back the
text you have written. I was thinking would it be possible to have
some sort of gesture which when performed, would then place
FlickType in some sort of review mode. With in this mode, other
traveler previous gestures that you use for FlickType would now be
used for other purposes. Just for example instead of a single
flick down accessing the suggestion list, you could be able to
flick between lines, words, sentences and things like that and
when you are finished you perform another gesture to return back
to the standard FlickType keyboard. As I said, I don't know if it would work but I would find something like that useful.
Cheers, Paul. Hi everyone, build 6 1 is working really well for me.
Obviously their are the problem's that people have already
addressed but for me it's been a pretty good release. I would like
to put an idea out there. I don't know if it would work for
everyone and to be honest I don't even know if it is possible but
I would love to hear other peoples views on it. Its to do with
reading back the text you have written. I was thinking would it be
possible to have some sort of gesture which when performed, would
then place FlickType in some sort of review mode. With in this
mode, other traveler previous gestures that you use for FlickType
would now be used for other purposes. Just for example instead of
a single flick down accessing the suggestion list, you could be
able to flick between lines, words, sentences and things like that
and when you are finished you perform another gesture to return
back to the standard FlickType keyboard. As I said, I don't know if it would work but I would find something like that useful.
Cheers, Paul. Cheers, Paul.
On 8 May 2018, at 19:00, David Nason <dnason@...> wrote:

I'm seeing a huge improvement in the predictive engine in this
build, many thanks for getting to it sooner than I expected.

I experienced some strange behaviour earlier today when trying to
switch between my three keyboards, standard, emoji and FlickType.
VoiceOver would announce one keyboard, but that one was not on screen.
I had one instance of FlickType appearing to be on screen
visually to me, but not operating properly, and reading out
letters as I tapped, as if it were the standard keyboard on
screen. However I cannot reproduce any of this behavior now, so maybe it was just an anomaly.

Dave
On 8 May 2018, at 16:44, Chuck Dean <cadean329@...> wrote:

Build 61.
Hi Kosta,
The custom keyboard has started to crash when I write a long email.
It looks like it does when it does a slow start.
The only way I found to fix it is to hit the home button, then
every thing is lost.


Chuck
















--
Muhammad Salman Haider
(765) 586-6840


Re: Build 61.

Chuck Dean
 

I use emoji in some of my text replacements. For example, if I want to insert a smiley face, I type c c and then I hit space to enter it.


Chuck

On May 8, 2018, at 11:29 PM, George Cham <George.cham@...> wrote:

Did I miss something, what did chuck do with text replacement?

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<https://aka.ms/qtex0l> for iOS
________________________________
From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of David Nason <dnason@...>
Sent: Wednesday, May 9, 2018 4:26:33 PM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 61.

Chuck, that is nothing short of genius! I use text replacement, but had never thought of using it in that way. Thanks for the tip sir 😀

Dave
On 9 May 2018, at 05:37, Salman Haider <salmanhaider.purdue@...> wrote:

Thanks for your input guys.
It sounds like I wasn't the only one and there indeed is a bug in iOS
as far as that is concerned. Removing the Emoji keyboard, definitely
is one workaround.

Salman

On 5/8/18, Chuck Dean <cadean329@...> wrote:
Go to settings: general: keyboards: and select text replacement, which used
to be called shortcuts.


Now tap add.
In the phrase text field, you can put any thing you want to enter quickly,
such as; addresses, emails, phone numbers, words or sentences you use
frequently. And also emoji.

Once you have entered the text or emoji, go to the next text box called
shortcuts... Optional.
I usually use a two letter shortcut; for example my smiley face with
sunglasses is s s..
Now go to the upper right and tap save.
Now when you enter your two letter shortcut and then hit space. The phrase
will be entered.
Good luck.


Chuck

On May 8, 2018, at 4:40 PM, Chanelle Allen <chanellem.allen@...>
wrote:


Hello,
My problems with switching keyboards were resolved after removing the
emoji keyboard as chuck did. When I switch between keyboards, I am still
not confident that my cursor will be in the correct location, but
FlickType is consistent. Alternating between keyboards while typing is
quick and nearly seamless. When I switch to the iOS keyboard for editing
and VoiceOver begins reading aloud, I worry that the insertion point will
change unless I am quick enough to set the rotor to characters or words
and begin flicking. I am just discovering how easy it is to use the
VoiceOver rotor while reading through the message contents, switch to
FlickType keyboard, and immediately begin typing at the cursor location.
Sometimes, when I switch between keyboards I forget to add a space
manually on the iOS keyboard before typing out a word. In transitioning
between the iOS keyboard and FlickType, however, a space is automatically
inserted. If I have entered something manually on the iOS keyboard, I
press space before switching back to FlickType, but if I am inserting
text, typing a space before switching keyboards is not needed. By the way,
chuck, how did you create emoji replacements?
I am so glad to be typing with the FlickType keyboard in responding to
this and other emails. Thanks again, Kosta.
Chanelle

On May 8, 2018, at 17:55, Chuck Dean <cadean329@...> wrote:

I was having similar problems switching keyboards, so I remove the emoji
keyboard from the list completely. I had a bunch of text replacement
shortcuts with emoji‘s in them, and they have been retained. Considering
that I don’t use the emoji keyboard anyways anymore. I don’t think I need
it on my list. Now I only have Fliktype and the English US keyboard in
the list. Works much better!

Chuck

On May 8, 2018, at 3:43 PM, Salman Haider
<salmanhaider.purdue@...> wrote:

I do want to add that the new release is working quite well for me
otherwise. Especially from the standpoint of prediction. It is as good
as the app itself, for me anyway. The only reason that I refrain from
using the FlickType custom keyboard generally is, the one I explained in
my previous email. The unpredictability and inconsistency of switching
back and forth between keyboards that is. Especially when I need to edit
text or add words that are not in the FlickType dictionary. Great job to
the FlickType team on making such good progress with every update. If
only this keyboard switching issue could be resolved somehow. And again,
it probably has nothing to do with FlickType. Its probably an iOS bug.
Salman



On May 8, 2018, at 6:35 PM, Salman Haider
<salmanhaider.purdue@...> wrote:

One of the issues that I consistently encounter is, when I perform the
tap and hold gesture to return to the iOS keyboard, sometimes I get the
emoji keyboard instead of the iOS keyboard. Other times, I get back to
the iOS keyboard like I should. I do not know why this is, but it
certainly causes a lot of irritation. Also, sometimes when I double tap
the next keyboard option on the iOS keyboard, it switches to the emoji
keyboard, even though the FlickType keyboard is the one that should come
up as that is next in the order of keyboards I have. I do not think that
these behaviors have anything to do with FlickType itself, rather the
implementation of custom keyboards in iOS. But I am curious to know if
others are having this issue as well. Once again, I just want to
reiterate that I have changed the order of the keyboards in the iOS
settings as well. Yet, the tap and hold gesture continues to sometimes
bring up the emoji keyboard rather than the iOS keyboard. Not every
single time, but a lot of times. And also, the next keyboard, FlickType
button also sometimes brings up the emoji keyboard rather than the
FlickType keyboard. These behaviors have existed pretty much from the
first day that I installed the FlickType custom keyboard, so its not
version specific. If anyone can shed any light on this, or even has a
possible workaround or solution, it would be much appreciated.
Salman


On May 8, 2018, at 3:07 PM, Chuck Dean <cadean329@...> wrote:


Hi Paul, I do that now by switching to the iOS keyboard with a single
tap and hold. Once I am in the iOS keyboard I can review my text
utilizing the the normal iPhone gestures. Then when I am ready to type,
I return to FlickType custom keyboard. The two keyboards play well
together.

Chuck

On May 8, 2018, at 11:50 AM, Paul Sutton <sutty_p@...>
wrote:

Hi everyone, build 61 is working really well for me. Obviously their
are the problem's that people have already addressed but for me it's
been a pretty good release. I would like to put an idea out there. I
don't know if it would work for everyone and to be honest I don't even
know if it is possible but I would love to hear other peoples views on
it. Its to do with reading back the text you have written. I was
thinking would it be possible to have some sort of gesture which when
performed, would then place FlickType in some sort of review mode. With
in this mode, other previous gestures that you use for FlickType would
now be used for other purposes. Just for example instead of a single
flick down accessing the suggestion list, you could be able to flick
between lines, words, sentences and things like that and when you are
finished you perform another gesture to return back to the standard
FlickType keyboard. As I said, I don't know if it would work but I
would find something like that useful.
Hi everyone, build 6 1 is working really well for me. Obviously their
are the problem's that people have already addressed but for me it's
been a pretty good release. I would like to put an idea out there. I
don't know if it would work for everyone and to be honest I don't even
know if it is possible but I would love to hear other peoples views on
it. Its to do with reading back the text you have written. I was
thinking would it be possible to have some sort of gesture which when
performed, would then place FlickType in some sort of review mode. With
in this mode, other traveler previous gestures that you use for
FlickType would now be used for other purposes. Just for example
instead of a single flick down accessing the suggestion list, you could
be able to flick between lines, words, sentences and things like that
and when you are finished you perform another gesture to return back to
the standard FlickType keyboard. As I said, I don't know if it would
work but I would find something like that useful.
Cheers, Paul. Hi everyone, build 6 1 is working really well for me.
Obviously their are the problem's that people have already addressed
but for me it's been a pretty good release. I would like to put an idea
out there. I don't know if it would work for everyone and to be honest
I don't even know if it is possible but I would love to hear other
peoples views on it. Its to do with reading back the text you have
written. I was thinking would it be possible to have some sort of
gesture which when performed, would then place FlickType in some sort
of review mode. With in this mode, other traveler previous gestures
that you use for FlickType would now be used for other purposes. Just
for example instead of a single flick down accessing the suggestion
list, you could be able to flick between lines, words, sentences and
things like that and when you are finished you perform another gesture
to return back to the standard FlickType keyboard. As I said, I don't
know if it would work but I would find something like that useful.
Cheers, Paul. Cheers, Paul.
On 8 May 2018, at 19:00, David Nason <dnason@...> wrote:

I'm seeing a huge improvement in the predictive engine in this build,
many thanks for getting to it sooner than I expected.

I experienced some strange behaviour earlier today when trying to
switch between my three keyboards, standard, emoji and FlickType.
VoiceOver would announce one keyboard, but that one was not on screen.
I had one instance of FlickType appearing to be on screen visually to
me, but not operating properly, and reading out letters as I tapped,
as if it were the standard keyboard on screen. However I cannot
reproduce any of this behavior now, so maybe it was just an anomaly.

Dave
On 8 May 2018, at 16:44, Chuck Dean <cadean329@...> wrote:

Build 61.
Hi Kosta,
The custom keyboard has started to crash when I write a long email.
It looks like it does when it does a slow start.
The only way I found to fix it is to hit the home button, then every
thing is lost.


Chuck
















--
Muhammad Salman Haider
(765) 586-6840