Date   

Re: Bild 75

Matthew Janusauskas
 

Force touch on the far left edge of the screen is the gesture to activate the iOS app switcher.

On May 29, 2018, at 7:19 PM, Chuck Dean <cadean329@...> wrote:


Hi Kosta,
I don't think there is a gesture for the app switcher, I think this is an iOS fluke when to close to the left side of the screen.
I had similar problems when trying to use 3D touch to enter a capital Q.


Chuck

On May 29, 2018, at 5:01 PM, FlickType <@FlickType> wrote:

What is the app switcher gesture that is similar to the new line gesture? I’m not aware of one...

Kosta

On May 29, 2018, at 16:58, Chanelle Allen <chanellem.allen@...> wrote:

Hello,
I can confirm that FlickType no longer inserts a space after deleting manually typed characters. I knew that FlickType did not announce new lines but I didn't realize that one swipe left would delete multiple line breaks until now. As of a few minutes ago, I have performed the new line gesture and ended up in the app Switcher. Maybe my finger was further to the left on the screen than usual, so hopefully, this quirk is not encountered by anyone else.

I am just glad that one of the spacing problems is resolved.😀 now, let's see how that emoji came out with FlickType and VoiceOver. Chanelle

On May 29, 2018, at 17:45, Paul Sutton <sutty_p@...> wrote:

Hi,
Just reporting that this build has fixed the inserting a space during manual typing error. Thank you.
I also wanted too add that VoiceOver does not amounts when you are deleting a new line. Also, when inserting multiple new lines, a single swipe left will delete all of the new lines that you have entered rather than one at a time..
The last thing that I would like to ask is when swiping left and right with two fingers to read word by word, is there a way of reading a manually entered word as a whole word rather than letter by letter?.
Kind regards, Paul.
On 29 May 2018, at 23:19, FlickType <@FlickType> wrote:

- Don't add a space when deleting manually entered characters.







Re: Bild 75

Chuck Dean
 

Hi Kosta,
I don't think there is a gesture for the app switcher, I think this is an iOS fluke when to close to the left side of the screen.
I had similar problems when trying to use 3D touch to enter a capital Q.


Chuck

On May 29, 2018, at 5:01 PM, FlickType <@FlickType> wrote:

What is the app switcher gesture that is similar to the new line gesture? I’m not aware of one...

Kosta

On May 29, 2018, at 16:58, Chanelle Allen <chanellem.allen@...> wrote:

Hello,
I can confirm that FlickType no longer inserts a space after deleting manually typed characters. I knew that FlickType did not announce new lines but I didn't realize that one swipe left would delete multiple line breaks until now. As of a few minutes ago, I have performed the new line gesture and ended up in the app Switcher. Maybe my finger was further to the left on the screen than usual, so hopefully, this quirk is not encountered by anyone else.

I am just glad that one of the spacing problems is resolved.😀 now, let's see how that emoji came out with FlickType and VoiceOver. Chanelle

On May 29, 2018, at 17:45, Paul Sutton <sutty_p@...> wrote:

Hi,
Just reporting that this build has fixed the inserting a space during manual typing error. Thank you.
I also wanted too add that VoiceOver does not amounts when you are deleting a new line. Also, when inserting multiple new lines, a single swipe left will delete all of the new lines that you have entered rather than one at a time..
The last thing that I would like to ask is when swiping left and right with two fingers to read word by word, is there a way of reading a manually entered word as a whole word rather than letter by letter?.
Kind regards, Paul.
On 29 May 2018, at 23:19, FlickType <@FlickType> wrote:

- Don't add a space when deleting manually entered characters.






Re: Bild 75

 

What is the app switcher gesture that is similar to the new line gesture? I’m not aware of one...

Kosta

On May 29, 2018, at 16:58, Chanelle Allen <chanellem.allen@...> wrote:

Hello,
I can confirm that FlickType no longer inserts a space after deleting manually typed characters. I knew that FlickType did not announce new lines but I didn't realize that one swipe left would delete multiple line breaks until now. As of a few minutes ago, I have performed the new line gesture and ended up in the app Switcher. Maybe my finger was further to the left on the screen than usual, so hopefully, this quirk is not encountered by anyone else.

