Date   

Build 44

 

Please report all your feedback by replying to this topic.

In this release:
- An iOS bug prevented us from correctly addressing the unintended invocation of the notification center. So we changed the flick up and hold menu gesture to a flick down and hold instead. Again, please let us know if this new gesture works well for you, or if you encounter any issues.
- Fixed sometimes not being able to toggle capitalization of a letter.

In the previous release:
- Flick down and hold anywhere to invoke the menu. This replaces the tap & hold gesture above the keyboard. Please let us know if this new gesture works well for you, or if you encounter any issues.
- Fixed iPhone X issue where the home and app switcher gestures were being suppressed and had to be performed twice to work.
- Fixed occasional lost feedback on tap & hold mode. Please help us confirm that the issue is now resolved.
- Added haptic feedback when invoking the menu.
- Lots of under-the-hood changes relating to touch and flick gesture recognition. Please let us know if you encounter any issues, and if they are new with this release. If you need to compare and confirm, you can always revert to a previous build from TestFlight.

Thank you for testing FlickType!

Kosta & Ashley


Re: Build 42.

Chuck Dean
 

That is force of habit. I always use punctuation... Even when texting. Which the younger generation thinks is stupid.

Chuck

On Apr 20, 2018, at 10:09 AM, FlickType <@FlickType> wrote:

I just noticed that you added a period at the end of the subject, this might be why the forum started a new topic.



Re: Build 42

Chuck Dean
 

Hello Santiago,
When I do the flick up and hold from the bottom gesture, I start in the middle of the screen flick up about an inch and then hold. It does not bring up the control panel if you stay in the middle of the screen, and works every time.
I have also reverted back to the two finger swipe up, because are usually used to finger double tap to bring up the export text panel so it just seems natural to me.

Chuck

On Apr 20, 2018, at 3:49 AM, Santiago <santiago.blue.hernandez@...> wrote:

The latest Alpha Version 42 seems to be working for me as well, although sometimes when I flick up and hold, my iPhone launches the control center, so I reverted back to using the two finger flick up gesture to open the menu.

Santiago
On Apr 20, 2018, at 2:43 AM, Maria and Joe Chapman <bubbygirl1972@...> wrote:

HI. the flick up is working for me no matter where I do it from, but I also am unable to get a letter to be capital.

Everything else is working very well.

Maria

On 20 Apr 2018, at 6:19 pm, Macster <@Macster> wrote:

Hi guys,

I have been testing build 42 and have noticed two problems...

The first is if you use the new flick up and hold gesture and begin flicking too close to the bottom of the screen, it somehow manages to bring up a combination of the menu and the control menu. Trying to use the home button doesn't seem to work to disregard the control center, even a triple click which should, in my set up, turn VoiceOver off doesn't work. Touching the top right of the screen after a few seconds was the only way I could get out of this culdesac. I've no idea if this would be possible, but in the area above the punctuation and numbers etc where we used to press and hold to bring up the menu, could the flick up and hold gesture be used only in that area to avoid the double activation of accidentally getting both if starting the initial flick too close to the home button? It works no problem if so.

And the other issue I've noticed is I can't capitalize a letter using the single flick up after manually typing now. For example, I was typing to my sister regarding my nephew mark. If I press the letter m alone, then flick up and I'd expect to hear capital m, but there is no announcement. I then type the rest of his name and flick right but only ark is entered. Its as if the flick up disregards the initial press of the letter m. Could this be because the swipe up is ”expecting” the hold of the new gesture for the menu? This can be reproduced with any word you type with a capital at the start, and you'll get a word one letter shorter than the desired word. I hope this is an easy fix?

Other than this, the actual typing is extremely slick and the rate at which you guys are sending out the updates is incredible and has not gone unnoticed.

Many thanks,

Alan






Re: Build 42.

 

I just noticed that you added a period at the end of the subject, this might be why the forum started a new topic.


Re: Build 42.

 

Thank you Chuck.

I will address the control center issue in the next release. The flick down to capitalize a letter has always co-existed with the flick up to do the same. For some unexpected reason the flick up to capitalize broke with this release and I will address that, thanks for the great feedback!

Noted on the deletion of a partial word, that definitely needs improvement.

By the way, your feedback was posted as a separate topic here on our forum. Did you reply to the email I sent out with the same subject? If you always reply to the release emails, your feedback will be included in the topic where everyone else is posting too. Everyone in the alpha group should get all messages anyway, even in topics they don't follow, but it's nicer if all feedback for a particular build is grouped under the same topic.

