Date   

Re: A test with Fleksy.

Chuck Dean
 


Allegedly a two finger swipe down is supposed to insert a new line, but I can not get any consistency. Most of the time it will insert a comma or question mark, and in the rare case that it does insert a new line, it usually inserts two lines.


Chuck

On May 20, 2018, at 7:42 PM, FlickType <hello@...> wrote:

Thank you Chuck, this is useful to know. What’s the difficulty with entering a new line? Is the gesture hard to trigger reliably?

Kosta

On May 20, 2018, at 18:24, Chuck Dean <cadean329@...> wrote:

Hi Kosta, i went into settings and turned off typing feedback to try and rid Fleksy of the stutter. It seemed better but not gone. I still have great difficulties entering a new line, and switching to another keyboard. Just thought you would light to know. 


Chuck

On May 20, 2018, at 11:34 AM, 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, this is useful to know. What’s the difficulty with entering a new line? Is the gesture hard to trigger reliably?

Kosta

On May 20, 2018, at 18:24, Chuck Dean <cadean329@...> wrote:

Hi Kosta, i went into settings and turned off typing feedback to try and rid Fleksy of the stutter. It seemed better but not gone. I still have great difficulties entering a new line, and switching to another keyboard. Just thought you would light to know. 


Chuck

On May 20, 2018, at 11:34 AM, 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
 


I was playing with Fleksy most of the day, and cane to the same conclusion. Then I switched back to FlickType... So much better!


Chuck

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

Hey chuck and Kosta, 

I have come to the same conclusion you have. I also turned off the word repeat on Fleksy and had the same findings. The voice still stutters whilst changing suggestions, and VoiceOver makes some end of document sounds when swiping. The keyboard isn't perfect but it's still faster than the iOS keyboard. 

Ed


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

Hi Kosta, i went into settings and turned off typing feedback to try and rid Fleksy of the stutter. It seemed better but not gone. I still have great difficulties entering a new line, and switching to another keyboard. Just thought you would light to know. 


Chuck

On May 20, 2018, at 11:34 AM, 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
 

Hey chuck and Kosta, 

I have come to the same conclusion you have. I also turned off the word repeat on Fleksy and had the same findings. The voice still stutters whilst changing suggestions, and VoiceOver makes some end of document sounds when swiping. The keyboard isn't perfect but it's still faster than the iOS keyboard. 

Ed


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

Hi Kosta, i went into settings and turned off typing feedback to try and rid Fleksy of the stutter. It seemed better but not gone. I still have great difficulties entering a new line, and switching to another keyboard. Just thought you would light to know. 


Chuck

On May 20, 2018, at 11:34 AM, 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 Kosta, i went into settings and turned off typing feedback to try and rid Fleksy of the stutter. It seemed better but not gone. I still have great difficulties entering a new line, and switching to another keyboard. Just thought you would light to know. 


Chuck

On May 20, 2018, at 11:34 AM, 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

 

Chanelle,

Thanks for the suggestion. I'm not sure what you described is my issue because the main FlickType app which I'm using to type this is working just fine. I don't use any other apps which use direct touch other than perhaps the Fleksy keyboard.

I'm hoping this is a bug that will be resolved. Kosta said that Ashley experienced a similar issue too.

I'll keep the list posted.

Alan Lemly

On May 20, 2018, at 6:50 PM, Chanelle Allen <chanellem.allen@...> wrote:

