Topics

Build 159

 

- Half screen stability improvements. A lot has changed under the hood, and we might need to iterate some more on this. Please test both full screen and half screen modes.
- Exposed a new "Multi-finger tap gestures" setting, on by default. Disable this if you are accidentally invoking the shift function when typing fast with multiple fingers.
- Added "Theme color" setting. Some low-vision users asked us for a splash of color. The default black background can now be a simple vertical gradient, starting from the top with the color of your choice, and ending in full black at the bottom. Let us know if any of the themes has any readability issues.

Chuck Dean
 

Hello Kosta,
I have tried both full and ½ screen modes and typing seems good.
I am trying this reply, which is where the ½ screen keyboard had the most problems for me... So far so good.👍

I notice that moving the cursor works best with the iOS rotor, which is fine by me.😎

It seems good to me, the only thing is the first word of a sentence is repeated once I start typing the second word. No big deal.
Chuck

On Aug 29, 2018, at 11:13 PM, FlickType <@FlickType> wrote:

- Half screen stability improvements. A lot has changed under the hood, and we might need to iterate some more on this. Please test both full screen and half screen modes.
- Exposed a new "Multi-finger tap gestures" setting, on by default. Disable this if you are accidentally invoking the shift function when typing fast with multiple fingers.
- Added "Theme color" setting. Some low-vision users asked us for a splash of color. The default black background can now be a simple vertical gradient, starting from the top with the color of your choice, and ending in full black at the bottom. Let us know if any of the themes has any readability issues.


David Nason
 

Hi Kosta and Ashley,

typing this in half scream mode, so far so good. The cursor is not moving around as it was before. So fingers crossed on that.
However I cannot seem to interact properly with the top half of the screen. I cannot move the cursor using the rotor for example.

when I swipe right a second time for a full stop, it is still saying "space". Although it looks like it is inserting the full stop.

In half screen mode, it is echoing entered characters even though I have that setting switched off.

I like the colour settings, though would like to have the option to switch off the gradient, and to choose the text colour as well.
That said, if half screen mode becomes solid, I'll be using that anyway.

The voice is too high pitched when reading the typed word. When I swipe down for other suggestions though those are fine. Again this is only in half screen mode.

Can you please explain what the new multi finger setting does?

Thanks,
Dave

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

Hello Kosta,
I have tried both full and ½ screen modes and typing seems good.
I am trying this reply, which is where the ½ screen keyboard had the most problems for me... So far so good.👍

I notice that moving the cursor works best with the iOS rotor, which is fine by me.😎

It seems good to me, the only thing is the first word of a sentence is repeated once I start typing the second word. No big deal.
Chuck

On Aug 29, 2018, at 11:13 PM, FlickType <@FlickType> wrote:

- Half screen stability improvements. A lot has changed under the hood, and we might need to iterate some more on this. Please test both full screen and half screen modes.
- Exposed a new "Multi-finger tap gestures" setting, on by default. Disable this if you are accidentally invoking the shift function when typing fast with multiple fingers.
- Added "Theme color" setting. Some low-vision users asked us for a splash of color. The default black background can now be a simple vertical gradient, starting from the top with the color of your choice, and ending in full black at the bottom. Let us know if any of the themes has any readability issues.



George Cham
 

Hi costa and Ashley,
I've tested the almost full screen and half screen options.
so far so good.


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 David Nason <dnason@...>
Sent: Thursday, August 30, 2018 7:08:14 PM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 159
 
Hi Kosta and Ashley,

typing this in half scream mode, so far so good. The cursor is not moving around as it was before. So fingers crossed on that.
However I cannot seem to interact properly with the top half of the screen. I cannot move the cursor using the rotor for example.

when I swipe right a second time for a full stop, it is still saying "space". Although it looks like it is inserting the full stop.

In half screen mode, it is echoing entered characters even though I have that setting switched off.

I like the colour settings, though would like to have the option to switch off the gradient, and to choose the text colour as well.
That said, if half screen mode becomes solid, I'll be using that anyway.

The voice is too high pitched when reading the typed word. When I swipe down for other suggestions though those are fine. Again this is only in half screen mode.

Can you please explain what the new multi finger setting does?

Thanks,
Dave
> On 30 Aug 2018, at 07:34, Chuck Dean <cadean329@...> wrote:
>
> Hello Kosta,
> I have tried both full and ½ screen modes and typing seems good.
> I am trying this reply, which is where the  ½ screen keyboard had the most problems for me... So far so good.👍
>
> I notice that moving the cursor works best with the iOS rotor, which is fine by me.😎
>
> It seems good to me, the only thing is the first word of a sentence is repeated once I start typing the second word. No big deal.
> Chuck
>
>> On Aug 29, 2018, at 11:13 PM, FlickType <hello@...> wrote:
>>
>> - Half screen stability improvements. A lot has changed under the hood, and we might need to iterate some more on this. Please test both full screen and half screen modes.
>> - Exposed a new "Multi-finger tap gestures" setting, on by default. Disable this if you are accidentally invoking the shift function when typing fast with multiple fingers.
>> - Added "Theme color" setting. Some low-vision users asked us for a splash of color. The default black background can now be a simple vertical gradient, starting from the top with the color of your choice, and ending in full black at the bottom. Let us know if any of the themes has any readability issues.
>>
>>
>>
>
>
>