Thank you again,
- Kosta


Re: Build 42

Santiago
 

The latest Alpha Version 42 seems to be working for me as well, although sometimes when I flick up and hold, my iPhone launches the control center, so I reverted back to using the two finger flick up gesture to open the menu.

Santiago

On Apr 20, 2018, at 2:43 AM, Maria and Joe Chapman <bubbygirl1972@...> wrote:

HI. the flick up is working for me no matter where I do it from, but I also am unable to get a letter to be capital.

Everything else is working very well.

Maria

On 20 Apr 2018, at 6:19 pm, Macster <@Macster> wrote:

Hi guys,

I have been testing build 42 and have noticed two problems...

The first is if you use the new flick up and hold gesture and begin flicking too close to the bottom of the screen, it somehow manages to bring up a combination of the menu and the control menu. Trying to use the home button doesn't seem to work to disregard the control center, even a triple click which should, in my set up, turn VoiceOver off doesn't work. Touching the top right of the screen after a few seconds was the only way I could get out of this culdesac. I've no idea if this would be possible, but in the area above the punctuation and numbers etc where we used to press and hold to bring up the menu, could the flick up and hold gesture be used only in that area to avoid the double activation of accidentally getting both if starting the initial flick too close to the home button? It works no problem if so.

And the other issue I've noticed is I can't capitalize a letter using the single flick up after manually typing now. For example, I was typing to my sister regarding my nephew mark. If I press the letter m alone, then flick up and I'd expect to hear capital m, but there is no announcement. I then type the rest of his name and flick right but only ark is entered. Its as if the flick up disregards the initial press of the letter m. Could this be because the swipe up is ”expecting” the hold of the new gesture for the menu? This can be reproduced with any word you type with a capital at the start, and you'll get a word one letter shorter than the desired word. I hope this is an easy fix?

Other than this, the actual typing is extremely slick and the rate at which you guys are sending out the updates is incredible and has not gone unnoticed.

Many thanks,

Alan





Build 42.

Chuck Dean
 

Build 42.
This build feels much like the last one.
I have tried the flick up and hold gesture, it works ok as long as I stay off the bottom. I prefer the two finger flick up, so I'll stick with that.
The flick down to cap a letter is going to take some getting used to. I still have a lot of muscle memory from using Fleksy, so I automatically go to the flick up.
There is still no indication when I delete a partial word. I'll just have to assume it has been deleted.
Otherwise, a great app!


Chuck


Re: Build 42

 

Hi List,

It was late when I first replied to the build 42 thread and mentioned the problem of adding words like mp3 to the dictionary. I did not even notice that a new gesture of single finger swipe up and hold to access the menu had been introduced. I've now tested that on my iPhone 7 running iOS 11.3 and can confirm that sometimes the single finger swipe up and hold will launch the control center. This seems to happen the closer to the bottom of the screen my finger is when I swipe up. For example, if I rest my finger on the home button and then single finger swipe up the screen and hold, the control center comes up every time. It does not seem to happen when I swipe up from a starting position about a half inch or higher above the home button. The menu pops up correctly each of those times. I will add that if the control center does pop up, the scrub gesture closes it and returns me to the FlickType menu every time.

Also, I'm noticing that when I access the menu using the new single finger swipe up and hold gesture, what I've typed is read twice by Voiceover but is only read once when accessing the menu using the original 2 finger swipe up gesture.

Alan Lemly

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf Of Chanelle Allen
Sent: Friday, April 20, 2018 8:31 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 42

Hello,
This FlickType build is great! So far, the new flick up and hold menu gesture works well. I will keep playing with it though. I can reproduce the problem of attempting to add MP3 to the dictionary. Flicking up results in the three increasing to four, and flicking down goes to two. However, it is not very often that I would be using MP3 in my writing.
I think that the new gesture to capitalize a letter is a one finger flick down while a one finger flick up is still used to add a word to the user dictionary.
Chanelle

On Apr 20, 2018, at 04:43, Maria and Joe Chapman <bubbygirl1972@...> wrote:

HI. the flick up is working for me no matter where I do it from, but I also am unable to get a letter to be capital.

Everything else is working very well.

Maria

On 20 Apr 2018, at 6:19 pm, Macster <@Macster> wrote:

Hi guys,

I have been testing build 42 and have noticed two problems...