Hi Alan and List,
Alan, it seems as if FlickType is acting for you as it did on my phone several builds ago when I inadvertently turned off direct touch. In my case, the FlickType keyboard and ap behaved as if touch typing was permanently enabled, but I couldn't really explore the keyboard with VoiceOver at the same time. It might be helpful for you to go into the FlickType app to determine if flick typing and touch typing are working as they should. If FlickType is not behaving correctly in the app, turning off VoiceOver and relying on whatever voice the app uses will cause FlickType to respond correctly to normal operation. Since that is not a permanent fix, there are a few things you might try. First, with FlickType on and VoiceOver enabled, try performing the rotor gesture. This might work better in the FlickType keyboard. If you can't change the rotor setting, try flicking up or down before typing. If that doesn't work (which it probably won't), do you have an accessible game that you play on your iDevice with VoiceOver? Some apps and games need to take over all or part of the functionality of VoiceOver, so developers enable direct touch, which allows their particular app gestures to pass through. If you think that you have another app that uses direct touch, try adjusting the rotor while in the app. Somehow, in all of my restoring/resetting activity, I was able to adjust direct touch in FlickType, but that is something normally not possible. Finally, if none of these options help, there is an option under Settings > General > Reset, which is called Reset All Settings. "Reset All Settings" puts everything back to default without erasing content and data. It's probably what I should have done before erasing my phone, but it needed a good restore. I cannot guarantee that Reset All Settings is the final answer. It didn't work for me, but I think that was due to iCloud attempting to restore my phone from a backup.
I hope that your FlickType issue isn't that complicated, and if it is, that I have been of some assistance.
Chanelle

On May 20, 2018, at 17:15, Alan Lemly <@walemly> wrote:

Hi Kosta?

The first time I went to the system wide keyboard with build 69 I was in FlickTyping mode which I believe is the default behavior. I then did a single finger tap and hold to switch to touch typing mode and I believe I've been in that mode ever since. Pressing on the button to the left of the spacebar which announces FlickTyping doesn't seem to change anything. That's about all I remember for purposes of trying to duplicate my issue.

Alan Lemly
On May 20, 2018, at 1:34 PM, FlickType <@FlickType> wrote:

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









Re: Build 69

Chanelle Allen
 

Hi Alan and List,
Alan, it seems as if FlickType is acting for you as it did on my phone several builds ago when I inadvertently turned off direct touch. In my case, the FlickType keyboard and ap behaved as if touch typing was permanently enabled, but I couldn't really explore the keyboard with VoiceOver at the same time. It might be helpful for you to go into the FlickType app to determine if flick typing and touch typing are working as they should. If FlickType is not behaving correctly in the app, turning off VoiceOver and relying on whatever voice the app uses will cause FlickType to respond correctly to normal operation. Since that is not a permanent fix, there are a few things you might try. First, with FlickType on and VoiceOver enabled, try performing the rotor gesture. This might work better in the FlickType keyboard. If you can't change the rotor setting, try flicking up or down before typing. If that doesn't work (which it probably won't), do you have an accessible game that you play on your iDevice with VoiceOver? Some apps and games need to take over all or part of the functionality of VoiceOver, so developers enable direct touch, which allows their particular app gestures to pass through. If you think that you have another app that uses direct touch, try adjusting the rotor while in the app. Somehow, in all of my restoring/resetting activity, I was able to adjust direct touch in FlickType, but that is something normally not possible. Finally, if none of these options help, there is an option under Settings > General > Reset, which is called Reset All Settings. "Reset All Settings" puts everything back to default without erasing content and data. It's probably what I should have done before erasing my phone, but it needed a good restore. I cannot guarantee that Reset All Settings is the final answer. It didn't work for me, but I think that was due to iCloud attempting to restore my phone from a backup.
I hope that your FlickType issue isn't that complicated, and if it is, that I have been of some assistance.
Chanelle

On May 20, 2018, at 17:15, Alan Lemly <@walemly> wrote:

Hi Kosta?

The first time I went to the system wide keyboard with build 69 I was in FlickTyping mode which I believe is the default behavior. I then did a single finger tap and hold to switch to touch typing mode and I believe I've been in that mode ever since. Pressing on the button to the left of the spacebar which announces FlickTyping doesn't seem to change anything. That's about all I remember for purposes of trying to duplicate my issue.

Alan Lemly
On May 20, 2018, at 1:34 PM, FlickType <@FlickType> wrote:

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








Re: Build 69

Chanelle Allen
 



