Date   
Re: Build 159

David Nason
 

ok here goes. Typing feedback is set to characters only in the VoiceOver settings, but I'm still getting the high pitch top word suggestion.
However, for this sentence, I have turned characters off as well, so set to Nothing, and the high pitch has gone away. Interestingly, it is also saying the full stop after the second swipe right, rather than space. so that's two bugs "fixed" for the price of one.

Of course though, I do still sometimes need to use the iOS keyboard, so would rather have typing feedback on if possible.

When I went to start this email by the way, the whole thing went haywire when I switched into FlickType, basically unresponsive. After a minute, and turning VoiceOver on and off a few times, it was back to normal. Hopefully just a little glitch.

It's still not reading apostrophe with the word suggestion. I can of course wait for the spelling feedback, but that slows things down.

When you delete the first word of a sentence, it says " beginning of document ", instead of "delete word ".

Dave

On 31 Aug 2018, at 21:32, Ed Worrell via Groups.Io <ed.worrell=icloud.com@groups.io> wrote:

Kosta,

I was performing the gesture properly. It just started working after your tip. Power of suggestion I guess.

Thanks,

Ed
On Aug 31, 2018, at 2:29 PM, FlickType <@FlickType> wrote:

Thank you Dave. Please try temporarily turning off iOS typing feedback for words and see if that helps with some of the issues you describe. Would love to know if it did help. I'll have to look into our old friend WhatsApp. On the quotation marks, you are correct, the issue is back in the non-full screen modes but should be fixed soon.

Ed, for the magic tap gesture, besides making sure the focus is on the keyboard, you also need to make sure you perform the gesture within the keyboard area for FlickType to capture it.

Benny, can you confirm you are using build 160? Please also try temporarily turning off iOS typing feedback for words and see if that helps. Anyone else experiencing the issues with the Mail app that Benny is describing?

- Kosta



Re: Build 159

Ed Worrell
 

Kosta,

I was performing the gesture properly. It just started working after your tip. Power of suggestion I guess.

Thanks,

Ed

On Aug 31, 2018, at 2:29 PM, FlickType <@FlickType> wrote:

Thank you Dave. Please try temporarily turning off iOS typing feedback for words and see if that helps with some of the issues you describe. Would love to know if it did help. I'll have to look into our old friend WhatsApp. On the quotation marks, you are correct, the issue is back in the non-full screen modes but should be fixed soon.

Ed, for the magic tap gesture, besides making sure the focus is on the keyboard, you also need to make sure you perform the gesture within the keyboard area for FlickType to capture it.

Benny, can you confirm you are using build 160? Please also try temporarily turning off iOS typing feedback for words and see if that helps. Anyone else experiencing the issues with the Mail app that Benny is describing?

- Kosta


Re: Build 159

 

Thank you Dave. Please try temporarily turning off iOS typing feedback for words and see if that helps with some of the issues you describe. Would love to know if it did help. I'll have to look into our old friend WhatsApp. On the quotation marks, you are correct, the issue is back in the non-full screen modes but should be fixed soon.

Ed, for the magic tap gesture, besides making sure the focus is on the keyboard, you also need to make sure you perform the gesture within the keyboard area for FlickType to capture it.

Benny, can you confirm you are using build 160? Please also try temporarily turning off iOS typing feedback for words and see if that helps. Anyone else experiencing the issues with the Mail app that Benny is describing?

- Kosta

Re: Build 159

David Nason
 

Hi Kosta,

For whatever reason, I seem to be having more luck with the latest build. I really like the new standard size.

I am still having the issue with the top word suggestion being too high pitched. I am on iOS 12 and typing feedback is set to characters and words. Is anyone else noticing that?

I am having much more success now interacting with the area above the keyboard, and using the rotor etc.

Our old friend WhatsApp is causing a bit of an issue though. In that app, when I swipe left to delete, VoiceOver is not saying " delete word " as it does in other apps, instead just saying " bottom of document ". Meaning I don't even know if it has deleted the word, or where the cursor actually is or what.

It is now spelling back words to me. I don't know if the restart or the new build fixed that.

I have noticed a small difference when typing in half screen versus full screen. if I type a word with an apostrophe, for example "don't"
when offering the word suggestion, VoiceOver will say “don apostrophe t" in full screen mode, but simply say "don't" in half or standard mode.
having it actually say the apostrophe is very useful for distinguishing between words like "its" and "it's" for example.

Reviewing the above text, I see some unwanted spaces beside quotation marks. Is that issue back in the standard/half keyboard?

Dave

On 31 Aug 2018, at 19:43, FlickType <@FlickType> wrote:

Thank you for the feedback. One of the goals as we are developing the half screen mode is to make sure the full screen mode remains unaffected. We don't want to accidentally break any existing functionality, and the full screen mode is always going to be a first class citizen of FlickType. So please keep testing the full screen mode as well, and definitely let us know if we mess it up ☺️