I am just glad that one of the spacing problems is resolved.😀 now, let's see how that emoji came out with FlickType and VoiceOver. Chanelle

On May 29, 2018, at 17:45, Paul Sutton <sutty_p@...> wrote:

Hi,
Just reporting that this build has fixed the inserting a space during manual typing error. Thank you.
I also wanted too add that VoiceOver does not amounts when you are deleting a new line. Also, when inserting multiple new lines, a single swipe left will delete all of the new lines that you have entered rather than one at a time..
The last thing that I would like to ask is when swiping left and right with two fingers to read word by word, is there a way of reading a manually entered word as a whole word rather than letter by letter?.
Kind regards, Paul.
On 29 May 2018, at 23:19, FlickType <@FlickType> wrote:

- Don't add a space when deleting manually entered characters.





Re: Bild 75

Chanelle Allen
 

Hello,
I can confirm that FlickType no longer inserts a space after deleting manually typed characters. I knew that FlickType did not announce new lines but I didn't realize that one swipe left would delete multiple line breaks until now. As of a few minutes ago, I have performed the new line gesture and ended up in the app Switcher. Maybe my finger was further to the left on the screen than usual, so hopefully, this quirk is not encountered by anyone else.

I am just glad that one of the spacing problems is resolved.😀 now, let's see how that emoji came out with FlickType and VoiceOver. Chanelle

On May 29, 2018, at 17:45, Paul Sutton <sutty_p@...> wrote:

Hi,
Just reporting that this build has fixed the inserting a space during manual typing error. Thank you.
I also wanted too add that VoiceOver does not amounts when you are deleting a new line. Also, when inserting multiple new lines, a single swipe left will delete all of the new lines that you have entered rather than one at a time..
The last thing that I would like to ask is when swiping left and right with two fingers to read word by word, is there a way of reading a manually entered word as a whole word rather than letter by letter?.
Kind regards, Paul.
On 29 May 2018, at 23:19, FlickType <@FlickType> wrote:

- Don't add a space when deleting manually entered characters.




Re: Bild 75

Paul Sutton
 

Hi,
Just reporting that this build has fixed the inserting a space during manual typing error. Thank you.
I also wanted too add that VoiceOver does not amounts when you are deleting a new line. Also, when inserting multiple new lines, a single swipe left will delete all of the new lines that you have entered rather than one at a time..
The last thing that I would like to ask is when swiping left and right with two fingers to read word by word, is there a way of reading a manually entered word as a whole word rather than letter by letter?.
Kind regards, Paul.

On 29 May 2018, at 23:19, FlickType <@FlickType> wrote:

- Don't add a space when deleting manually entered characters.



Bild 75

 

- Don't add a space when deleting manually entered characters.


Re: Build 74

Sharon Kim
 

hello all,
so here's a weird bug I noticed, that is a bit annoying.
When you enter a word manually, and if you hit the wrong letter by
accident, and flick left to delete it, that'll actually delete the
letter, but also add a space. so what you end up having to do is,
delete the rest of the word, and start all over again. And if you
click the wrong letter by accident, you're having to do it all over
again.
It's making typing words manually a bit challenging.

On 5/29/18, Ed Worrell <ed.worrell@...> wrote:

Hey Kosta,

In the previous email I added text to finish a thought.

I typed in the message field as for usual. Dismissed the keyboard to find
the send button. I then realized that I had some more feedback to give you
and doubled tapped on the message field again in the email compose screen.
The FlickType cursor was placed at the begining of the email. I had to
switch back to the iOS keyboard to move to the proper place in the message
text field, as FlickType would not move past the first line. I had to
utilize the VO rotor to move to the proper point in the email. I then could
switch back to FlickType and everything worked as expected.

I hope this helps,

Ed Worrell
On May 29, 2018, at 12:25 AM, FlickType <@FlickType> wrote:

Hi Ed,

Whenever you go back to edit existing text, FlickType doesn’t know the
entire contents of the text because iOS only supplies us with roughly a
sentence or so from where the cursor happens to be. So if you go back to
the iOS keyboard and then switch back to FlickType, you will likely have
only one or two sentences available to edit and read back, even though the
entire text should be in the text field. This may also happen if you
remain on FlickType but switch apps. Unfortunately there's even a chance
that there is no workaround for this, apart from something that might be
too fragile and introduce other bugs elsewhere. We'll have to investigate
more on this.