Hi Kosta, 
you gave us much to consider. Keeping in mind that I quite often accidentally start flick typing when I have finished touch typing without first switching to the correct mode, their is definitely an advantage to choice #1. As you stated, maybe the exceptions could be numbers and symbols. After finishing with a number or punctuation sequence, maybe the flick right gesture could signal that flick typing should resume. Benny's idea is practical and now makes more sense. Even though you provide excellent documentation of all changes to FlickType with each new build, I overlooked the fact that the flick right gesture is now used in touch typing to insert a space. I have become so accustomed to searching for the spacebar when touch typing, so I need to transform my thinking. I don't see myself having any problems with either of the transition methods that you described, but I think that my preference would be for #2. I also agree that changing the wording of the modes would make things less complicated. Touch typing allows us to review character by character whereas flick typing enables reading of words and sentences. Sometimes, I wish that I had a way of getting into touch typing mode just to review the letters of a word in case VoiceOver or the suggestion didn't sound very clear. For now, aside from going back to the iOS keyboard, my work around is to look for the shift or "more numbers" keys after leaving flick mode with the touch and explore gesture so that I do not insert an additional letter. I can't wait until you are able to try your ideas out on us. Thank you. 
 
Chanelle

On May 20, 2018, at 09:44, 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: Build 69

 

Hi Kosta?

The first time I went to the system wide keyboard with build 69 I was in FlickTyping mode which I believe is the default behavior. I then did a single finger tap and hold to switch to touch typing mode and I believe I've been in that mode ever since. Pressing on the button to the left of the spacebar which announces FlickTyping doesn't seem to change anything. That's about all I remember for purposes of trying to duplicate my issue.

Alan Lemly

On May 20, 2018, at 1:34 PM, FlickType <@FlickType> wrote:

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







Re: A test with Fleksy.

Paul Sutton
 

Hi chuck, I totally agree with you. Perhaps at some point in the future it might be possible to adjust the size of the FlickType keyboard. Just for example have it filling maybe 75% of the screen which would give the user just a little more room to play with but still giving enough room to navigate text fields. Or perhaps even giving the user the ability to adjust the keyboard to the size that they are most comfortable with. 
Regards, Paul


On 20 May 2018, at 22:27, Chuck Dean <cadean329@...> wrote:

Hi Paul,
Yes, that’s very understandable that a totally blind person would have much more problems with half screen keyboard then with the whole screen keyboard. I think this is why the full screen keyboard was initially invented.
I guess this is why we need more than one keyboard.
Although, a partially sighted person could also use a full screen keyboard, so I think the best route is to work with full screen keyboard now, and perhaps in the future go with half screen keyboard.


Chuck

On May 20, 2018, at 2:24 PM, Paul Sutton <sutty_p@...> wrote:


Out of curiosity I just installed Fleksy and had a quick go. I found it incredibly difficult because I was trying really hard not to tap above the Fleksy keyboard so as a consequence my typing was terrible and messy. 
I can however understand the benefits from having a half screen keyboard from the point of view that it would be a lot more easy to fill in multiple text fields. 
By the way, I am writing this from the view of a totally blind user. 
Regards, Paul.


On 20 May 2018, at 22:02, Chuck Dean <cadean329@...> wrote:

If I may chime in here, 

I like the rotor because it is familiar to me and is used in other situations, so I also like the consistency of the controls. I sometimes get frustrated because I have forgotten a basic gesture and have screwed up my typing. 

But the reason I like the Fleksy minimal keyboard is, for instance, if I am composing an email, first I enter the recipient, then I can double tap in the subject field and type in the  subject of the email, then I can double tap on the text body and start typing, all without having to change keyboards or doing a dismiss. The same is true when sending a text message. 

I understand you like the words being visible on the top half of the screen, and it is pretty cool, but my sad eyes wouldn't use this feature very much and I'd prefer to have the interaction with the iPhone's screen.,  


Chuck

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

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.

Chuck Dean
 