- The issue of announcing a space when inserting a period will be fixed soon.
- Benny: are you still having the same troubles with build 160? A lot of stability issues have been addressed in just the last couple of days.
- Salman: the possibility of touching a point outside the keyboard area is definitely a drawback of the smaller size modes, and for some people this might be a deal breaker. Hence we will provide everyone a choice of keyboard height that is most comfortable to use. That said, when you get back into the keyboard area you should now be able to delete the last typed word as usual, even if it's already entered into the field. Theoretically all this should now be seamless. Of course we are still working on a few glitches.
- Chuck: changing back to letters after typing only one number has always been the case, if I'm not mistaken. We plan to improve that, but I wanted to make sure this is not a new issue in recent builds.

Thank you, please keep the feedback and ideas coming ☺️


Re: Build 159

Benny Barber
 

Kosta,
I am mostly working in the mail app. When I touch in the upper part of the screen, I never get feedback of what I just typed. I have to start at the top and swipe down until I get to the message body. In the message body I cannot maneuver the cursor properly. I get erratic feedback. I may hear a letter, word or sentence. Trying to move the cursor is impossible and sometimes FlickType crashes while trying to do so. I don't understand how others are able to do so.
In the standard height keyboard, in every swipe the feedback is stuttering. I'm sorry, but I can't find a way to use the half or partial keyboard.
Benny

On Aug 31, 2018, at 1:43 PM, FlickType <@FlickType> wrote:

Thank you for the feedback. One of the goals as we are developing the half screen mode is to make sure the full screen mode remains unaffected. We don't want to accidentally break any existing functionality, and the full screen mode is always going to be a first class citizen of FlickType. So please keep testing the full screen mode as well, and definitely let us know if we mess it up ☺️

- The issue of announcing a space when inserting a period will be fixed soon.
- Benny: are you still having the same troubles with build 160? A lot of stability issues have been addressed in just the last couple of days.
- Salman: the possibility of touching a point outside the keyboard area is definitely a drawback of the smaller size modes, and for some people this might be a deal breaker. Hence we will provide everyone a choice of keyboard height that is most comfortable to use. That said, when you get back into the keyboard area you should now be able to delete the last typed word as usual, even if it's already entered into the field. Theoretically all this should now be seamless. Of course we are still working on a few glitches.
- Chuck: changing back to letters after typing only one number has always been the case, if I'm not mistaken. We plan to improve that, but I wanted to make sure this is not a new issue in recent builds.

Thank you, please keep the feedback and ideas coming ☺️


Re: Build 159

Ed Worrell
 

Hello Kosta,

I am having issues with the magic tap gesture in the standard keyboard size.
I try to access the symbols keyboard and my stored music starts playing. I make sure that focus is in side the keyboard section and perform the gesture and music starts up. FlickType doesn't switch to the symbols keyboard. I have restarted my phone with no luck.
I'm on ios 12 Vega 12.
Thanks,. Ed

On Aug 31, 2018, at 1:00 PM, Chuck Dean <cadean329@...> wrote:

Hello,
Sometimes I can type multiple digit numbers and then flick right to go to the letters keyboard. Today was the first time I noticed that I could only type one digit, then flicktype would go to the letters keyboard without any other action. This is not consistent, as sometimes it is working as usual.

54321
There... I typed that number without having to switch to the number keyboard each time.
my first attempt at typing that number, I typed the 5, and as soon as it said five it switched to the letters keyboard... But not this time.😎 ❓❓❓
Chuck

On Aug 31, 2018, at 11:43 AM, FlickType <@FlickType> wrote:

Thank you for the feedback. One of the goals as we are developing the half screen mode is to make sure the full screen mode remains unaffected. We don't want to accidentally break any existing functionality, and the full screen mode is always going to be a first class citizen of FlickType. So please keep testing the full screen mode as well, and definitely let us know if we mess it up ☺️

- The issue of announcing a space when inserting a period will be fixed soon.
- Benny: are you still having the same troubles with build 160? A lot of stability issues have been addressed in just the last couple of days.
- Salman: the possibility of touching a point outside the keyboard area is definitely a drawback of the smaller size modes, and for some people this might be a deal breaker. Hence we will provide everyone a choice of keyboard height that is most comfortable to use. That said, when you get back into the keyboard area you should now be able to delete the last typed word as usual, even if it's already entered into the field. Theoretically all this should now be seamless. Of course we are still working on a few glitches.
- Chuck: changing back to letters after typing only one number has always been the case, if I'm not mistaken. We plan to improve that, but I wanted to make sure this is not a new issue in recent builds.

Thank you, please keep the feedback and ideas coming ☺️



Re: Build 159

Chuck Dean
 

Hello,
Sometimes I can type multiple digit numbers and then flick right to go to the letters keyboard. Today was the first time I noticed that I could only type one digit, then flicktype would go to the letters keyboard without any other action. This is not consistent, as sometimes it is working as usual.

54321
There... I typed that number without having to switch to the number keyboard each time.
my first attempt at typing that number, I typed the 5, and as soon as it said five it switched to the letters keyboard... But not this time.😎 ❓❓❓
Chuck

On Aug 31, 2018, at 11:43 AM, FlickType <@FlickType> wrote:

Thank you for the feedback. One of the goals as we are developing the half screen mode is to make sure the full screen mode remains unaffected. We don't want to accidentally break any existing functionality, and the full screen mode is always going to be a first class citizen of FlickType. So please keep testing the full screen mode as well, and definitely let us know if we mess it up ☺️

