Date   

Re: A test with Fleksy.

 

Thank you Ed, that does clear it up. Aside from the unbeatable aspect that the standard VoiceOver cursor mechanism is familiar, can you describe in more detail what aspects of it you prefer over the gesture control in FlickType?

Kosta 

On May 20, 2018, at 12:16, Ed Worrell <ed.worrell@...> wrote:

Kosta, 

all of the basic gestures are the same between FlickType and Fleksy. I guess I was more referring to the difference between the default iOS keyboard. And Fleksy. Not to take anything away from your cursor control but I prefer using the VoiceOver rotor with the half screen keyboard. I just feel that the simpler you can make the gestures the better it will be for all users. With Fleksy in the minimum style keyboard the gestures are very simple and straight forward. The only thing I am missing is the ability to quickly switch between modes such as symbols and numbers. I hope this clears up my previous email... 

Ed


On May 20, 2018, at 1:07 PM, FlickType <hello@...> wrote:

Ed, you mentioned: “The typing is so much easier and quicker for me with the gestures I forgive the stutter with VoiceOver.”  

What gestures are you referring to that are not available in FlickType? Are you talking about the new line?

Kosta 

On May 20, 2018, at 12:04, Chuck Dean <cadean329@...> wrote:

Hi Ed, thanks, I'll try it once I turn on Fleksy again. I don't like having more than two keyboards active at a time.


Chuck

On May 20, 2018, at 11:37 AM, Ed Worrell <ed.worrell@...> wrote:

Chuck, 

try performing a two finger flick down in the bottom right hand corner. This should insert a new line. 

 Ed


On May 20, 2018, at 12:34 PM, Chuck Dean <cadean329@...> wrote:

H


u Kosta, i went back and downloaded Fleksy again to see how it interacts with the iOS screen. As i an typing this, i an using the Fleksy minimal keyboard. The keyboard is the bottom half of the screen, and i can interact with all the nails text fields and i can use the rotor Tu move the cursor where i want. The predictive engine doesn't seem as good, it has a stutter when announcing words, and there is no good way to insert a new line. Also, changing keyboards is a nightmare, having to change to the spacebar keyboard first, then using the globe button to select a keyboard. My pointr is, this would be the perfect keyboard layout, for me anyways, and is what i mean by a half screen keyboard. Plus i can easily input my text replacements. 😎 👍 




Re: A test with Fleksy.

Ed Worrell
 

Kosta, 

all of the basic gestures are the same between FlickType and Fleksy. I guess I was more referring to the difference between the default iOS keyboard. And Fleksy. Not to take anything away from your cursor control but I prefer using the VoiceOver rotor with the half screen keyboard. I just feel that the simpler you can make the gestures the better it will be for all users. With Fleksy in the minimum style keyboard the gestures are very simple and straight forward. The only thing I am missing is the ability to quickly switch between modes such as symbols and numbers. I hope this clears up my previous email... 

Ed


On May 20, 2018, at 1:07 PM, FlickType <hello@...> wrote:

Ed, you mentioned: “The typing is so much easier and quicker for me with the gestures I forgive the stutter with VoiceOver.”  

What gestures are you referring to that are not available in FlickType? Are you talking about the new line?

Kosta 

On May 20, 2018, at 12:04, Chuck Dean <cadean329@...> wrote:

Hi Ed, thanks, I'll try it once I turn on Fleksy again. I don't like having more than two keyboards active at a time.


Chuck

On May 20, 2018, at 11:37 AM, Ed Worrell <ed.worrell@...> wrote:

Chuck, 

try performing a two finger flick down in the bottom right hand corner. This should insert a new line. 

 Ed


On May 20, 2018, at 12:34 PM, Chuck Dean <cadean329@...> wrote:

H


u Kosta, i went back and downloaded Fleksy again to see how it interacts with the iOS screen. As i an typing this, i an using the Fleksy minimal keyboard. The keyboard is the bottom half of the screen, and i can interact with all the nails text fields and i can use the rotor Tu move the cursor where i want. The predictive engine doesn't seem as good, it has a stutter when announcing words, and there is no good way to insert a new line. Also, changing keyboards is a nightmare, having to change to the spacebar keyboard first, then using the globe button to select a keyboard. My pointr is, this would be the perfect keyboard layout, for me anyways, and is what i mean by a half screen keyboard. Plus i can easily input my text replacements. 😎 👍 