Hi Ed,
This is why Kosta has such a big job ahead of him. There are so many different types of vision acuity, and even when people have the same vision acuity, some people have better spatial recognition than others. He has a very hard road to ride.

Even sighted people cannot agree on what’s the best keyboard, if you look in the App Store there are hundreds.
Chuck

On May 20, 2018, at 2:32 PM, Ed Worrell <ed.worrell@...> wrote:

Hey chuck and all, 

I am completely blind and I find the half screen keyboard much more user friendly. The productivity level for me is much, much faster with the half screen effort. 

Ed


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

Hi Paul,
Yes, that’s very understandable that a totally blind person would have much more problems with half screen keyboard then with the whole screen keyboard. I think this is why the full screen keyboard was initially invented.
I guess this is why we need more than one keyboard.
Although, a partially sighted person could also use a full screen keyboard, so I think the best route is to work with full screen keyboard now, and perhaps in the future go with half screen keyboard.


Chuck

On May 20, 2018, at 2:24 PM, Paul Sutton <sutty_p@...> wrote:


Out of curiosity I just installed Fleksy and had a quick go. I found it incredibly difficult because I was trying really hard not to tap above the Fleksy keyboard so as a consequence my typing was terrible and messy. 
I can however understand the benefits from having a half screen keyboard from the point of view that it would be a lot more easy to fill in multiple text fields. 
By the way, I am writing this from the view of a totally blind user. 
Regards, Paul.


On 20 May 2018, at 22:02, Chuck Dean <cadean329@...> wrote:

If I may chime in here, 

I like the rotor because it is familiar to me and is used in other situations, so I also like the consistency of the controls. I sometimes get frustrated because I have forgotten a basic gesture and have screwed up my typing. 

But the reason I like the Fleksy minimal keyboard is, for instance, if I am composing an email, first I enter the recipient, then I can double tap in the subject field and type in the  subject of the email, then I can double tap on the text body and start typing, all without having to change keyboards or doing a dismiss. The same is true when sending a text message. 

I understand you like the words being visible on the top half of the screen, and it is pretty cool, but my sad eyes wouldn't use this feature very much and I'd prefer to have the interaction with the iPhone's screen.,  


Chuck

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

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
 

Hey chuck and all, 

I am completely blind and I find the half screen keyboard much more user friendly. The productivity level for me is much, much faster with the half screen effort. 

Ed


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

Hi Paul,
Yes, that’s very understandable that a totally blind person would have much more problems with half screen keyboard then with the whole screen keyboard. I think this is why the full screen keyboard was initially invented.
I guess this is why we need more than one keyboard.
Although, a partially sighted person could also use a full screen keyboard, so I think the best route is to work with full screen keyboard now, and perhaps in the future go with half screen keyboard.


Chuck

On May 20, 2018, at 2:24 PM, Paul Sutton <sutty_p@...> wrote:


Out of curiosity I just installed Fleksy and had a quick go. I found it incredibly difficult because I was trying really hard not to tap above the Fleksy keyboard so as a consequence my typing was terrible and messy. 
I can however understand the benefits from having a half screen keyboard from the point of view that it would be a lot more easy to fill in multiple text fields. 
By the way, I am writing this from the view of a totally blind user. 
Regards, Paul.


On 20 May 2018, at 22:02, Chuck Dean <cadean329@...> wrote:

If I may chime in here, 

I like the rotor because it is familiar to me and is used in other situations, so I also like the consistency of the controls. I sometimes get frustrated because I have forgotten a basic gesture and have screwed up my typing. 

But the reason I like the Fleksy minimal keyboard is, for instance, if I am composing an email, first I enter the recipient, then I can double tap in the subject field and type in the  subject of the email, then I can double tap on the text body and start typing, all without having to change keyboards or doing a dismiss. The same is true when sending a text message. 

I understand you like the words being visible on the top half of the screen, and it is pretty cool, but my sad eyes wouldn't use this feature very much and I'd prefer to have the interaction with the iPhone's screen.,  