- The issue of announcing a space when inserting a period will be fixed soon.
- Benny: are you still having the same troubles with build 160? A lot of stability issues have been addressed in just the last couple of days.
- Salman: the possibility of touching a point outside the keyboard area is definitely a drawback of the smaller size modes, and for some people this might be a deal breaker. Hence we will provide everyone a choice of keyboard height that is most comfortable to use. That said, when you get back into the keyboard area you should now be able to delete the last typed word as usual, even if it's already entered into the field. Theoretically all this should now be seamless. Of course we are still working on a few glitches.
- Chuck: changing back to letters after typing only one number has always been the case, if I'm not mistaken. We plan to improve that, but I wanted to make sure this is not a new issue in recent builds.

Thank you, please keep the feedback and ideas coming ☺️


Re: Build 159

 

Thank you for the feedback. One of the goals as we are developing the half screen mode is to make sure the full screen mode remains unaffected. We don't want to accidentally break any existing functionality, and the full screen mode is always going to be a first class citizen of FlickType. So please keep testing the full screen mode as well, and definitely let us know if we mess it up ☺️

- The issue of announcing a space when inserting a period will be fixed soon.
- Benny: are you still having the same troubles with build 160? A lot of stability issues have been addressed in just the last couple of days.
- Salman: the possibility of touching a point outside the keyboard area is definitely a drawback of the smaller size modes, and for some people this might be a deal breaker. Hence we will provide everyone a choice of keyboard height that is most comfortable to use. That said, when you get back into the keyboard area you should now be able to delete the last typed word as usual, even if it's already entered into the field. Theoretically all this should now be seamless. Of course we are still working on a few glitches.
- Chuck: changing back to letters after typing only one number has always been the case, if I'm not mistaken. We plan to improve that, but I wanted to make sure this is not a new issue in recent builds.

Thank you, please keep the feedback and ideas coming ☺️

Re: Build 159

Chuck Dean
 

Hello Ed,
He sure your focus is on the FlickType keyboard before you double tap.
Something related I just noticed. When I double tap to insert a number it will change back to letters after typing only one number.
I was trying to type the number 15 and it switched to letters after typing the one... But it didn't happen this time.
This build is good, but still a little jittery.

I'm sure Kosta will fix it in the next few days.😎
Chuck

On Aug 31, 2018, at 9:40 AM, Ed Worrell via Groups.Io <ed.worrell=icloud.com@groups.io> wrote:

Hey chuck,

The only thing I have discovered recently is the two finger double tap isn't working... It seems to be playing music instead of switching to the symbols keyboard.
Other than that it works well.

Ed
On Aug 31, 2018, at 10:37 AM, Chuck Dean <cadean329@...> wrote:

Hi Ed, I couldn't agree more.
One other thing I have noticed is sometimes there is a delay when inserting Punctuation or a new line. I find that turning VoiceOver off and then on again cures this problem. Otherwise it's working well.😎
Chuck

On Aug 31, 2018, at 9:25 AM, Ed Worrell via Groups.Io <ed.worrell=icloud.com@groups.io> wrote:

Hello all,

I am really enjoying the new standard sized keyboard. It works great for me...
I have turned off all typing feedback in the voiceover settings. Cursor navigation is working very well. I really am only seeing an issue with VoiceOver announcing space after I delete punctuation. Other then that great build so far.

Ed
On Aug 30, 2018, at 8:56 PM, Salman Haider <salmanhaider.purdue@...> wrote:

Definitely not giving up or anything. However, I hope that toggle is not at the cost of some existing gesture being taken away or changed or getting replaced as that would make things extremely extremely inconvenient.
I am not in favor of any existing functionality or features being taken away or replaced. Rather, new ones should be introduced. Not saying that that has happened, but just expressing an opinion in advance.
I am hoping there is a new and different gesture to make that toggle work.

On Aug 30, 2018, at 9:24 PM, Chuck Dean <cadean329@...> wrote:

Hello,
This is the reason kosta is developing a toggle for the full and half screen keyboard. For example: once you enter the recipients and subject into an email's field you can activate the message body, toggle to the full screen keyboard, and type the body without worrying about going outside the keyboard area.

don't give up yet, good things may be coming.😎
Chuck



On Aug 30, 2018, at 5:53 PM, Salman Haider <salmanhaider.purdue@...> wrote:

In addition to all the different glitches and bugs that everyone is
experiencing with the half-screen/standard size keyboard and reporting
here, I personally just find the full screen keyboard (or, the almost
full screen mode in my case since I use that due to experiencing
crashes in Whatsapp when using full screen only) just more convenient
and favorable to me. The issue that I encounter is, frequently
touching a point outside of the keyboard area, when attempting to
type, which throws me off. When I get back into the keyboard area, I
obviously can't delete the last word that I typed for instance, as
that text has already been entered into the field by that point. This
is something that I have always been afraid of (for me personally
anyway), considering how Flicktype works and the text is committed as
soon as one touches any area outside of the keyboard area. so I have
generally favored the full screen option more.
Add all the different bugs that are there at this time, and getting
things to work consistently becomes, like Benny said, a nightmare.
I definitely prefer the full-screen option for myself personally and
will be continuing to use that for now, and maybe even permanently.
Not at all against having the half screen option being developed and
available, but the full-screen option just works better for my typing
habits.