But when dismissing or switching, the cursor should be where you left it
on FlickType. Do you have a small example that can reproduce the behavior
you describe?

- Kosta





Re: Build 72

Chuck Dean
 

Hi Chanell,
I use the😎 emoji all the time, but I live in the valley of the sun.

Btw there is also a😀 emoji in the list, just continue to flick up.


Chuck

On May 29, 2018, at 10:34 AM, Chanelle Allen <chanellem.allen@...> wrote:


Hi Alan,
Thank you for pointing out the strange text at the end of my sentence. I think that I was trying to write the smiling face emoji, but I switched to the iOS keyboard to do so since I really don't know in what contexts to use the smiling face with sunglasses emoji. Yesterday, I also noticed the strange text you observed, but I thought that it had to do with Microsoft Outlook on my computer and the screen reader I was using.


On May 29, 2018, at 10:30, Alan Lemly <@walemly> wrote:

Kosta and Chanelle,

I wanted to point out something I noticed in Chanelle's post below that I've also picked up in posts from others. The paragraph that ends with I learn something new every day ends with a period but is then followed by a space and two question marks. I don't know what behavior is causing this but as I've said, I've seen it on other posts and if I'm remembering correctly, I believe they were from Chuck Dean. This seems like a bug or if not, something procedural that we users need to be aware of and adjust for if possible.

Alan Lemly

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf Of Chanelle Allen
Sent: Tuesday, May 29, 2018 7:31 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 72

Hi Kosta,
Thank you for replying to me. I tried dismissing the FlickType keyboard in Messages, and sure enough, send is at the bottom right. I would not have even thought of looking for it their because it's always above the letter p when typing on the iOS keyboard. The "Go," "Search," and "Return," buttons are always at the bottom right though. I learn something new every day. ??
I am also glad to hear that you will be able to add buttons to the FlickType keyboard without making things too complicated for new users and everyone in general. The reason why I made my requests also had to do with our list discussion yesterday about manual typing and spacing. You have always resolved FlickType difficulties in the past, and I am confident that everything will work out just great.
Chanelle

On May 28, 2018, at 22:58, FlickType <@FlickType> wrote:

Hi Chanelle, and thank you for the long and thoughtful post.

We definitely want to make finer text editing easier with FlickType, so you can expect features such as moving the cursor by character as well as deleting individual characters to be available soon. We will also work on improving the current automatic spacing logic so that you'll have fewer errors that need correcting to begin with. We are simply starting with the basics, and proceeding slowly but surely with the rest of the expected functionality.

On the issue of the bottom row getting crammed as we add more keys, the most likely option is to simply add back a fourth row and make the keyboard feel almost identical to the iOS one when touch typing, but without affecting the Flick Typing experience at all, ie you wouldn't have to worry about accidentally hitting any control keys. This would also significantly ease new users into the system, where each control key could also offer a hint of how to invoke it using a gesture instead. Easing new users into the system will be a big focus area for us in the near future.

In your email you mentioned, quote: "When dismissing FlickType, finding and tapping the "Send" button is impossible without first double tapping the text edit field in the Messages app". As far as I can tell, you can access the "Send" button when the keyboard is dismissed: it's located at the very bottom right corner. Please let me know if this doesn't work for you for some reason.

Thank you,
Kosta








Re: Build 72

Chanelle Allen
 

Hi Alan,
Thank you for pointing out the strange text at the end of my sentence. I think that I was trying to write the smiling face emoji, but I switched to the iOS keyboard to do so since I really don't know in what contexts to use the smiling face with sunglasses emoji. Yesterday, I also noticed the strange text you observed, but I thought that it had to do with Microsoft Outlook on my computer and the screen reader I was using.

On May 29, 2018, at 10:30, Alan Lemly <@walemly> wrote:

Kosta and Chanelle,