Re: iPhone X bug in build 68

 

Hi David,

The dedicated next keyboard button at the very bottom of the screen on the iPhone X is always there, and no keyboard can change that. But what happens is that if you start a tap and hold gesture in the main keyboard area, your touch is not allowed to cross over to the dedicated bottom area of the iPhone X. But if you start your tap and hold further towards the very bottom of the device it should work. Regardless, I recommend you switch using the flicktype gesture, although I understand that this might not currently be ideal due to needing more than one finger.

Kosta

On May 20, 2018, at 12:03, David Nason <dnason@...> wrote:

Ok I am still intermittently experiencing this issue of the text I've typed disappearing when returning to the iOS keyboard by using the next keyboard button on iPhone X. It happened again earlier today, but then fixed itself, without a restart.
In addition, I was also experiencing the issue Chuck mentioned where some of the text I have typed would appear twice in the text field after dismissing the keyboard.
I have also noticed that the next keyboard button does not appear when in touch typing mode. So it's actually become rather difficult to access. If and when there is a one finger gesture to dismiss FlickType or switch to the iOS keyboard, then this will not matter though.

Dave
On 20 May 2018, at 00:34, David Nason <dnason@...> wrote:

Ok yes, a restart seems to have fixed the issue.
It just started at some point during the day today, not even straight away after installing build 68. I'll let you know if it happens again at all.

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

Thanks for the report. I can't seem to be able to reproduce this on my iPhone X. Did this only start happening with build 68? And have you tried restarting your device?

- Kosta


Re: A test with Fleksy.

 

Ed, you mentioned: “The typing is so much easier and quicker for me with the gestures I forgive the stutter with VoiceOver.”  

What gestures are you referring to that are not available in FlickType? Are you talking about the new line?

Kosta 

On May 20, 2018, at 12:04, Chuck Dean <cadean329@...> wrote:

Hi Ed, thanks, I'll try it once I turn on Fleksy again. I don't like having more than two keyboards active at a time.


Chuck

On May 20, 2018, at 11:37 AM, Ed Worrell <ed.worrell@...> wrote:

Chuck, 

try performing a two finger flick down in the bottom right hand corner. This should insert a new line. 

 Ed


On May 20, 2018, at 12:34 PM, Chuck Dean <cadean329@...> wrote:

H


u Kosta, i went back and downloaded Fleksy again to see how it interacts with the iOS screen. As i an typing this, i an using the Fleksy minimal keyboard. The keyboard is the bottom half of the screen, and i can interact with all the nails text fields and i can use the rotor Tu move the cursor where i want. The predictive engine doesn't seem as good, it has a stutter when announcing words, and there is no good way to insert a new line. Also, changing keyboards is a nightmare, having to change to the spacebar keyboard first, then using the globe button to select a keyboard. My pointr is, this would be the perfect keyboard layout, for me anyways, and is what i mean by a half screen keyboard. Plus i can easily input my text replacements. 😎 👍 




Re: A test with Fleksy.

Chuck Dean
 

Hi Ed, thanks, I'll try it once I turn on Fleksy again. I don't like having more than two keyboards active at a time.


Chuck

On May 20, 2018, at 11:37 AM, Ed Worrell <ed.worrell@...> wrote:

Chuck, 

try performing a two finger flick down in the bottom right hand corner. This should insert a new line. 

 Ed


On May 20, 2018, at 12:34 PM, Chuck Dean <cadean329@...> wrote:

H


u Kosta, i went back and downloaded Fleksy again to see how it interacts with the iOS screen. As i an typing this, i an using the Fleksy minimal keyboard. The keyboard is the bottom half of the screen, and i can interact with all the nails text fields and i can use the rotor Tu move the cursor where i want. The predictive engine doesn't seem as good, it has a stutter when announcing words, and there is no good way to insert a new line. Also, changing keyboards is a nightmare, having to change to the spacebar keyboard first, then using the globe button to select a keyboard. My pointr is, this would be the perfect keyboard layout, for me anyways, and is what i mean by a half screen keyboard. Plus i can easily input my text replacements. 😎 👍 