Salman

On 8/30/18, FlickType <@FlickType> wrote:
Thanks Chuck. From what I can tell, the cursor is actually moved by line as
expected, but FlickType only announces a single word. This is similar to
another issue covered earlier, and should be fixed soon.

As you all play more with it, I'd love to get a better sense of two things:
One, how close is the half screen mode to becoming more useful than the full
screen one, to the extent that you would use half screen more often than
full screen? Two, out of all issues so far, what is the biggest priority to
fix with the half screen as it stands today?

Thanks,
Kosta











Re: Build 159

Ed Worrell
 

Hey chuck,

The only thing I have discovered recently is the two finger double tap isn't working... It seems to be playing music instead of switching to the symbols keyboard.
Other than that it works well.

Ed

On Aug 31, 2018, at 10:37 AM, Chuck Dean <cadean329@...> wrote:

Hi Ed, I couldn't agree more.
One other thing I have noticed is sometimes there is a delay when inserting Punctuation or a new line. I find that turning VoiceOver off and then on again cures this problem. Otherwise it's working well.😎
Chuck

On Aug 31, 2018, at 9:25 AM, Ed Worrell via Groups.Io <ed.worrell=icloud.com@groups.io> wrote:

Hello all,

I am really enjoying the new standard sized keyboard. It works great for me...
I have turned off all typing feedback in the voiceover settings. Cursor navigation is working very well. I really am only seeing an issue with VoiceOver announcing space after I delete punctuation. Other then that great build so far.

Ed
On Aug 30, 2018, at 8:56 PM, Salman Haider <salmanhaider.purdue@...> wrote:

Definitely not giving up or anything. However, I hope that toggle is not at the cost of some existing gesture being taken away or changed or getting replaced as that would make things extremely extremely inconvenient.
I am not in favor of any existing functionality or features being taken away or replaced. Rather, new ones should be introduced. Not saying that that has happened, but just expressing an opinion in advance.
I am hoping there is a new and different gesture to make that toggle work.

On Aug 30, 2018, at 9:24 PM, Chuck Dean <cadean329@...> wrote:

Hello,
This is the reason kosta is developing a toggle for the full and half screen keyboard. For example: once you enter the recipients and subject into an email's field you can activate the message body, toggle to the full screen keyboard, and type the body without worrying about going outside the keyboard area.

don't give up yet, good things may be coming.😎
Chuck



On Aug 30, 2018, at 5:53 PM, Salman Haider <salmanhaider.purdue@...> wrote:

In addition to all the different glitches and bugs that everyone is
experiencing with the half-screen/standard size keyboard and reporting
here, I personally just find the full screen keyboard (or, the almost
full screen mode in my case since I use that due to experiencing
crashes in Whatsapp when using full screen only) just more convenient
and favorable to me. The issue that I encounter is, frequently
touching a point outside of the keyboard area, when attempting to
type, which throws me off. When I get back into the keyboard area, I
obviously can't delete the last word that I typed for instance, as
that text has already been entered into the field by that point. This
is something that I have always been afraid of (for me personally
anyway), considering how Flicktype works and the text is committed as
soon as one touches any area outside of the keyboard area. so I have
generally favored the full screen option more.
Add all the different bugs that are there at this time, and getting
things to work consistently becomes, like Benny said, a nightmare.
I definitely prefer the full-screen option for myself personally and
will be continuing to use that for now, and maybe even permanently.
Not at all against having the half screen option being developed and
available, but the full-screen option just works better for my typing
habits.

Salman

On 8/30/18, FlickType <@FlickType> wrote:
Thanks Chuck. From what I can tell, the cursor is actually moved by line as
expected, but FlickType only announces a single word. This is similar to
another issue covered earlier, and should be fixed soon.

As you all play more with it, I'd love to get a better sense of two things:
One, how close is the half screen mode to becoming more useful than the full
screen one, to the extent that you would use half screen more often than
full screen? Two, out of all issues so far, what is the biggest priority to
fix with the half screen as it stands today?

Thanks,
Kosta










Re: Build 159

Chuck Dean
 

Hi Ed, I couldn't agree more.
One other thing I have noticed is sometimes there is a delay when inserting Punctuation or a new line. I find that turning VoiceOver off and then on again cures this problem. Otherwise it's working well.😎
Chuck

On Aug 31, 2018, at 9:25 AM, Ed Worrell via Groups.Io <ed.worrell=icloud.com@groups.io> wrote:

Hello all,

I am really enjoying the new standard sized keyboard. It works great for me...
I have turned off all typing feedback in the voiceover settings. Cursor navigation is working very well. I really am only seeing an issue with VoiceOver announcing space after I delete punctuation. Other then that great build so far.

Ed
On Aug 30, 2018, at 8:56 PM, Salman Haider <salmanhaider.purdue@...> wrote:

Definitely not giving up or anything. However, I hope that toggle is not at the cost of some existing gesture being taken away or changed or getting replaced as that would make things extremely extremely inconvenient.
I am not in favor of any existing functionality or features being taken away or replaced. Rather, new ones should be introduced. Not saying that that has happened, but just expressing an opinion in advance.
I am hoping there is a new and different gesture to make that toggle work.