The first is if you use the new flick up and hold gesture and begin flicking too close to the bottom of the screen, it somehow manages to bring up a combination of the menu and the control menu. Trying to use the home button doesn't seem to work to disregard the control center, even a triple click which should, in my set up, turn VoiceOver off doesn't work. Touching the top right of the screen after a few seconds was the only way I could get out of this culdesac. I've no idea if this would be possible, but in the area above the punctuation and numbers etc where we used to press and hold to bring up the menu, could the flick up and hold gesture be used only in that area to avoid the double activation of accidentally getting both if starting the initial flick too close to the home button? It works no problem if so.

And the other issue I've noticed is I can't capitalize a letter using the single flick up after manually typing now. For example, I was typing to my sister regarding my nephew mark. If I press the letter m alone, then flick up and I'd expect to hear capital m, but there is no announcement. I then type the rest of his name and flick right but only ark is entered. Its as if the flick up disregards the initial press of the letter m. Could this be because the swipe up is expecting the hold of the new gesture for the menu? This can be reproduced with any word you type with a capital at the start, and you'll get a word one letter shorter than the desired word. I hope this is an easy fix?

Other than this, the actual typing is extremely slick and the rate at which you guys are sending out the updates is incredible and has not gone unnoticed.

Many thanks,

Alan





Re: Build 42

Alex Hiironen
 

Hey all,

So far this release is solid for me. The new flick up and hold gesture is working great without accidentally triggering anything odd. I'm in landscape left orientation, so that negates any control center activation, thankfully.

Best of all, holding on letters is fixed!

Thanks for all the amazing work!

Alex

On Apr 20, 2018, at 2:58 AM, FlickType <@FlickType> wrote:

Please report all your feedback by replying to this topic. Thank you for testing FlickType!

In this release:
- Flick up and hold anywhere to invoke the menu. This replaces the tap & hold gesture above the keyboard. Please let us know if this new gesture works well for you, or if you encounter any issues.
- Fixed iPhone X issue where the home and app switcher gestures were being suppressed and had to be performed twice to work.
- Fixed occasional lost feedback on tap & hold mode. Please confirm if the issue is now resolved.
- Added haptic feedback when invoking the menu.
- Lots of under-the-hood changes relating to touch and flick gesture recognition. Please let us know if you encounter any issues, and if they are new with this release. If you need to compare and confirm, you can always revert to a previous build from TestFlight.

Thank you for testing FlickType!

Kosta & Ashley



Re: Build 42

Chuck Dean
 

I have found that if the slide and hold gesture brings of the control panel, if you tap on the control panel, and then press the home button. The control panel disappears, and the Fliktype menu is underneath. This is working very well on my iPhone ate. I hope this works for everyone else.

Chuck

On Apr 20, 2018, at 7:31 AM, Paul Sutton <sutty_p@...> wrote:

Hi, after testing build 42, I just wanted to confirm what other's have been saying. The slide and hold gesture does indeed bring up the control Centre which I would like to add is incredibly difficult to dismiss. cheers, Paul



Re: Build 42

Paul Sutton
 

Hi, after testing build 42, I just wanted to confirm what other's have been saying. The slide and hold gesture does indeed bring up the control Centre which I would like to add is incredibly difficult to dismiss. cheers, Paul


Re: Build 42

Macster
 

Well spotted! I didn't realize the single finger swipe down was to capitalize a letter now, please disregard my previous post about this costa and Ashley.


Re: Build 42

Chanelle Allen
 

Hello,
This FlickType build is great! So far, the new flick up and hold menu gesture works well. I will keep playing with it though. I can reproduce the problem of attempting to add MP3 to the dictionary. Flicking up results in the three increasing to four, and flicking down goes to two. However, it is not very often that I would be using MP3 in my writing.
I think that the new gesture to capitalize a letter is a one finger flick down while a one finger flick up is still used to add a word to the user dictionary.
Chanelle

On Apr 20, 2018, at 04:43, Maria and Joe Chapman <bubbygirl1972@...> wrote:

HI. the flick up is working for me no matter where I do it from, but I also am unable to get a letter to be capital.

Everything else is working very well.

Maria

On 20 Apr 2018, at 6:19 pm, Macster <@Macster> wrote:

Hi guys,

I have been testing build 42 and have noticed two problems...