Re: iPhone X bug in build 68

David Nason
 

Ok I am still intermittently experiencing this issue of the text I've typed disappearing when returning to the iOS keyboard by using the next keyboard button on iPhone X. It happened again earlier today, but then fixed itself, without a restart.
In addition, I was also experiencing the issue Chuck mentioned where some of the text I have typed would appear twice in the text field after dismissing the keyboard.
I have also noticed that the next keyboard button does not appear when in touch typing mode. So it's actually become rather difficult to access. If and when there is a one finger gesture to dismiss FlickType or switch to the iOS keyboard, then this will not matter though.

Dave

On 20 May 2018, at 00:34, David Nason <dnason@...> wrote:

Ok yes, a restart seems to have fixed the issue.
It just started at some point during the day today, not even straight away after installing build 68. I'll let you know if it happens again at all.

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

Thanks for the report. I can't seem to be able to reproduce this on my iPhone X. Did this only start happening with build 68? And have you tried restarting your device?

- Kosta




Re: A test with Fleksy.

Chuck Dean
 


Hi Kosta, the stutter is annoying but I could learn to live with it.. I noticed when I turned off voice over the stutter was gone but there was a delay. 

If their was a good way to enter a new line, an easier way to change to the numbers and symbols, and to switch keyboards, as you have implemented in FlickType, I would be pleased with that particular layout.


Chuck

On May 20, 2018, at 11:39 AM, FlickType <hello@...> wrote:

Thank you Chuck. Is the word stutter bearable? I remember that with the first flicktype builds with manual input, most people complained about the stutter or the delay that was used as a workaround to prevent the stutter.

Kosta 

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

H


u Kosta, i went back and downloaded Fleksy again to see how it interacts with the iOS screen. As i an typing this, i an using the Fleksy minimal keyboard. The keyboard is the bottom half of the screen, and i can interact with all the nails text fields and i can use the rotor Tu move the cursor where i want. The predictive engine doesn't seem as good, it has a stutter when announcing words, and there is no good way to insert a new line. Also, changing keyboards is a nightmare, having to change to the spacebar keyboard first, then using the globe button to select a keyboard. My pointr is, this would be the perfect keyboard layout, for me anyways, and is what i mean by a half screen keyboard. Plus i can easily input my text replacements. 😎 👍 




Re: Build 69

Matthew Janusauskas
 


I have also experienced this with my iPhone X.


On May 20, 2018, at 10:56 AM, Chuck Dean <cadean329@...> wrote:

 Hi Kosta, 

as you may have noticed, after I reviewed my text with the three finger swipe down, I returned to type some more. The cursor moved to the top, and my last sentence was repeated. 

I replicated this problem while trying to reply, and I am now trying to figure out what is happening. 



Chuck

On May 20, 2018, at 8:47 AM, FlickType <hello@...> wrote:

Hi Ed,

What you propose sounds good. I’d probably still add a numbers and symbols button on the main layout so that people who don’t know about the magic tap gesture can still switch to numbers and symbols in an intuitive way, even if it’s slower. After all, I believe the magic tap in iOS is only meant to be a shortcut to trigger an action that can also be performed in a traditional way, so I think we should maintain that principle here too.

Regardless, reassigning the magic tap to the above does mean that there will need to be another gesture to switch to the iOS keyboard, which does bring me to my following point: like Chuck just wrote, if what you’re looking to do is review your text and possibly send it, you can always do that by dismissing the keyboard entirely rather than switching to the iOS one. This way you can also more easily resume typing in flicktype by simply double tapping on the text field again. In fact, I’d love to know more about the most common use cases that absolutely require you to switch to the iOS keyboard. The one case that flicktype might never be able to cover is dictation, unless Apple eventually allows 3rd party keyboards to access the microphone. Another case right now is text replacement shortcuts, but these will be soon available in FlickType as well. Same goes for emoji. The standard iOS predictions above the keyboard are also not currently available in FlickType, and I’d love to know if and how much people use those. And again, to review the text using the traditional voiceover methods you can simply dismiss FlickType altogether by flicking down with 3 fingers. 

Kosta


On May 20, 2018, at 08:26, Chuck Dean <cadean329@...> wrote:

This process takes a lot of trial and error, and I admire your patience. Btw I discovered the three finger swipe down to dismiss the keyboard works fantastic to review what I had just typed... I just have to remember that it is available. 
😎 
Hi Kosta, 

personally I think the permanent typing mode with the flick right to exit would work best for me. Most of my use of manual entry is for caps and numbers. 

The tap and hold to enter symbols works great for me, and I was against it at first. This process takes a lot of trial and error, and I admire your patience.


Chuck

On May 20, 2018, at 7:44 AM, FlickType <hello@...> wrote:

I am indeed working towards making the two styles seamless. The key for that is seamless entry into, as well as seamless exit out of touch typing. Seamless entry can be achieved with what I think is the most intuitive gesture of holding down your finger to explore, since you’ll have to do that anyway to select your desired character. 

For seamless exit, there are two options at the top of my list:

One is making the touch typing entry be temporary, for a single character only, so as soon as you release your finger your are back into flick typing. This is similar to the app, but also if you release on the numbers and symbols key you’d remain in touch typing mode in the numbers and symbols layout, returning back to flick typing as soon as you enter a single character. Some downsides with this are: First, you can’t easily type multiple numbers and symbols in one go. To type a phone number for example, you’d have to tap, hold, and release on the numbers button, before being able to select each and every digit of the phone number. Second downside is that the touch typing gestures that only affect one character at a time, for example cursor move by character or changing the case of a character, would not be available since you’d always be in flick typing mode unless you are holding your finger down to explore. There are some workarounds for this though: one is to contextually bring those character gestures in flick typing mode, where the result of the exact same flick gesture would depend on whether you’ve last typed a single character or an entire word. This also would be similar to the app, where for example flick left to delete may delete a character. The other workaround is to take advantage of the fact that releasing on the numbers button leaves you in the touch typing mode without holding down anything anymore, so those character gestures could be performed there. 

The other seamless exit option is indeed the flick right, or space key, or both. You very likely will be doing that anyway, and you can always keep touch typing the next word too if you want. And until you exit by flicking right, you can perform all the character gestures too. I call this the permanent touch typing mode, as opposed to temporary above. Chanelle, you mentioned that this wouldn’t work for you because you use touch typing to enter a lot of symbols, can you please elaborate, perhaps with some examples?

A hybrid approach could involve the first temporary option where you always return back to flick typing after a single character, unless you go to numbers and symbols. And if you do go to numbers and symbols, you could stay there permanently until a flick right.  

I should also note that there are plenty more details to figure out here, as well as many other ways to achieve the desired features. Also the more the two styles blend into each other, the more it makes sense to call them something else, like word mode vs character mode. 

Happy to hear your thoughts,
Kosta


On May 20, 2018, at 07:02, David Nason <dnason@...> wrote:


Hi Macky,

the advantage though of the tap and hold to switch is that you can switch to manual and slide to the key you want, all in one fluid motion, making it much like the experience of manual typing in the main app. This is a huge step forward in my own opinion. 

For me, the interesting question is in finding the best way to get back to the flick mode again. And perhaps Benny is onto an idea that can be developed. 

Personally I would also like a one finger gesture to dismiss the keyboard, as I like to operate the phone one handed, using my thumb, as much as possible. 

That's my thoughts anyway. As you say, its interesting to read the different preferences in the group. 

Dave




On 20 May 2018, at 14:45, Macster <alan.macdonald1@...> wrote:

I think there is a split in the camp here, but I preferred the double tap gesture to enable the touch typing mode and the press and hold gesture to return to the iOS keyboard. My reasoning for this is the double tap is quicker and I invariably would be changing between flick and touch much more than flick and iOS. It just seemed more responsive to me that way and it also eliminated the need to feel around for the dedicated change back to flick typing button at the bottom. I don't think there is a right or wrong answer to this, just personal preference. Macky 


On 20 May 2018, at 09:55, David Nason <dnason@...> wrote:

I'm a little on the fence about the choice of gestures. I do definitely prefer the tap and hold to the magic tap, but the fact that you can't use the same gesture to go back from the touch typing mode to the flick mode is arguably a problem. My brain would prefer if I could use the same gesture to go both ways.

I really like what you've done in this build though, in that I can tap and hold, and navigate to the key I want, all in one go. Superb. 