On Aug 30, 2018, at 9:24 PM, Chuck Dean <cadean329@...> wrote:

Hello,
This is the reason kosta is developing a toggle for the full and half screen keyboard. For example: once you enter the recipients and subject into an email's field you can activate the message body, toggle to the full screen keyboard, and type the body without worrying about going outside the keyboard area.

don't give up yet, good things may be coming.😎
Chuck



On Aug 30, 2018, at 5:53 PM, Salman Haider <salmanhaider.purdue@...> wrote:

In addition to all the different glitches and bugs that everyone is
experiencing with the half-screen/standard size keyboard and reporting
here, I personally just find the full screen keyboard (or, the almost
full screen mode in my case since I use that due to experiencing
crashes in Whatsapp when using full screen only) just more convenient
and favorable to me. The issue that I encounter is, frequently
touching a point outside of the keyboard area, when attempting to
type, which throws me off. When I get back into the keyboard area, I
obviously can't delete the last word that I typed for instance, as
that text has already been entered into the field by that point. This
is something that I have always been afraid of (for me personally
anyway), considering how Flicktype works and the text is committed as
soon as one touches any area outside of the keyboard area. so I have
generally favored the full screen option more.
Add all the different bugs that are there at this time, and getting
things to work consistently becomes, like Benny said, a nightmare.
I definitely prefer the full-screen option for myself personally and
will be continuing to use that for now, and maybe even permanently.
Not at all against having the half screen option being developed and
available, but the full-screen option just works better for my typing
habits.

Salman

On 8/30/18, FlickType <@FlickType> wrote:
Thanks Chuck. From what I can tell, the cursor is actually moved by line as
expected, but FlickType only announces a single word. This is similar to
another issue covered earlier, and should be fixed soon.

As you all play more with it, I'd love to get a better sense of two things:
One, how close is the half screen mode to becoming more useful than the full
screen one, to the extent that you would use half screen more often than
full screen? Two, out of all issues so far, what is the biggest priority to
fix with the half screen as it stands today?

Thanks,
Kosta









Re: Build 159

Ed Worrell
 

Hello all,

I am really enjoying the new standard sized keyboard. It works great for me...
I have turned off all typing feedback in the voiceover settings. Cursor navigation is working very well. I really am only seeing an issue with VoiceOver announcing space after I delete punctuation. Other then that great build so far.

Ed

On Aug 30, 2018, at 8:56 PM, Salman Haider <salmanhaider.purdue@...> wrote:

Definitely not giving up or anything. However, I hope that toggle is not at the cost of some existing gesture being taken away or changed or getting replaced as that would make things extremely extremely inconvenient.
I am not in favor of any existing functionality or features being taken away or replaced. Rather, new ones should be introduced. Not saying that that has happened, but just expressing an opinion in advance.
I am hoping there is a new and different gesture to make that toggle work.

On Aug 30, 2018, at 9:24 PM, Chuck Dean <cadean329@...> wrote:

Hello,
This is the reason kosta is developing a toggle for the full and half screen keyboard. For example: once you enter the recipients and subject into an email's field you can activate the message body, toggle to the full screen keyboard, and type the body without worrying about going outside the keyboard area.

don't give up yet, good things may be coming.😎
Chuck



On Aug 30, 2018, at 5:53 PM, Salman Haider <salmanhaider.purdue@...> wrote:

In addition to all the different glitches and bugs that everyone is
experiencing with the half-screen/standard size keyboard and reporting
here, I personally just find the full screen keyboard (or, the almost
full screen mode in my case since I use that due to experiencing
crashes in Whatsapp when using full screen only) just more convenient
and favorable to me. The issue that I encounter is, frequently
touching a point outside of the keyboard area, when attempting to
type, which throws me off. When I get back into the keyboard area, I
obviously can't delete the last word that I typed for instance, as
that text has already been entered into the field by that point. This
is something that I have always been afraid of (for me personally
anyway), considering how Flicktype works and the text is committed as
soon as one touches any area outside of the keyboard area. so I have
generally favored the full screen option more.
Add all the different bugs that are there at this time, and getting
things to work consistently becomes, like Benny said, a nightmare.
I definitely prefer the full-screen option for myself personally and
will be continuing to use that for now, and maybe even permanently.
Not at all against having the half screen option being developed and
available, but the full-screen option just works better for my typing
habits.

Salman

On 8/30/18, FlickType <@FlickType> wrote:
Thanks Chuck. From what I can tell, the cursor is actually moved by line as
expected, but FlickType only announces a single word. This is similar to
another issue covered earlier, and should be fixed soon.

As you all play more with it, I'd love to get a better sense of two things:
One, how close is the half screen mode to becoming more useful than the full
screen one, to the extent that you would use half screen more often than
full screen? Two, out of all issues so far, what is the biggest priority to
fix with the half screen as it stands today?

Thanks,
Kosta








Re: Build 159

Salman Haider
 

Definitely not giving up or anything. However, I hope that toggle is not at the cost of some existing gesture being taken away or changed or getting replaced as that would make things extremely extremely inconvenient.
I am not in favor of any existing functionality or features being taken away or replaced. Rather, new ones should be introduced. Not saying that that has happened, but just expressing an opinion in advance.
I am hoping there is a new and different gesture to make that toggle work.