I wanted to point out something I noticed in Chanelle's post below that I've also picked up in posts from others. The paragraph that ends with I learn something new every day ends with a period but is then followed by a space and two question marks. I don't know what behavior is causing this but as I've said, I've seen it on other posts and if I'm remembering correctly, I believe they were from Chuck Dean. This seems like a bug or if not, something procedural that we users need to be aware of and adjust for if possible.

Alan Lemly

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf Of Chanelle Allen
Sent: Tuesday, May 29, 2018 7:31 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 72

Hi Kosta,
Thank you for replying to me. I tried dismissing the FlickType keyboard in Messages, and sure enough, send is at the bottom right. I would not have even thought of looking for it their because it's always above the letter p when typing on the iOS keyboard. The "Go," "Search," and "Return," buttons are always at the bottom right though. I learn something new every day. ??
I am also glad to hear that you will be able to add buttons to the FlickType keyboard without making things too complicated for new users and everyone in general. The reason why I made my requests also had to do with our list discussion yesterday about manual typing and spacing. You have always resolved FlickType difficulties in the past, and I am confident that everything will work out just great.
Chanelle

On May 28, 2018, at 22:58, FlickType <@FlickType> wrote:

Hi Chanelle, and thank you for the long and thoughtful post.

We definitely want to make finer text editing easier with FlickType, so you can expect features such as moving the cursor by character as well as deleting individual characters to be available soon. We will also work on improving the current automatic spacing logic so that you'll have fewer errors that need correcting to begin with. We are simply starting with the basics, and proceeding slowly but surely with the rest of the expected functionality.

On the issue of the bottom row getting crammed as we add more keys, the most likely option is to simply add back a fourth row and make the keyboard feel almost identical to the iOS one when touch typing, but without affecting the Flick Typing experience at all, ie you wouldn't have to worry about accidentally hitting any control keys. This would also significantly ease new users into the system, where each control key could also offer a hint of how to invoke it using a gesture instead. Easing new users into the system will be a big focus area for us in the near future.

In your email you mentioned, quote: "When dismissing FlickType, finding and tapping the "Send" button is impossible without first double tapping the text edit field in the Messages app". As far as I can tell, you can access the "Send" button when the keyboard is dismissed: it's located at the very bottom right corner. Please let me know if this doesn't work for you for some reason.

Thank you,
Kosta







Re: Build 74

Ed Worrell
 

Hey Kosta,

In the previous email I added text to finish a thought.

I typed in the message field as for usual. Dismissed the keyboard to find the send button. I then realized that I had some more feedback to give you and doubled tapped on the message field again in the email compose screen. The FlickType cursor was placed at the begining of the email. I had to switch back to the iOS keyboard to move to the proper place in the message text field, as FlickType would not move past the first line. I had to utilize the VO rotor to move to the proper point in the email. I then could switch back to FlickType and everything worked as expected.

I hope this helps,

Ed Worrell

On May 29, 2018, at 12:25 AM, FlickType <@FlickType> wrote:

Hi Ed,

Whenever you go back to edit existing text, FlickType doesn’t know the entire contents of the text because iOS only supplies us with roughly a sentence or so from where the cursor happens to be. So if you go back to the iOS keyboard and then switch back to FlickType, you will likely have only one or two sentences available to edit and read back, even though the entire text should be in the text field. This may also happen if you remain on FlickType but switch apps. Unfortunately there's even a chance that there is no workaround for this, apart from something that might be too fragile and introduce other bugs elsewhere. We'll have to investigate more on this.

But when dismissing or switching, the cursor should be where you left it on FlickType. Do you have a small example that can reproduce the behavior you describe?

- Kosta



Re: Build 72

 

Kosta and Chanelle,

I wanted to point out something I noticed in Chanelle's post below that I've also picked up in posts from others. The paragraph that ends with I learn something new every day ends with a period but is then followed by a space and two question marks. I don't know what behavior is causing this but as I've said, I've seen it on other posts and if I'm remembering correctly, I believe they were from Chuck Dean. This seems like a bug or if not, something procedural that we users need to be aware of and adjust for if possible.

Alan Lemly

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf Of Chanelle Allen
Sent: Tuesday, May 29, 2018 7:31 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 72