Chuck

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

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.

Chuck Dean
 

Hi Paul,
Yes, that’s very understandable that a totally blind person would have much more problems with half screen keyboard then with the whole screen keyboard. I think this is why the full screen keyboard was initially invented.
I guess this is why we need more than one keyboard.
Although, a partially sighted person could also use a full screen keyboard, so I think the best route is to work with full screen keyboard now, and perhaps in the future go with half screen keyboard.


Chuck

On May 20, 2018, at 2:24 PM, Paul Sutton <sutty_p@...> wrote:


Out of curiosity I just installed Fleksy and had a quick go. I found it incredibly difficult because I was trying really hard not to tap above the Fleksy keyboard so as a consequence my typing was terrible and messy. 
I can however understand the benefits from having a half screen keyboard from the point of view that it would be a lot more easy to fill in multiple text fields. 
By the way, I am writing this from the view of a totally blind user. 
Regards, Paul.


On 20 May 2018, at 22:02, Chuck Dean <cadean329@...> wrote:

If I may chime in here, 

I like the rotor because it is familiar to me and is used in other situations, so I also like the consistency of the controls. I sometimes get frustrated because I have forgotten a basic gesture and have screwed up my typing. 

But the reason I like the Fleksy minimal keyboard is, for instance, if I am composing an email, first I enter the recipient, then I can double tap in the subject field and type in the  subject of the email, then I can double tap on the text body and start typing, all without having to change keyboards or doing a dismiss. The same is true when sending a text message. 

I understand you like the words being visible on the top half of the screen, and it is pretty cool, but my sad eyes wouldn't use this feature very much and I'd prefer to have the interaction with the iPhone's screen.,  


Chuck

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

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.

George Cham
 

I had fleksy installed , however if you plan on importing your dictionary  , fleksy will launch as the deafult app .

Kind regards,

George Cham

‘May the Lord bless you and protect you. May the Lord smile on you and be gracious to you. May the Lord show you his favor and give you his peace.’
Numbers 6:24-26
Get Outlook for iOS


From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Chuck Dean <cadean329@...>
Sent: Monday, May 21, 2018 7:02:47 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] A test with Fleksy.
 
If I may chime in here, 

I like the rotor because it is familiar to me and is used in other situations, so I also like the consistency of the controls. I sometimes get frustrated because I have forgotten a basic gesture and have screwed up my typing. 

But the reason I like the Fleksy minimal keyboard is, for instance, if I am composing an email, first I enter the recipient, then I can double tap in the subject field and type in the  subject of the email, then I can double tap on the text body and start typing, all without having to change keyboards or doing a dismiss. The same is true when sending a text message. 

I understand you like the words being visible on the top half of the screen, and it is pretty cool, but my sad eyes wouldn't use this feature very much and I'd prefer to have the interaction with the iPhone's screen.,  


Chuck

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

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.

Chuck Dean
 

Hi,
I find just the opposite! 
It looks like Kosta really has his work cut out for him. 😎 


Chuck

On May 20, 2018, at 2:21 PM, Matthew Janusauskas <mjanusauskas@...> wrote:


I find the two and three-finger swipe cursor movement gestures to be far more efficient and fluid than the extra movements required to use the Voiceover rotor, even though the rotor is still more familiar and is used in so many other contexts. Just my opinion.

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

If I may chime in here, 

I like the rotor because it is familiar to me and is used in other situations, so I also like the consistency of the controls. I sometimes get frustrated because I have forgotten a basic gesture and have screwed up my typing. 

But the reason I like the Fleksy minimal keyboard is, for instance, if I am composing an email, first I enter the recipient, then I can double tap in the subject field and type in the  subject of the email, then I can double tap on the text body and start typing, all without having to change keyboards or doing a dismiss. The same is true when sending a text message. 

I understand you like the words being visible on the top half of the screen, and it is pretty cool, but my sad eyes wouldn't use this feature very much and I'd prefer to have the interaction with the iPhone's screen.,  