On Aug 30, 2018, at 9:24 PM, Chuck Dean <cadean329@...> wrote:

Hello,
This is the reason kosta is developing a toggle for the full and half screen keyboard. For example: once you enter the recipients and subject into an email's field you can activate the message body, toggle to the full screen keyboard, and type the body without worrying about going outside the keyboard area.

don't give up yet, good things may be coming.😎
Chuck



On Aug 30, 2018, at 5:53 PM, Salman Haider <salmanhaider.purdue@...> wrote:

In addition to all the different glitches and bugs that everyone is
experiencing with the half-screen/standard size keyboard and reporting
here, I personally just find the full screen keyboard (or, the almost
full screen mode in my case since I use that due to experiencing
crashes in Whatsapp when using full screen only) just more convenient
and favorable to me. The issue that I encounter is, frequently
touching a point outside of the keyboard area, when attempting to
type, which throws me off. When I get back into the keyboard area, I
obviously can't delete the last word that I typed for instance, as
that text has already been entered into the field by that point. This
is something that I have always been afraid of (for me personally
anyway), considering how Flicktype works and the text is committed as
soon as one touches any area outside of the keyboard area. so I have
generally favored the full screen option more.
Add all the different bugs that are there at this time, and getting
things to work consistently becomes, like Benny said, a nightmare.
I definitely prefer the full-screen option for myself personally and
will be continuing to use that for now, and maybe even permanently.
Not at all against having the half screen option being developed and
available, but the full-screen option just works better for my typing
habits.

Salman

On 8/30/18, FlickType <@FlickType> wrote:
Thanks Chuck. From what I can tell, the cursor is actually moved by line as
expected, but FlickType only announces a single word. This is similar to
another issue covered earlier, and should be fixed soon.

As you all play more with it, I'd love to get a better sense of two things:
One, how close is the half screen mode to becoming more useful than the full
screen one, to the extent that you would use half screen more often than
full screen? Two, out of all issues so far, what is the biggest priority to
fix with the half screen as it stands today?

Thanks,
Kosta




Re: Build 159

Chuck Dean
 

Hello,
This is the reason kosta is developing a toggle for the full and half screen keyboard. For example: once you enter the recipients and subject into an email's field you can activate the message body, toggle to the full screen keyboard, and type the body without worrying about going outside the keyboard area.

don't give up yet, good things may be coming.😎
Chuck

On Aug 30, 2018, at 5:53 PM, Salman Haider <salmanhaider.purdue@...> wrote:

In addition to all the different glitches and bugs that everyone is
experiencing with the half-screen/standard size keyboard and reporting
here, I personally just find the full screen keyboard (or, the almost
full screen mode in my case since I use that due to experiencing
crashes in Whatsapp when using full screen only) just more convenient
and favorable to me. The issue that I encounter is, frequently
touching a point outside of the keyboard area, when attempting to
type, which throws me off. When I get back into the keyboard area, I
obviously can't delete the last word that I typed for instance, as
that text has already been entered into the field by that point. This
is something that I have always been afraid of (for me personally
anyway), considering how Flicktype works and the text is committed as
soon as one touches any area outside of the keyboard area. so I have
generally favored the full screen option more.
Add all the different bugs that are there at this time, and getting
things to work consistently becomes, like Benny said, a nightmare.
I definitely prefer the full-screen option for myself personally and
will be continuing to use that for now, and maybe even permanently.
Not at all against having the half screen option being developed and
available, but the full-screen option just works better for my typing
habits.

Salman

On 8/30/18, FlickType <@FlickType> wrote:
Thanks Chuck. From what I can tell, the cursor is actually moved by line as
expected, but FlickType only announces a single word. This is similar to
another issue covered earlier, and should be fixed soon.

As you all play more with it, I'd love to get a better sense of two things:
One, how close is the half screen mode to becoming more useful than the full
screen one, to the extent that you would use half screen more often than
full screen? Two, out of all issues so far, what is the biggest priority to
fix with the half screen as it stands today?

Thanks,
Kosta




Re: Build 159

Salman Haider
 

In addition to all the different glitches and bugs that everyone is
experiencing with the half-screen/standard size keyboard and reporting
here, I personally just find the full screen keyboard (or, the almost
full screen mode in my case since I use that due to experiencing
crashes in Whatsapp when using full screen only) just more convenient
and favorable to me. The issue that I encounter is, frequently
touching a point outside of the keyboard area, when attempting to
type, which throws me off. When I get back into the keyboard area, I
obviously can't delete the last word that I typed for instance, as
that text has already been entered into the field by that point. This
is something that I have always been afraid of (for me personally
anyway), considering how Flicktype works and the text is committed as
soon as one touches any area outside of the keyboard area. so I have
generally favored the full screen option more.
Add all the different bugs that are there at this time, and getting
things to work consistently becomes, like Benny said, a nightmare.
I definitely prefer the full-screen option for myself personally and
will be continuing to use that for now, and maybe even permanently.
Not at all against having the half screen option being developed and
available, but the full-screen option just works better for my typing
habits.