Hi Kosta,
Thank you for replying to me. I tried dismissing the FlickType keyboard in Messages, and sure enough, send is at the bottom right. I would not have even thought of looking for it their because it's always above the letter p when typing on the iOS keyboard. The "Go," "Search," and "Return," buttons are always at the bottom right though. I learn something new every day. ??
I am also glad to hear that you will be able to add buttons to the FlickType keyboard without making things too complicated for new users and everyone in general. The reason why I made my requests also had to do with our list discussion yesterday about manual typing and spacing. You have always resolved FlickType difficulties in the past, and I am confident that everything will work out just great.
Chanelle

On May 28, 2018, at 22:58, FlickType <@FlickType> wrote:

Hi Chanelle, and thank you for the long and thoughtful post.

We definitely want to make finer text editing easier with FlickType, so you can expect features such as moving the cursor by character as well as deleting individual characters to be available soon. We will also work on improving the current automatic spacing logic so that you'll have fewer errors that need correcting to begin with. We are simply starting with the basics, and proceeding slowly but surely with the rest of the expected functionality.

On the issue of the bottom row getting crammed as we add more keys, the most likely option is to simply add back a fourth row and make the keyboard feel almost identical to the iOS one when touch typing, but without affecting the Flick Typing experience at all, ie you wouldn't have to worry about accidentally hitting any control keys. This would also significantly ease new users into the system, where each control key could also offer a hint of how to invoke it using a gesture instead. Easing new users into the system will be a big focus area for us in the near future.

In your email you mentioned, quote: "When dismissing FlickType, finding and tapping the "Send" button is impossible without first double tapping the text edit field in the Messages app". As far as I can tell, you can access the "Send" button when the keyboard is dismissed: it's located at the very bottom right corner. Please let me know if this doesn't work for you for some reason.

Thank you,
Kosta



Re: Build 72

Chanelle Allen
 

Hi Kosta,
Thank you for replying to me. I tried dismissing the FlickType keyboard in Messages, and sure enough, send is at the bottom right. I would not have even thought of looking for it their because it's always above the letter p when typing on the iOS keyboard. The "Go," "Search," and "Return," buttons are always at the bottom right though. I learn something new every day. ☺️
I am also glad to hear that you will be able to add buttons to the FlickType keyboard without making things too complicated for new users and everyone in general. The reason why I made my requests also had to do with our list discussion yesterday about manual typing and spacing. You have always resolved FlickType difficulties in the past, and I am confident that everything will work out just great.
Chanelle

On May 28, 2018, at 22:58, FlickType <@FlickType> wrote:

Hi Chanelle, and thank you for the long and thoughtful post.

We definitely want to make finer text editing easier with FlickType, so you can expect features such as moving the cursor by character as well as deleting individual characters to be available soon. We will also work on improving the current automatic spacing logic so that you'll have fewer errors that need correcting to begin with. We are simply starting with the basics, and proceeding slowly but surely with the rest of the expected functionality.

On the issue of the bottom row getting crammed as we add more keys, the most likely option is to simply add back a fourth row and make the keyboard feel almost identical to the iOS one when touch typing, but without affecting the Flick Typing experience at all, ie you wouldn't have to worry about accidentally hitting any control keys. This would also significantly ease new users into the system, where each control key could also offer a hint of how to invoke it using a gesture instead. Easing new users into the system will be a big focus area for us in the near future.

In your email you mentioned, quote: "When dismissing FlickType, finding and tapping the "Send" button is impossible without first double tapping the text edit field in the Messages app". As far as I can tell, you can access the "Send" button when the keyboard is dismissed: it's located at the very bottom right corner. Please let me know if this doesn't work for you for some reason.

Thank you,
Kosta



Re: Build 74

Nozi <noziphokhanda@...>
 

Thanks so much for all your hard work. This build is working well and I've had no text loss this time. I'm wondering if you are planning to introduce the number pad in the custom keyboard?


Re: Build 74

 

Hi Ed,

Whenever you go back to edit existing text, FlickType doesn’t know the entire contents of the text because iOS only supplies us with roughly a sentence or so from where the cursor happens to be. So if you go back to the iOS keyboard and then switch back to FlickType, you will likely have only one or two sentences available to edit and read back, even though the entire text should be in the text field. This may also happen if you remain on FlickType but switch apps. Unfortunately there's even a chance that there is no workaround for this, apart from something that might be too fragile and introduce other bugs elsewhere. We'll have to investigate more on this.