I too like the idea of a half screen option. But I also see that this could be difficult for some users. Many people cannot see enough to be as targeted as others in there taps, so the full screen keyboard allows them much more ability to type successfully. So if implemented, it would have to be optional. The same fact is true for the discussion yesterday about typing accuracy. Of course user training and practice is necessary, but its easier for those of us who have some usable sight to be accurate than those who don't. So lets not dismiss the need to keep that conversation in mind.

Dave
 


On 20 May 2018, at 03:08, Chuck Dean <cadean329@...> wrote:


This is another reason for the half screen keyboard. If the top half is the iOS screen, we could use the rotor to edit text and to change the cursor position; leaving the FlickType area for the same gestures as the app's keyboard.


Chuck

On May 19, 2018, at 7:03 PM, George Cham <George.cham@...> wrote:

If thats the case , after flicking right for space, can we have a flick gesture down for symbles  and numbers ?

Kind Regards,

George Cham



From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Ed Worrell <ed.worrell@...>
Sent: Sunday, May 20, 2018 11:57:33 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 69
 
I think we will have the same manual typing as the keyboard in the future. 

Ed
I believe at some point there will be no difference between the modes. I think the short cuts are simply there to return to the gesture keyboard at this point and time. I think we will have the same manual typing as the keyboard in the future.
> On May 19, 2018, at 7:02 PM, Benny Barber <rebelben@...> wrote:
> 
> 
> I prefer the magic tap to return to the iOS keyboard and tap and hold for direct typing. Thanks. 
> 
> Benny
> 
>> On May 19, 2018, at 7:16 PM, FlickType <hello@...> wrote:
>> 
>> - Allow the same long press gesture that triggers Touch Typing to continue the exploration, so you don't have to start a second press every time.
>> - Fix shift sometimes not being in the correct state upon entering Touch Typing mode.
>> 
>> Please continue providing as much feedback as possible, thank you all for being so awesome!
>> 
>> - Kosta
>> 
>> 
>> 
> 
> 
> 
> 





Re: A test with Fleksy.

Ed Worrell
 

I too use the Fleksy keyboard off and on. The stutter is ok. The typing is so much easier and quicker for me with the gestures I forgive the stutter with VoiceOver. Kosta, you mentioned that turning off Voiceover feedback whilst typing would fix the stuttering issues. Like I mentioned in a previous email if the keyboard is fully functional with everything working as it should I would be ok with the word announcement being turned off in VoiceOver settings. 

Just my thoughts on the idea.. 

Ed


On May 20, 2018, at 12:39 PM, FlickType <hello@...> wrote:

Thank you Chuck. Is the word stutter bearable? I remember that with the first flicktype builds with manual input, most people complained about the stutter or the delay that was used as a workaround to prevent the stutter.

Kosta 

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

H


u Kosta, i went back and downloaded Fleksy again to see how it interacts with the iOS screen. As i an typing this, i an using the Fleksy minimal keyboard. The keyboard is the bottom half of the screen, and i can interact with all the nails text fields and i can use the rotor Tu move the cursor where i want. The predictive engine doesn't seem as good, it has a stutter when announcing words, and there is no good way to insert a new line. Also, changing keyboards is a nightmare, having to change to the spacebar keyboard first, then using the globe button to select a keyboard. My pointr is, this would be the perfect keyboard layout, for me anyways, and is what i mean by a half screen keyboard. Plus i can easily input my text replacements. 😎 👍 




Re: A test with Fleksy.

 

Ed, how are you finding the word feedback with the Fleksy custom keyboard?

Kosta 

On May 20, 2018, at 11:40, Ed Worrell <ed.worrell@...> wrote:

Chuck, 

you are correct. I too like the style of the minimum keyboard. This would be great to have with FlickType at some point in the future. 

Ed 


On May 20, 2018, at 12:34 PM, Chuck Dean <cadean329@...> wrote:

H