Salman

On 8/30/18, FlickType <@FlickType> wrote:
Thanks Chuck. From what I can tell, the cursor is actually moved by line as
expected, but FlickType only announces a single word. This is similar to
another issue covered earlier, and should be fixed soon.

As you all play more with it, I'd love to get a better sense of two things:
One, how close is the half screen mode to becoming more useful than the full
screen one, to the extent that you would use half screen more often than
full screen? Two, out of all issues so far, what is the biggest priority to
fix with the half screen as it stands today?

Thanks,
Kosta



Re: Build 159

Benny Barber
 

I'll be honest. Working with the half screen is virtually impossible for me. After typing and trying to interact with the app at the top of the screen is a nightmare to me. The cursor behaves wildly. Sometimes I hear empty line. Sometimes I can't locate where I'm at. Occasionally FlickType crashes. The full screen is much more usable. At this point I will be using the full screen. Sorry. Thanks.
Benny

On Aug 30, 2018, at 4:58 PM, FlickType <@FlickType> wrote:

Build 160 is out, keeping this in the same thread.

What’s new:
- Disabled initial cursor position announcements. This should fix a few incorrect announcement issues when moving the cursor.
- Added "Standard" keyboard height option, which is slightly larger than the system keyboard. There is a known issue with this option not working correctly within the container app on iPhone X.

Thank you for the continued feedback. A gesture to change keyboard height on the fly is coming soon. Glad you like the visual announcements, Chuck. I was pretty excited when I was initially implementing it ☺️

Kosta

On Aug 30, 2018, at 13:46, Chuck Dean <cadean329@...> wrote:

Btw,
I would like to see a toggle between the full and ½ screen keyboard, so when I am typing longer text I would be able to see the visual announcement. The two finger swipe up and down would work great for me.

Its funny, when you brought out the visual announcement feature, I couldn't imagine myself ever using them... now I depend on them.
chuck


On Aug 30, 2018, at 1:22 PM, FlickType <@FlickType> wrote:

Thanks Chuck. From what I can tell, the cursor is actually moved by line as expected, but FlickType only announces a single word. This is similar to another issue covered earlier, and should be fixed soon.

As you all play more with it, I'd love to get a better sense of two things: One, how close is the half screen mode to becoming more useful than the full screen one, to the extent that you would use half screen more often than full screen? Two, out of all issues so far, what is the biggest priority to fix with the half screen as it stands today?

Thanks,
Kosta




Re: Build 159

Chuck Dean
 

Hi kosta, ignore that last email. I toggled VoiceOver off then on and both lags were cured.😎
Chuck

On Aug 30, 2018, at 3:34 PM, Chuck Dean <cadean329@...> wrote:

This is better.
I like the standard size keyboard, and the corrected cursor announcements.
I have tried this in my journal app and replying to this email... The two most troublesome areas for the flicktype ½ screen keyboard and it is running well.👍



On Aug 30, 2018, at 2:58 PM, FlickType <@FlickType> wrote:

Build 160 is out, keeping this in the same thread.

What’s new:
- Disabled initial cursor position announcements. This should fix a few incorrect announcement issues when moving the cursor.
- Added "Standard" keyboard height option, which is slightly larger than the system keyboard. There is a known issue with this option not working correctly within the container app on iPhone X.

Thank you for the continued feedback. A gesture to change keyboard height on the fly is coming soon. Glad you like the visual announcements, Chuck. I was pretty excited when I was initially implementing it ☺️

Kosta

On Aug 30, 2018, at 13:46, Chuck Dean <cadean329@...> wrote:

Btw,
I would like to see a toggle between the full and ½ screen keyboard, so when I am typing longer text I would be able to see the visual announcement. The two finger swipe up and down would work great for me.

Its funny, when you brought out the visual announcement feature, I couldn't imagine myself ever using them... now I depend on them.
chuck


On Aug 30, 2018, at 1:22 PM, FlickType <@FlickType> wrote:

Thanks Chuck. From what I can tell, the cursor is actually moved by line as expected, but FlickType only announces a single word. This is similar to another issue covered earlier, and should be fixed soon.

As you all play more with it, I'd love to get a better sense of two things: One, how close is the half screen mode to becoming more useful than the full screen one, to the extent that you would use half screen more often than full screen? Two, out of all issues so far, what is the biggest priority to fix with the half screen as it stands today?

Thanks,
Kosta




Good work!😎
Chuck

Re: Build 159

Chuck Dean
 

Hi kosta,
Two things I notice with build 160.
When manually typing there is a long lag between the tap and voice announcement, and there is also a lag when inserting Punctuation.
Chuck

On Aug 30, 2018, at 3:34 PM, Chuck Dean <cadean329@...> wrote:

This is better.
I like the standard size keyboard, and the corrected cursor announcements.
I have tried this in my journal app and replying to this email... The two most troublesome areas for the flicktype ½ screen keyboard and it is running well.👍



On Aug 30, 2018, at 2:58 PM, FlickType <@FlickType> wrote:

Build 160 is out, keeping this in the same thread.

What’s new:
- Disabled initial cursor position announcements. This should fix a few incorrect announcement issues when moving the cursor.
- Added "Standard" keyboard height option, which is slightly larger than the system keyboard. There is a known issue with this option not working correctly within the container app on iPhone X.