Chuck

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

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.

Paul Sutton
 


Out of curiosity I just installed Fleksy and had a quick go. I found it incredibly difficult because I was trying really hard not to tap above the Fleksy keyboard so as a consequence my typing was terrible and messy. 
I can however understand the benefits from having a half screen keyboard from the point of view that it would be a lot more easy to fill in multiple text fields. 
By the way, I am writing this from the view of a totally blind user. 
Regards, Paul.


On 20 May 2018, at 22:02, Chuck Dean <cadean329@...> wrote:

If I may chime in here, 

I like the rotor because it is familiar to me and is used in other situations, so I also like the consistency of the controls. I sometimes get frustrated because I have forgotten a basic gesture and have screwed up my typing. 

But the reason I like the Fleksy minimal keyboard is, for instance, if I am composing an email, first I enter the recipient, then I can double tap in the subject field and type in the  subject of the email, then I can double tap on the text body and start typing, all without having to change keyboards or doing a dismiss. The same is true when sending a text message. 

I understand you like the words being visible on the top half of the screen, and it is pretty cool, but my sad eyes wouldn't use this feature very much and I'd prefer to have the interaction with the iPhone's screen.,  


Chuck

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

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.

Matthew Janusauskas
 


I find the two and three-finger swipe cursor movement gestures to be far more efficient and fluid than the extra movements required to use the Voiceover rotor, even though the rotor is still more familiar and is used in so many other contexts. Just my opinion.

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

If I may chime in here, 

I like the rotor because it is familiar to me and is used in other situations, so I also like the consistency of the controls. I sometimes get frustrated because I have forgotten a basic gesture and have screwed up my typing. 

But the reason I like the Fleksy minimal keyboard is, for instance, if I am composing an email, first I enter the recipient, then I can double tap in the subject field and type in the  subject of the email, then I can double tap on the text body and start typing, all without having to change keyboards or doing a dismiss. The same is true when sending a text message. 

I understand you like the words being visible on the top half of the screen, and it is pretty cool, but my sad eyes wouldn't use this feature very much and I'd prefer to have the interaction with the iPhone's screen.,  


Chuck

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

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. 😎 👍 




A weird problem I have, encountered a few times

Chuck Dean
 

Hi Kosta

this is a weird problem I have encountered a couple of times in the past, but much more since including the Fleksy keyboard.


Hi Kosta

this is a weird problem I have encountered a couple of times in the past, but much more since including the Fleksy keyboard.

If I am using Fleksy and change keyboards it usually goes to the FlickType keyboard, so I'll do a two finger double tap to go to the iOS keyboard which will change correctly, but will also start playing the last audio I listened to. If I do another two finger double tap, it will start dictation then if I two finger double tap again, it will start the audio again, etc. I basically have to exit and two finger double tap on the home screen to stop all the nonsense.,


Chuck


Re: A test with Fleksy.

Chuck Dean
 

If I may chime in here, 

I like the rotor because it is familiar to me and is used in other situations, so I also like the consistency of the controls. I sometimes get frustrated because I have forgotten a basic gesture and have screwed up my typing. 

But the reason I like the Fleksy minimal keyboard is, for instance, if I am composing an email, first I enter the recipient, then I can double tap in the subject field and type in the  subject of the email, then I can double tap on the text body and start typing, all without having to change keyboards or doing a dismiss. The same is true when sending a text message. 

I understand you like the words being visible on the top half of the screen, and it is pretty cool, but my sad eyes wouldn't use this feature very much and I'd prefer to have the interaction with the iPhone's screen.,  


Chuck

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

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
 

Hey Kosta, 

I really think that is it in its simplest form. I am use to using it everyday. I really am not sure what could make the FlickType cursor control on par with the VoiceOver rotor option. I guess just making the FlickType manual input more seamless, and adding the new line feature would make me use the FlickType keyboard in more circumstances. You have done a great job, I really think it's simply the VoiceOver rotor is built in.


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

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. 😎 👍