1. alpha@flicktype.groups.io
   Date   
Re: Build 42

Alan Lemly
 

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
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

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
Re: Build 42.

FlickType
 

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.

FlickType
 

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.

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.
Build 44

FlickType
 

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: Version 41 what is the haptic feedback?

FlickType
 

Chuck, all jokes aside, my gut feeling is that FlickType on the watch would be quite possible and even fun to use. We have no such plans currently, but it might be worthwhile trying it out at some point.

On the haptic feedback, my opinion is that it literally adds a new dimension to the feedback you get from the device, enriching the interactive experience. Everyone's different, but I personally quite like it. If you'd like, you can temporarily turn on the system option under "Settings", "Sounds & Haptics" and give FlickType a go - we'd love to hear what you think!

Warmly,
Kosta
Build 44

Chuck Dean
 

Build 44
Looks good. The swipe up for caps is working again.
The swipe down and hold brings up the menu and nothing else. Personally I like the two finger swipe up better.
The keyboard is stable and responsive.

I still do not hear anything when deleting partial words. I may be in the minority, but I would rather hear gibberish then nothing, at least I would have an idea where the cursor is. Otherwise, I like it!


Chuck
Re: Build 44

FlickType
 
Edited

Thanks Chuck, noted on the partial word deletion, this will be addressed soon. - Kosta
Re: Version 41 what is the haptic feedback?

Chuck Dean
 

Hi,
I tried the haptic feedback last night. You are right, it does give another dimension to typing. Personally, I like it better off. Somewhere in the back of my mind, I know the haptic feedback is eating up batteries. :)

Chuck

On Apr 20, 2018, at 8:35 PM, FlickType <@FlickType> wrote:

Chuck, all jokes aside, my gut feeling is that FlickType on the watch would be quite possible and even fun to use. We have no such plans currently, but it might be worthwhile trying it out at some point.

On the haptic feedback, my opinion is that it literally adds a new dimension to the feedback you get from the device, enriching the interactive experience. Everyone's different, but I personally quite like it. If you'd like, you can temporarily turn on the system option under "Settings", "Sounds & Haptics" and give FlickType a go - we'd love to hear what you think!

Warmly,
Kosta
Re: Build 44

Alan Lemly
 

I can confirm Chuck's findings too. The new gesture to invoke the menu works
as it should with no control center being invoked. I also prefer the old 2
finger swipe up to invoke the menu. I'm curious, why is another gesture to
invoke the menu needed? Are the plans to have two different ways to invoke
the menu and if not, which one will survive?

Thanks for all your hard work.

Alan Lemly

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of Chuck Dean
Sent: Friday, April 20, 2018 10:36 PM
To: Alpha
Subject: [FlickType-alpha] Build 44

Build 44
Looks good. The swipe up for caps is working again.
The swipe down and hold brings up the menu and nothing else. Personally I
like the two finger swipe up better.
The keyboard is stable and responsive.

I still do not hear anything when deleting partial words. I may be in the
minority, but I would rather hear gibberish then nothing, at least I would
have an idea where the cursor is. Otherwise, I like it!


Chuck
Re: Build 44

Chuck Dean
 

Hi Alan,
My best guess is it has something to do with the system wide extension coming in the future. Perhaps Kosta wants us to be ready with the proper gesture.

Chuck

On Apr 20, 2018, at 10:11 PM, Alan Lemly <@walemly> wrote:

I can confirm Chuck's findings too. The new gesture to invoke the menu works
as it should with no control center being invoked. I also prefer the old 2
finger swipe up to invoke the menu. I'm curious, why is another gesture to
invoke the menu needed? Are the plans to have two different ways to invoke
the menu and if not, which one will survive?

Thanks for all your hard work.

Alan Lemly

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of Chuck Dean
Sent: Friday, April 20, 2018 10:36 PM
To: Alpha
Subject: [FlickType-alpha] Build 44

Build 44
Looks good. The swipe up for caps is working again.
The swipe down and hold brings up the menu and nothing else. Personally I
like the two finger swipe up better.
The keyboard is stable and responsive.

I still do not hear anything when deleting partial words. I may be in the
minority, but I would rather hear gibberish then nothing, at least I would
have an idea where the cursor is. Otherwise, I like it!


Chuck
Re: Build 44

Macster
 

Hi guys,

I'm very happy to say the two problems I encountered with the previous build are now not an issue. Superb job in a short period of time again. I like the idea of announcing deletion of partial words, though as you say it might be difficult to follow depending on the accuracy or otherwise of my typing.

I genuinely think this is the best the app has ever worked, and I include the old app in that as well. And the new flick down and hold gesture works a treat. Bliss!
Re: Build 44

Alan Lemly
 

Chuck,

That makes perfect sense. I'm so caught up enjoying the standalone FlickType
that I keep forgetting about the third party keyboard extension and how it
can impact the gesture decisions.