Chuck Dean
 

Hi Kosta, I have been using the ½ screen keyboard and have noticed the following glitches.
First, when double tapping in the text field to move the cursor to the beginning or end of the text, VoiceOver will say the first or last word instead of " beginning of document " or end of document ". This is a little confusing and not consistent with iOS.

Second, I can not flick line by line, only word by word.

Third, when I am flicking through the text word by word, the last word in a sentence is not always announced. If I flick past the end of the sentence a few words and then back, the last word will be announced... Sometimes.

Also, while trying to reply to a email, I could not access the sent . This only happened once, so far. Button While trying to get it to send, I lost the email. I am not sure what I did, and I am still looking for that email.

Otherwise, FlickType is typing well and I can interact with the top of the screen fairly well.😎

A little more work and this will be great.
Chuck

Chuck Dean
 

Hi kosta, I tried turning off multi finger gestures which did turn them off, but I tried typing words with a hard press to capitalize the word with no results. The first letter is announced but not typed.

I will never use this feature, but I thought you should know.
Chuck

David Nason
 

A new problem has just cropped up for me. 
FlickType is no longer spelling back words to me, even though I have the setting turned on. 

Dave 



On 30 Aug 2018, at 10:37, George Cham <George.cham@...> wrote:

Hi costa and Ashley,
I've tested the almost full screen and half screen options.
so far so good.


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 David Nason <dnason@...>
Sent: Thursday, August 30, 2018 7:08:14 PM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 159
 
Hi Kosta and Ashley,

typing this in half scream mode, so far so good. The cursor is not moving around as it was before. So fingers crossed on that.
However I cannot seem to interact properly with the top half of the screen. I cannot move the cursor using the rotor for example.

when I swipe right a second time for a full stop, it is still saying "space". Although it looks like it is inserting the full stop.

In half screen mode, it is echoing entered characters even though I have that setting switched off.

I like the colour settings, though would like to have the option to switch off the gradient, and to choose the text colour as well.
That said, if half screen mode becomes solid, I'll be using that anyway.

The voice is too high pitched when reading the typed word. When I swipe down for other suggestions though those are fine. Again this is only in half screen mode.

Can you please explain what the new multi finger setting does?

Thanks,
Dave
> On 30 Aug 2018, at 07:34, Chuck Dean <cadean329@...> wrote:
>
> Hello Kosta,
> I have tried both full and ½ screen modes and typing seems good.
> I am trying this reply, which is where the  ½ screen keyboard had the most problems for me... So far so good.👍
>
> I notice that moving the cursor works best with the iOS rotor, which is fine by me.😎
>
> It seems good to me, the only thing is the first word of a sentence is repeated once I start typing the second word. No big deal.
> Chuck
>
>> On Aug 29, 2018, at 11:13 PM, FlickType <hello@...> wrote:
>>
>> - Half screen stability improvements. A lot has changed under the hood, and we might need to iterate some more on this. Please test both full screen and half screen modes.
>> - Exposed a new "Multi-finger tap gestures" setting, on by default. Disable this if you are accidentally invoking the shift function when typing fast with multiple fingers.
>> - Added "Theme color" setting. Some low-vision users asked us for a splash of color. The default black background can now be a simple vertical gradient, starting from the top with the color of your choice, and ending in full black at the bottom. Let us know if any of the themes has any readability issues.
>>
>>
>>
>
>
>



 

Thank you all for the helpful feedback, please keep it coming. When posting an issue, please include additional information such as full screen or half screen, iOS 11 or 12, and any iOS typing feedback settings when applicable. Below are my responses to all your points:

- The first word of the sentence being repeated once you start typing the next word. Chuck, is this with the half screen mode? And what are your iOS typing feedback settings and iOS version? Anyone else experiencing that?

- Cannot interact properly with the top half of the screen, for example move the cursor using the rotor. David, what exactly happens when you try that? Note that with half screen mode, any iOS system gesture such as the rotor needs to be performed entirely outside of the FlickType area, in other words it has to be done inside the application area. If one finger is in the application area and another finger is inside FlickType, the rotor gesture will not register.

- Hearing "space" when inserting a period is a known issue and should be fixed soon.

- The voice being too high pitched when reading the typed word: David, what are your iOS typing feedback settings and iOS version? Anyone else experiencing that?

- The new multi-finger setting only affects the two finger single tap to toggle shift. When disabled, that gesture will not trigger a shift change. I will rename the setting to something better. This is more of a bandaid fix for now.

- When double tapping in the text field to move the cursor to the beginning or end of the text, VoiceOver will say the first or last word instead of "beginning of document" or "end of document". This should be fixed soon.