u Kosta, i went back and downloaded Fleksy again to see how it interacts with the iOS screen. As i an typing this, i an using the Fleksy minimal keyboard. The keyboard is the bottom half of the screen, and i can interact with all the nails text fields and i can use the rotor Tu move the cursor where i want. The predictive engine doesn't seem as good, it has a stutter when announcing words, and there is no good way to insert a new line. Also, changing keyboards is a nightmare, having to change to the spacebar keyboard first, then using the globe button to select a keyboard. My pointr is, this would be the perfect keyboard layout, for me anyways, and is what i mean by a half screen keyboard. Plus i can easily input my text replacements. 😎 👍 




Re: A test with Fleksy.

Ed Worrell
 

Chuck, 

you are correct. I too like the style of the minimum keyboard. This would be great to have with FlickType at some point in the future. 

Ed 


On May 20, 2018, at 12:34 PM, Chuck Dean <cadean329@...> wrote:

H


u Kosta, i went back and downloaded Fleksy again to see how it interacts with the iOS screen. As i an typing this, i an using the Fleksy minimal keyboard. The keyboard is the bottom half of the screen, and i can interact with all the nails text fields and i can use the rotor Tu move the cursor where i want. The predictive engine doesn't seem as good, it has a stutter when announcing words, and there is no good way to insert a new line. Also, changing keyboards is a nightmare, having to change to the spacebar keyboard first, then using the globe button to select a keyboard. My pointr is, this would be the perfect keyboard layout, for me anyways, and is what i mean by a half screen keyboard. Plus i can easily input my text replacements. 😎 👍 




Re: A test with Fleksy.

 

Thank you Chuck. Is the word stutter bearable? I remember that with the first flicktype builds with manual input, most people complained about the stutter or the delay that was used as a workaround to prevent the stutter.

Kosta 

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

H


u Kosta, i went back and downloaded Fleksy again to see how it interacts with the iOS screen. As i an typing this, i an using the Fleksy minimal keyboard. The keyboard is the bottom half of the screen, and i can interact with all the nails text fields and i can use the rotor Tu move the cursor where i want. The predictive engine doesn't seem as good, it has a stutter when announcing words, and there is no good way to insert a new line. Also, changing keyboards is a nightmare, having to change to the spacebar keyboard first, then using the globe button to select a keyboard. My pointr is, this would be the perfect keyboard layout, for me anyways, and is what i mean by a half screen keyboard. Plus i can easily input my text replacements. 😎 👍 




Re: A test with Fleksy.

Ed Worrell
 

Chuck, 

try performing a two finger flick down in the bottom right hand corner. This should insert a new line. 

 Ed


On May 20, 2018, at 12:34 PM, Chuck Dean <cadean329@...> wrote:

H


u Kosta, i went back and downloaded Fleksy again to see how it interacts with the iOS screen. As i an typing this, i an using the Fleksy minimal keyboard. The keyboard is the bottom half of the screen, and i can interact with all the nails text fields and i can use the rotor Tu move the cursor where i want. The predictive engine doesn't seem as good, it has a stutter when announcing words, and there is no good way to insert a new line. Also, changing keyboards is a nightmare, having to change to the spacebar keyboard first, then using the globe button to select a keyboard. My pointr is, this would be the perfect keyboard layout, for me anyways, and is what i mean by a half screen keyboard. Plus i can easily input my text replacements. 😎 👍 




Re: Build 69

 

Hi Alan,

I believe you are experiencing a bug rather than the intended behavior. Ashley also got something like that last night. Do you have exact steps to reproduce by any chance? Does it always happen for you when trying to return to flick typing?

Also I understand that changing the behavior and gestures every few builds can be overwhelming, and even more so when there’s additional bugs to top it all off. Please bear with us while we figure things out together, smile!

Kosta

On May 20, 2018, at 11:03, Alan Lemly <@walemly> wrote:

Hi Kosta,

I'm running iOS 11.3.1 on an iPhone 7 and I'm getting a strange result with this latest build. I have restarted my iPhone since getting this strange result but it continues. When I press and hold to go from FlickType to touch typing mode, I'm unable to return to FlickTyping mode. I've tried placing my finger on the style key to the left of the spacebar and though it announces FlickTyping, I still seem to be in touch typing mode. The odd thing is that the mode I'm in really seems to be sort of a hybrid mode because when I tap quickly to enter words as I do with the main app, they are being announced even though I know darned well I'm not hitting the correct keys. However, I'm still able to move across the keyboard and have individual letters announced. Maybe I'm not understanding what is presented and its operation when switching between FlickTyping and touch typing modes. Are all the keys such as spacebar, etc. that are present when touch typing also available when FlickTyping? I wouldn't have thought so but they seem to be with this hybrid mode I'm experiencing.