Thank you for the continued feedback. A gesture to change keyboard height on the fly is coming soon. Glad you like the visual announcements, Chuck. I was pretty excited when I was initially implementing it ☺️

Kosta

On Aug 30, 2018, at 13:46, Chuck Dean <cadean329@...> wrote:

Btw,
I would like to see a toggle between the full and ½ screen keyboard, so when I am typing longer text I would be able to see the visual announcement. The two finger swipe up and down would work great for me.

Its funny, when you brought out the visual announcement feature, I couldn't imagine myself ever using them... now I depend on them.
chuck


On Aug 30, 2018, at 1:22 PM, FlickType <@FlickType> wrote:

Thanks Chuck. From what I can tell, the cursor is actually moved by line as expected, but FlickType only announces a single word. This is similar to another issue covered earlier, and should be fixed soon.

As you all play more with it, I'd love to get a better sense of two things: One, how close is the half screen mode to becoming more useful than the full screen one, to the extent that you would use half screen more often than full screen? Two, out of all issues so far, what is the biggest priority to fix with the half screen as it stands today?

Thanks,
Kosta




Good work!😎
Chuck

Re: Build 159

George Cham
 

I also like the standed keyboard. When I was testing the almost full screen keyboard, I can see a. But VoiceOver says space.

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: 32111130400n behalf of
Sent: Friday, August 31, 2018 8:34 am
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 159
 
This is better.
I like the standard size keyboard, and the corrected cursor announcements.
I have tried this in my journal app and replying to this email... The two most troublesome areas for the flicktype ½ screen keyboard and it is running well.👍



> On Aug 30, 2018, at 2:58 PM, FlickType <hello@...> wrote:
>
> Build 160 is out, keeping this in the same thread.
>
> What’s new:
> - Disabled initial cursor position announcements. This should fix a few incorrect announcement issues when moving the cursor.
> - Added "Standard" keyboard height option, which is slightly larger than the system keyboard. There is a known issue with this option not working correctly within the container app on iPhone X.
>
> Thank you for the continued feedback. A gesture to change keyboard height on the fly is coming soon. Glad you like the visual announcements, Chuck. I was pretty excited when I was initially implementing it ☺️
>
> Kosta
>
>> On Aug 30, 2018, at 13:46, Chuck Dean <cadean329@...> wrote:
>>
>> Btw,
>> I would like to see a toggle between the full and ½ screen keyboard, so when I am typing longer text I would be able to see the visual announcement. The two finger swipe up and down would work great for me.
>>
>> Its funny, when you brought out the visual announcement feature, I couldn't imagine myself ever using them... now I depend on them.
>> chuck
>>
>>
>>> On Aug 30, 2018, at 1:22 PM, FlickType <hello@...> wrote:
>>>
>>> Thanks Chuck. From what I can tell, the cursor is actually moved by line as expected, but FlickType only announces a single word. This is similar to another issue covered earlier, and should be fixed soon.
>>>
>>> As you all play more with it, I'd love to get a better sense of two things: One, how close is the half screen mode to becoming more useful than the full screen one, to the extent that you would use half screen more often than full screen? Two, out of all issues so far, what is the biggest priority to fix with the half screen as it stands today?
>>>
>>> Thanks,
>>> Kosta
>>>
>>>
>>>
>>
>>
>>
>
>
>
Good work!😎
Chuck



Re: Build 159

Chuck Dean
 

This is better.
I like the standard size keyboard, and the corrected cursor announcements.
I have tried this in my journal app and replying to this email... The two most troublesome areas for the flicktype ½ screen keyboard and it is running well.👍



On Aug 30, 2018, at 2:58 PM, FlickType <@FlickType> wrote:

Build 160 is out, keeping this in the same thread.

What’s new:
- Disabled initial cursor position announcements. This should fix a few incorrect announcement issues when moving the cursor.
- Added "Standard" keyboard height option, which is slightly larger than the system keyboard. There is a known issue with this option not working correctly within the container app on iPhone X.

Thank you for the continued feedback. A gesture to change keyboard height on the fly is coming soon. Glad you like the visual announcements, Chuck. I was pretty excited when I was initially implementing it ☺️

Kosta

On Aug 30, 2018, at 13:46, Chuck Dean <cadean329@...> wrote:

Btw,
I would like to see a toggle between the full and ½ screen keyboard, so when I am typing longer text I would be able to see the visual announcement. The two finger swipe up and down would work great for me.

Its funny, when you brought out the visual announcement feature, I couldn't imagine myself ever using them... now I depend on them.
chuck


On Aug 30, 2018, at 1:22 PM, FlickType <@FlickType> wrote:

Thanks Chuck. From what I can tell, the cursor is actually moved by line as expected, but FlickType only announces a single word. This is similar to another issue covered earlier, and should be fixed soon.

As you all play more with it, I'd love to get a better sense of two things: One, how close is the half screen mode to becoming more useful than the full screen one, to the extent that you would use half screen more often than full screen? Two, out of all issues so far, what is the biggest priority to fix with the half screen as it stands today?

Thanks,
Kosta




Good work!😎
Chuck