Alan

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of Chuck Dean
Sent: Saturday, April 21, 2018 12:17 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 44

Hi Alan,
My best guess is it has something to do with the system wide extension
coming in the future. Perhaps Kosta wants us to be ready with the proper
gesture.

Chuck


On Apr 20, 2018, at 10:11 PM, Alan Lemly <@walemly> wrote:

I can confirm Chuck's findings too. The new gesture to invoke the menu
works as it should with no control center being invoked. I also prefer
the old 2 finger swipe up to invoke the menu. I'm curious, why is
another gesture to invoke the menu needed? Are the plans to have two
different ways to invoke the menu and if not, which one will survive?

Thanks for all your hard work.

Alan Lemly

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On
Behalf Of Chuck Dean
Sent: Friday, April 20, 2018 10:36 PM
To: Alpha
Subject: [FlickType-alpha] Build 44

Build 44
Looks good. The swipe up for caps is working again.
The swipe down and hold brings up the menu and nothing else.
Personally I like the two finger swipe up better.
The keyboard is stable and responsive.

I still do not hear anything when deleting partial words. I may be in
the minority, but I would rather hear gibberish then nothing, at least
I would have an idea where the cursor is. Otherwise, I like it!


Chuck
Re: Build 44

Chuck Dean
 

I am hoping the stand alone app will be supported after the system wide extension is implemented. I think I'd still use it, although if the system wide keyboard works as well as the app, perhaps not.

Chuck

On Apr 20, 2018, at 10:44 PM, Alan Lemly <@walemly> wrote:

Chuck,

That makes perfect sense. I'm so caught up enjoying the standalone FlickType
that I keep forgetting about the third party keyboard extension and how it
can impact the gesture decisions.

Alan

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of Chuck Dean
Sent: Saturday, April 21, 2018 12:17 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 44

Hi Alan,
My best guess is it has something to do with the system wide extension
coming in the future. Perhaps Kosta wants us to be ready with the proper
gesture.

Chuck


On Apr 20, 2018, at 10:11 PM, Alan Lemly <@walemly> wrote:

I can confirm Chuck's findings too. The new gesture to invoke the menu
works as it should with no control center being invoked. I also prefer
the old 2 finger swipe up to invoke the menu. I'm curious, why is
another gesture to invoke the menu needed? Are the plans to have two
different ways to invoke the menu and if not, which one will survive?

Thanks for all your hard work.

Alan Lemly

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On
Behalf Of Chuck Dean
Sent: Friday, April 20, 2018 10:36 PM
To: Alpha
Subject: [FlickType-alpha] Build 44

Build 44
Looks good. The swipe up for caps is working again.
The swipe down and hold brings up the menu and nothing else.
Personally I like the two finger swipe up better.
The keyboard is stable and responsive.

I still do not hear anything when deleting partial words. I may be in
the minority, but I would rather hear gibberish then nothing, at least
I would have an idea where the cursor is. Otherwise, I like it!


Chuck
Re: Build 44

Chanelle Allen
 

Hello,
This is another awesome version of FlickType! Thank you, Kosta and Ashley! The new flick down and hold gesture works well and as expected. I am also curious as to why new menu gestures are being introduced. I appreciate that VoiceOver now announces what it should every time the tap and hold gesture is invoked to find letters/numbers/symbols. I am also hearing VoiceOver announce when I delete incorrectly typed characters. Maybe the more we type, the more confident we will become about what is being deleted. I am slightly embarrassed that I have not used FlickType on a regular basis since it is quicker to type short texts using braille screen input directly in the Messages or Mail app, but being a member of the alpha group has given me motivation and excitement for when FlickType becomes a keyboard.
By the way, someday, it would be so neat if we could actually type on our wrists! I think that the apple watch needs more processing power though.
Chanelle

On Apr 21, 2018, at 00:36, Macster <@Macster> wrote:

Hi guys,

I'm very happy to say the two problems I encountered with the previous build are now not an issue. Superb job in a short period of time again. I like the idea of announcing deletion of partial words, though as you say it might be difficult to follow depending on the accuracy or otherwise of my typing.

I genuinely think this is the best the app has ever worked, and I include the old app in that as well. And the new flick down and hold gesture works a treat. Bliss!
Just a suggestion,

Chuck Dean
 

Just a suggestion,
Hello Kosta,
Could you add @ icloud.com. to the list under the @ sign?
Considering all of us are using iphones, many may be using this as an email address. I use it as a secondary... More private email address.
Thanks,


Chuck
TestFlight down for anyone else?

Alan Lemly
 

Hi list,

I've been getting an error message for several hours from TestFlight that it is down for temporary maintenance. Is anyone else getting this? It seems to have been going on for a lot longer than I'd call temporary.

Thanks.

Alan Lemly