I also prefer the magic tap button to switch between FlickTyping and touch typing but I mainly just want a decision to be made so I can get to learning and using whatever it is provided it works as it should. I know the whole purpose of alpha and beta testing is to iron out the wrinkles but I'm finding it much easier just to type with the main app until the final system wide keyboard is released. It's starting to feel as if many have a different opinion of the ideal gesture to do the same thing which is fine but I expect I'll get about learning whatever is decided and I also expect your decision will more than likely be the best one.

Anyway, I'd appreciate any comments on the hybrid results I seem to be getting switching between FlickTyping and touch typing.

Alan Lemly

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf Of FlickType
Sent: Saturday, May 19, 2018 7:17 PM
To: alpha@flicktype.groups.io
Subject: [FlickType-alpha] Build 69

- Allow the same long press gesture that triggers Touch Typing to continue the exploration, so you don't have to start a second press every time.
- Fix shift sometimes not being in the correct state upon entering Touch Typing mode.

Please continue providing as much feedback as possible, thank you all for being so awesome!

- Kosta






A test with Fleksy.

Chuck Dean
 

H


u Kosta, i went back and downloaded Fleksy again to see how it interacts with the iOS screen. As i an typing this, i an using the Fleksy minimal keyboard. The keyboard is the bottom half of the screen, and i can interact with all the nails text fields and i can use the rotor Tu move the cursor where i want. The predictive engine doesn't seem as good, it has a stutter when announcing words, and there is no good way to insert a new line. Also, changing keyboards is a nightmare, having to change to the spacebar keyboard first, then using the globe button to select a keyboard. My pointr is, this would be the perfect keyboard layout, for me anyways, and is what i mean by a half screen keyboard. Plus i can easily input my text replacements. 😎 👍 




Re: Build 69

 

Hi Kosta,

I'm running iOS 11.3.1 on an iPhone 7 and I'm getting a strange result with this latest build. I have restarted my iPhone since getting this strange result but it continues. When I press and hold to go from FlickType to touch typing mode, I'm unable to return to FlickTyping mode. I've tried placing my finger on the style key to the left of the spacebar and though it announces FlickTyping, I still seem to be in touch typing mode. The odd thing is that the mode I'm in really seems to be sort of a hybrid mode because when I tap quickly to enter words as I do with the main app, they are being announced even though I know darned well I'm not hitting the correct keys. However, I'm still able to move across the keyboard and have individual letters announced. Maybe I'm not understanding what is presented and its operation when switching between FlickTyping and touch typing modes. Are all the keys such as spacebar, etc. that are present when touch typing also available when FlickTyping? I wouldn't have thought so but they seem to be with this hybrid mode I'm experiencing.

I also prefer the magic tap button to switch between FlickTyping and touch typing but I mainly just want a decision to be made so I can get to learning and using whatever it is provided it works as it should. I know the whole purpose of alpha and beta testing is to iron out the wrinkles but I'm finding it much easier just to type with the main app until the final system wide keyboard is released. It's starting to feel as if many have a different opinion of the ideal gesture to do the same thing which is fine but I expect I'll get about learning whatever is decided and I also expect your decision will more than likely be the best one.

Anyway, I'd appreciate any comments on the hybrid results I seem to be getting switching between FlickTyping and touch typing.

Alan Lemly

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf Of FlickType
Sent: Saturday, May 19, 2018 7:17 PM
To: alpha@flicktype.groups.io
Subject: [FlickType-alpha] Build 69

- Allow the same long press gesture that triggers Touch Typing to continue the exploration, so you don't have to start a second press every time.
- Fix shift sometimes not being in the correct state upon entering Touch Typing mode.

Please continue providing as much feedback as possible, thank you all for being so awesome!

- Kosta


Re: This may be a good time to start a pole.

Ed Worrell
 

Kosta,

much like chuck I would love to see a half screen option in the future. I now understand the difficulties in developing this. I however would be willing to forgo character or word feedback but only if the keyboard functions are mature as you said. I would be greatful for this way off in the future of the keyboard.