The first is if you use the new flick up and hold gesture and begin flicking too close to the bottom of the screen, it somehow manages to bring up a combination of the menu and the control menu. Trying to use the home button doesn't seem to work to disregard the control center, even a triple click which should, in my set up, turn VoiceOver off doesn't work. Touching the top right of the screen after a few seconds was the only way I could get out of this culdesac. I've no idea if this would be possible, but in the area above the punctuation and numbers etc where we used to press and hold to bring up the menu, could the flick up and hold gesture be used only in that area to avoid the double activation of accidentally getting both if starting the initial flick too close to the home button? It works no problem if so.

And the other issue I've noticed is I can't capitalize a letter using the single flick up after manually typing now. For example, I was typing to my sister regarding my nephew mark. If I press the letter m alone, then flick up and I'd expect to hear capital m, but there is no announcement. I then type the rest of his name and flick right but only ark is entered. Its as if the flick up disregards the initial press of the letter m. Could this be because the swipe up is ”expecting” the hold of the new gesture for the menu? This can be reproduced with any word you type with a capital at the start, and you'll get a word one letter shorter than the desired word. I hope this is an easy fix?

Other than this, the actual typing is extremely slick and the rate at which you guys are sending out the updates is incredible and has not gone unnoticed.

Many thanks,

Alan





Re: Build 42

MariaRosa Chapman
 

HI. the flick up is working for me no matter where I do it from, but I also am unable to get a letter to be capital.

Everything else is working very well.

Maria

On 20 Apr 2018, at 6:19 pm, Macster <@Macster> wrote:

Hi guys,

I have been testing build 42 and have noticed two problems...

The first is if you use the new flick up and hold gesture and begin flicking too close to the bottom of the screen, it somehow manages to bring up a combination of the menu and the control menu. Trying to use the home button doesn't seem to work to disregard the control center, even a triple click which should, in my set up, turn VoiceOver off doesn't work. Touching the top right of the screen after a few seconds was the only way I could get out of this culdesac. I've no idea if this would be possible, but in the area above the punctuation and numbers etc where we used to press and hold to bring up the menu, could the flick up and hold gesture be used only in that area to avoid the double activation of accidentally getting both if starting the initial flick too close to the home button? It works no problem if so.

And the other issue I've noticed is I can't capitalize a letter using the single flick up after manually typing now. For example, I was typing to my sister regarding my nephew mark. If I press the letter m alone, then flick up and I'd expect to hear capital m, but there is no announcement. I then type the rest of his name and flick right but only ark is entered. Its as if the flick up disregards the initial press of the letter m. Could this be because the swipe up is ”expecting” the hold of the new gesture for the menu? This can be reproduced with any word you type with a capital at the start, and you'll get a word one letter shorter than the desired word. I hope this is an easy fix?

Other than this, the actual typing is extremely slick and the rate at which you guys are sending out the updates is incredible and has not gone unnoticed.

Many thanks,

Alan



Re: Build 42

Macster
 

Hi guys,

I have been testing build 42 and have noticed two problems...

The first is if you use the new flick up and hold gesture and begin flicking too close to the bottom of the screen, it somehow manages to bring up a combination of the menu and the control menu. Trying to use the home button doesn't seem to work to disregard the control center, even a triple click which should, in my set up, turn VoiceOver off doesn't work. Touching the top right of the screen after a few seconds was the only way I could get out of this culdesac. I've no idea if this would be possible, but in the area above the punctuation and numbers etc where we used to press and hold to bring up the menu, could the flick up and hold gesture be used only in that area to avoid the double activation of accidentally getting both if starting the initial flick too close to the home button? It works no problem if so.

And the other issue I've noticed is I can't capitalize a letter using the single flick up after manually typing now. For example, I was typing to my sister regarding my nephew mark. If I press the letter m alone, then flick up and I'd expect to hear capital m, but there is no announcement. I then type the rest of his name and flick right but only ark is entered. Its as if the flick up disregards the initial press of the letter m. Could this be because the swipe up is ”expecting” the hold of the new gesture for the menu? This can be reproduced with any word you type with a capital at the start, and you'll get a word one letter shorter than the desired word. I hope this is an easy fix?

Other than this, the actual typing is extremely slick and the rate at which you guys are sending out the updates is incredible and has not gone unnoticed.

Many thanks,

Alan


Re: Build 42

 

Hi List,