- I can not flick line by line, only word by word. Do you mean using the 3-finger gesture on FlickType? There is a known issue where the cursor will actually move over entire sentences as expected, but only the punctuation marks will be announced.

- When flicking through the text word by word with the iOS gestures, the last word in a sentence is not always announced. This should be fixed soon.

- While trying to reply to a email, I could not access the send button, I lost the email. Chuck, can you please elaborate on not being able to access the send button? And was the email saved as a draft? With the half screen mode, you should not ever experience text loss since all text changes are instantly reflected in the application's text field.

- I tried turning off multi finger gestures which did turn them off, but I tried typing words with a hard press to capitalize the word with no results. The first letter is announced but not typed. Chuck, I was not able to reproduce this.

- FlickType is no longer spelling back words to me, even though I have the setting turned on. David, is this with the half screen mode? Does restarting your device seem to fix it?

Thanks,
Kosta

Chuck Dean
 

Hello kosta,
I I am using an iPhone 8, running iOS 11.4.1 i
All the glitches I have reported pertain to the ½ screen keyboard.

As for moving line by line, I was talking about using the iOS rotor, selecting line and flicking up and down. It only moves one word at a time
Chuck

On Aug 30, 2018, at 11:19 AM, FlickType <@FlickType> wrote:

Thank you all for the helpful feedback, please keep it coming. When posting an issue, please include additional information such as full screen or half screen, iOS 11 or 12, and any iOS typing feedback settings when applicable. Below are my responses to all your points:

- The first word of the sentence being repeated once you start typing the next word. Chuck, is this with the half screen mode? And what are your iOS typing feedback settings and iOS version? Anyone else experiencing that?

- Cannot interact properly with the top half of the screen, for example move the cursor using the rotor. David, what exactly happens when you try that? Note that with half screen mode, any iOS system gesture such as the rotor needs to be performed entirely outside of the FlickType area, in other words it has to be done inside the application area. If one finger is in the application area and another finger is inside FlickType, the rotor gesture will not register.

- Hearing "space" when inserting a period is a known issue and should be fixed soon.

- The voice being too high pitched when reading the typed word: David, what are your iOS typing feedback settings and iOS version? Anyone else experiencing that?

- The new multi-finger setting only affects the two finger single tap to toggle shift. When disabled, that gesture will not trigger a shift change. I will rename the setting to something better. This is more of a bandaid fix for now.

- When double tapping in the text field to move the cursor to the beginning or end of the text, VoiceOver will say the first or last word instead of "beginning of document" or "end of document". This should be fixed soon.

- I can not flick line by line, only word by word. Do you mean using the 3-finger gesture on FlickType? There is a known issue where the cursor will actually move over entire sentences as expected, but only the punctuation marks will be announced.

- When flicking through the text word by word with the iOS gestures, the last word in a sentence is not always announced. This should be fixed soon.

- While trying to reply to a email, I could not access the send button, I lost the email. Chuck, can you please elaborate on not being able to access the send button? And was the email saved as a draft? With the half screen mode, you should not ever experience text loss since all text changes are instantly reflected in the application's text field.

- I tried turning off multi finger gestures which did turn them off, but I tried typing words with a hard press to capitalize the word with no results. The first letter is announced but not typed. Chuck, I was not able to reproduce this.

- FlickType is no longer spelling back words to me, even though I have the setting turned on. David, is this with the half screen mode? Does restarting your device seem to fix it?

Thanks,
Kosta


 

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

Ed Worrell
 

Hello Kosta,


I would love to see the size of the half screen keyboard decreased. I still feel that it's way to large to be affective. The rotor is hard to use with the current size. It would be a welcome improvement. Maybe another size option could be included that's smaller than the half screen option. If you fix the feedback options that everyone has reported it would be very close to a release I think.
As usual great job! 👍🏻

Ed

On Aug 30, 2018, at 2: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


Chuck Dean
 

Hi Kosta,
The present build is running well enough that I haven't gone back to the full screen keyboard since the release of 159. Once the cursor movement is predictable and the little voice glitches are taken care of, I think this ½ screen keyboard will be my default keyboard..
As it is right now, I have only reverted to the iOS keyboard in order to move the cursor.

Personally I have no problem with the current size of the ½ screen keyboard, but a smaller keyboard would be ok.

I think you're close to a release.😎.👍
Chuck

On Aug 30, 2018, at 1:29 PM, Ed Worrell via Groups.Io <ed.worrell=icloud.com@groups.io> wrote:

Hello Kosta,


I would love to see the size of the half screen keyboard decreased. I still feel that it's way to large to be affective. The rotor is hard to use with the current size. It would be a welcome improvement. Maybe another size option could be included that's smaller than the half screen option. If you fix the feedback options that everyone has reported it would be very close to a release I think.
As usual great job! 👍🏻

Ed
On Aug 30, 2018, at 2: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



Chuck Dean
 

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


 

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



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

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



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

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

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




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