But when dismissing or switching, the cursor should be where you left it on FlickType. Do you have a small example that can reproduce the behavior you describe?

- Kosta


Re: Build 74

Ed Worrell
 

Hello Kosta,

I have been playing with the new release and it is still acting weird with text. I however have not noticed the text being deleted or vanishing. I however an still having issues with text after dismissing or switching to the iOS keyboard. The FlickType cursor is only seeing the last sentence typed after I switch to the iOS keyboard. When I dismiss the keyboard via the dismiss key the FlickType cursor seems to jump to the begining of the text field. I then an not able to move the FlickType cursor past the few first words in the text field.

Ed

On May 28, 2018, at 9:33 PM, FlickType <@FlickType> wrote:

Reduced memory consumption in order to prevent iOS from terminating and restarting the keyboard. When that happened, typed text would be lost, so hopefully this doesn't happen anymore.



Re: Build 72

 

Hi Chanelle, and thank you for the long and thoughtful post.

We definitely want to make finer text editing easier with FlickType, so you can expect features such as moving the cursor by character as well as deleting individual characters to be available soon. We will also work on improving the current automatic spacing logic so that you'll have fewer errors that need correcting to begin with. We are simply starting with the basics, and proceeding slowly but surely with the rest of the expected functionality.

On the issue of the bottom row getting crammed as we add more keys, the most likely option is to simply add back a fourth row and make the keyboard feel almost identical to the iOS one when touch typing, but without affecting the Flick Typing experience at all, ie you wouldn't have to worry about accidentally hitting any control keys. This would also significantly ease new users into the system, where each control key could also offer a hint of how to invoke it using a gesture instead. Easing new users into the system will be a big focus area for us in the near future.

In your email you mentioned, quote: "When dismissing FlickType, finding and tapping the "Send" button is impossible without first double tapping the text edit field in the Messages app". As far as I can tell, you can access the "Send" button when the keyboard is dismissed: it's located at the very bottom right corner. Please let me know if this doesn't work for you for some reason.

Thank you,
Kosta


Build 74

 

Reduced memory consumption in order to prevent iOS from terminating and restarting the keyboard. When that happened, typed text would be lost, so hopefully this doesn't happen anymore.


Re: Text population question

 

Thank you Ed, and you are correct. If FlickType populates the text field as you type, then no text would ever be lost. The devil is in the details, though.

Even if you turn all VoiceOver typing feedback off, VoiceOver will still incorrectly play some sound effects like end of document after typing or changing any word. Additionally, it will also still try to announce some things, like when moving the cursor. I will still need to figure out some workarounds for those, and it's not going to be easy to make this robust, but it's probably doable.

Additionally, what I believe is currently happening is that the FlickType custom keyboard is simply terminated by iOS due to momentarily exceeding the tiny amount of memory custom keyboards are allowed to use, compared to regular apps. I believe something in the last few releases has caused memory consumption to increase ever so slightly, but enough to trigger the iOS termination policy. If that's the case, the first order of things will be to bring down the memory usage within acceptable limits.

Of course making FlickType populate the text field as you type is more or less a requirement for the half-screen option to work, so we'll definitely do more work in that direction, including making the return key trigger the app action whenever possible.

Kosta


Re: Build 73, text still vanishing.

Chuck Dean
 

No, the last thing I did before the text vanished was type the letter s.
Btw once before I noticed that my text vanished when I typed the word "as".. I don't know if there is a connection.

I just noticed another bug, although I doubt it will come up often. It is difficult to cap the letter Q using 3D touch. It wants to open the app switcher.


Chuck

On May 28, 2018, at 4:47 PM, FlickType <@FlickType> wrote:

Thank you Chuck.

Do you happen to remember if the last thing you did right before the text vanished was browse or enter emojis?

Kosta



Re: Build 73, text still vanishing.

 

Thank you Chuck.

Do you happen to remember if the last thing you did right before the text vanished was browse or enter emojis?

Kosta