I did some quick typing on this build and could find no issues. I do have one minor thing I noticed with build 41 that continues with build 42. Say you're manually entering a word like mp3 which ends in a number. After swiping right to get the word announced, attempting to flick up to get it added to the dictionary doesn't work. Instead, what happens is that the 3 is changed to a 4 and what was mp3 becomes mp4. This result is identical whether the 3 is entered with the separate number screen or with the topline popup number item. I'm sure this is something of which Kosta and Ashley are aware and it's very minor because how many words end in a number. Anyway, I just wanted to put it on the record.

Alan Lemly

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf Of FlickType
Sent: Friday, April 20, 2018 1:59 AM
To: alpha@flicktype.groups.io
Subject: [FlickType-alpha] Build 42

Please report all your feedback by replying to this topic. Thank you for testing FlickType!

In this release:
- Flick up and hold anywhere to invoke the menu. This replaces the tap & hold gesture above the keyboard. Please let us know if this new gesture works well for you, or if you encounter any issues.
- Fixed iPhone X issue where the home and app switcher gestures were being suppressed and had to be performed twice to work.
- Fixed occasional lost feedback on tap & hold mode. Please confirm if the issue is now resolved.
- Added haptic feedback when invoking the menu.
- Lots of under-the-hood changes relating to touch and flick gesture recognition. Please let us know if you encounter any issues, and if they are new with this release. If you need to compare and confirm, you can always revert to a previous build from TestFlight.

Thank you for testing FlickType!

Kosta & Ashley


Build 42

 

Please report all your feedback by replying to this topic. Thank you for testing FlickType!

In this release:
- Flick up and hold anywhere to invoke the menu. This replaces the tap & hold gesture above the keyboard. Please let us know if this new gesture works well for you, or if you encounter any issues.
- Fixed iPhone X issue where the home and app switcher gestures were being suppressed and had to be performed twice to work.
- Fixed occasional lost feedback on tap & hold mode. Please confirm if the issue is now resolved.
- Added haptic feedback when invoking the menu.
- Lots of under-the-hood changes relating to touch and flick gesture recognition. Please let us know if you encounter any issues, and if they are new with this release. If you need to compare and confirm, you can always revert to a previous build from TestFlight.

Thank you for testing FlickType!

Kosta & Ashley


Re: Version 41 I just noticed something.

Chuck Dean
 

Although, the contact list would be a nice addition to FlickType, I think the app is very close to release, and is unlikely to add more features.
I believe once the app is released the team will devote 100% of its time to the system wide keyboard, which is the ultimate goal.
I'm looking forward to the future of typing.

Chuck

On Apr 19, 2018, at 7:52 PM, Alan Lemly <@walemly> wrote:

Chuck,

Thanks for mentioning that previous Fleksy feature with the contacts. I know we're all aware of how we can do the same thing multiple ways with the iPhone so I'm very interested in learning as many alternatives and workarounds as possible.

Alan Lemly
On Apr 19, 2018, at 8:04 PM, Chuck Dean <cadean329@...> wrote:

Hi Ellen, thanks, I appreciate the information. I use the copy and clear option by closing the app all the time when I’m entering stuff into my daily journal. But as far as emails and messages I like to go directly to the app just seems easier.
I’m hoping that someday they’ll be able to do with FlickType the same thing that fleksy did years ago. They had a contacts list that you could populate with your most used contacts, all you had to do was type whatever you want, go to contact list, select the contact whether it be an email or a phone number, it would put the text into the appropriate app and then all I had to do was hit send.

Chuck


On Apr 19, 2018, at 4:07 PM, Alan Lemly <@walemly> wrote:

Chuck,

I can certainly appreciate not wanting to hunt for the edit menu and just wanted to make sure you were aware of the option. I find that when I place focus in the text box receiving the pasted text, that single finger double tapping and holding brings up a pop-up menu containing paste which can eliminate the need to rotor to edit.

And I'm a firm believer in different strokes for different folks. I just want the folks to be aware of all the different strokes.

Alan Lemly
-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf Of Chuck Dean
Sent: Wednesday, April 18, 2018 11:28 PM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Version 41 I just noticed something.

Hello Allen,
I have copied and clear turned on on my FlickType. I just like exploring directly to the messages and email apps, that way I don t have to hunt around for the edit menu to find paste etc. etc.

Chuck


On Apr 18, 2018, at 9:17 PM, Alan Lemly <@walemly> wrote:

Chuck,

Or you could turn on the copy and clear on exit setting and simply go to your message or email app to paste your FlickType input without having to go to the menu.

Alan Lemly

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On
Behalf Of Chuck Dean
Sent: Wednesday, April 18, 2018 10:42 PM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Version 41 I just noticed something.