Ed

On May 20, 2018, at 11:52 AM, FlickType <@FlickType> wrote:

I sent this earlier just as you posted the idea for the poll, but I think it's worth repeating here:

A half-screen option is probably doable, but currently presents many challenges due to the system VoiceOver announcements interfering with the FlickType announcements. You might remember that from the first builds of the manual typing where you had to change your VoiceOver typing feedback settings. This is not the case when the keyboard is fullscreen, simply because in that case FlickType does not change the contents of the underlying textfield until you dismiss it or switch to the next keyboard, so there are no system VoiceOver announcements to worry about. And we can't make FlickType only cover part of the screen with this workaround behavior, because then you'd notice that the text in the textfield is empty or entirely different from what FlickType is reporting, until you dismiss it or switch to the next keyboard. If you are willing to disable your VoiceOver word typing feedback, this could work, but I think most people would rather not have to change their VoiceOver settings. Perhaps when manual mode is fully developed we can revisit that, since you'd very rarely need to use the iOS keyboard in that case, and hence you might be ok with changing the typing feedback. There's also another possible workaround here, where as soon as you touch away from the half screen FlickType keyboard, we would immediately commit all changes to the textfield. But all this is opening a whole world of possible issues so for now we'll stick with the full screen mode until more things are in place and the full screen mode is more mature.

Kosta



Re: This may be a good time to start a pole.

 

I sent this earlier just as you posted the idea for the poll, but I think it's worth repeating here:

A half-screen option is probably doable, but currently presents many challenges due to the system VoiceOver announcements interfering with the FlickType announcements. You might remember that from the first builds of the manual typing where you had to change your VoiceOver typing feedback settings. This is not the case when the keyboard is fullscreen, simply because in that case FlickType does not change the contents of the underlying textfield until you dismiss it or switch to the next keyboard, so there are no system VoiceOver announcements to worry about. And we can't make FlickType only cover part of the screen with this workaround behavior, because then you'd notice that the text in the textfield is empty or entirely different from what FlickType is reporting, until you dismiss it or switch to the next keyboard. If you are willing to disable your VoiceOver word typing feedback, this could work, but I think most people would rather not have to change their VoiceOver settings. Perhaps when manual mode is fully developed we can revisit that, since you'd very rarely need to use the iOS keyboard in that case, and hence you might be ok with changing the typing feedback. There's also another possible workaround here, where as soon as you touch away from the half screen FlickType keyboard, we would immediately commit all changes to the textfield. But all this is opening a whole world of possible issues so for now we'll stick with the full screen mode until more things are in place and the full screen mode is more mature.

Kosta


Re: Build 69

 

Salman: flick and hold gestures are coming soon. These are not built into the iOS APIs so I have to create my own, and that takes a bit of time, but once done it means that single and double flick and hold gestures of all 4 directions will be available to assign to actions as needed. I, too, would like to be able to switch to the iOS keyboard or dismiss the keyboard altogether with just one finger, so we will try that and see how it feels.

Ed, on using enter to activate the search function in search boxes: thank you for pointing that out. This only applies to single-line text fields where you cannot enter a new line, but I agree that it's still going to be very useful to be able to do that right from within FlickType. What happens after you enter a Return from FlickType will depend on the app, so for example on the App Store search field this will trigger the search and dismiss the keyboard, whereas in the mail app this will allow you to move from the recipient field to the subject field, and then to the message body field. The reason this is not currently working is because FlickType does not commit any changes to the underlying textfield until you dismiss it, for reasons I explained in my previous email. But I will investigate making an exception so that whenever you use the Return key or perform the future new line gesture, FlickType will automatically commit all changes to the textfield. VoiceOver will try to announce all the text in that case, but maybe that's not a big deal and I can also try to suppress that after a small delay.

Thank you all for the discussion, this has been a great thread. Please keep it coming, smile!

Kosta


Re: This may be a good time to start a pole.

Michael Maslo
 

My responds is no

Sincerely,, mike 


On May 20, 2018 at 11:34, <Chuck Dean> wrote:

 Hello everyone,


this may be a good time to start a poll to see how many of us would like to see a half screen option. Does any one know how to set one up?