Hi Ed,
Actually, I was thinking that the 3-D touch should be used to go directly to the export text panel. Bypassing the menu completely. Most of the time when I am using FlickType I am either sending a text message or eight email, and there s no reason to bring up the menu, if I could go directly to the export text panel, I can completely take out one step.

Chuck


On Apr 18, 2018, at 8:36 PM, Ed Worrell <ed.worrell@...> wrote:

I agree with the 3D touch for invoking the menu. I miss the tap and hold gesture at the top half of the scream.

E
Ed













Re: Version 41 I just noticed something.

 

Chuck,

Thanks for mentioning that previous Fleksy feature with the contacts. I know we're all aware of how we can do the same thing multiple ways with the iPhone so I'm very interested in learning as many alternatives and workarounds as possible.

Alan Lemly

On Apr 19, 2018, at 8:04 PM, Chuck Dean <cadean329@...> wrote:

Hi Ellen, thanks, I appreciate the information. I use the copy and clear option by closing the app all the time when I’m entering stuff into my daily journal. But as far as emails and messages I like to go directly to the app just seems easier.
I’m hoping that someday they’ll be able to do with FlickType the same thing that fleksy did years ago. They had a contacts list that you could populate with your most used contacts, all you had to do was type whatever you want, go to contact list, select the contact whether it be an email or a phone number, it would put the text into the appropriate app and then all I had to do was hit send.

Chuck


On Apr 19, 2018, at 4:07 PM, Alan Lemly <@walemly> wrote:

Chuck,

I can certainly appreciate not wanting to hunt for the edit menu and just wanted to make sure you were aware of the option. I find that when I place focus in the text box receiving the pasted text, that single finger double tapping and holding brings up a pop-up menu containing paste which can eliminate the need to rotor to edit.

And I'm a firm believer in different strokes for different folks. I just want the folks to be aware of all the different strokes.

Alan Lemly
-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf Of Chuck Dean
Sent: Wednesday, April 18, 2018 11:28 PM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Version 41 I just noticed something.

Hello Allen,
I have copied and clear turned on on my FlickType. I just like exploring directly to the messages and email apps, that way I don t have to hunt around for the edit menu to find paste etc. etc.

Chuck


On Apr 18, 2018, at 9:17 PM, Alan Lemly <@walemly> wrote:

Chuck,

Or you could turn on the copy and clear on exit setting and simply go to your message or email app to paste your FlickType input without having to go to the menu.

Alan Lemly

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On
Behalf Of Chuck Dean
Sent: Wednesday, April 18, 2018 10:42 PM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Version 41 I just noticed something.

Hi Ed,
Actually, I was thinking that the 3-D touch should be used to go directly to the export text panel. Bypassing the menu completely. Most of the time when I am using FlickType I am either sending a text message or eight email, and there s no reason to bring up the menu, if I could go directly to the export text panel, I can completely take out one step.

Chuck


On Apr 18, 2018, at 8:36 PM, Ed Worrell <ed.worrell@...> wrote:

I agree with the 3D touch for invoking the menu. I miss the tap and hold gesture at the top half of the scream.

E
Ed












Re: Version 41.

 

Hi Team,

Happy to hear things are mostly running smoothly for everyone! The manual text entry has improved, but not completely resolved - we're still working on it. As for the dictionary import issue, that is a known issue and something we're also trying to resolve, not sure if that will be a post-system-wide keyboard fix or a pre-system-wide keyboard fix as we're still trying to figure that out. For the partial word deletion issue, we will try to add a deletion sound for the standalone app for those that have the deletion sound setting on as we don't want it to announce "deleted garble" since what is typically typed really does not resemble a word before flicking right and it can be confusing if the system tries to announce that word.

To make sure everyone is on the same page, our largest goal is to launch the system-wide keyboard in alpha asap and in order to do that, we need to resolve the dealbreaker issues in the standalone app and keep moving with the system-wide extension. One of the obvious dealbreaker issues is the manual entry bug, and a couple other things and then we will push the standalone app to the app store and move forward. Many of the issues specific to the standalone app will become non-issues in the extension since Kosta is building the system-wide extension from scratch and none of the shortcomings exist there. We will also be able to apply some of the newly built components to the standalone app, so lots of these issues can be resolved in the future with the work we're doing on the system-wide extension.

Thanks a lot for all the great feedback!
Ashley