Date   

Re: Build 80

Chanelle Allen
 

Hi Kosta and Ashley,
The new FlickType build is great! I like the simplified container app and how we are able to easily view and edit dictionary entries. The best thing of all for me is that my tap volume settings remain consistent in both the new app and keyboard. I am looking forward to playing around with the new app/build, but I am most excited about not having to hear my taps so loud! ๐Ÿ˜€ ๐Ÿ˜Ž to most people, this isn't a big deal, but their is some expression about the little things in life being worthwhile. Thank you very much. I wonder if their is a way to eliminate or reduce the volume of the clicks when manually typing. Is their a setting on my phone that I need to change?
Chanelle

On Jun 6, 2018, at 10:54, FlickType <@FlickType> wrote:

Please note: This update replaces the container app with an entirely new app, and some features are not yet implemented. If you need the old container app for any reason, you can always switch back to an older build from TestFlight.

What's new:
- Brand new container app which helps us set the right foundation for the future.
- The first tab is called "Type", and is where you can use the built-in keyboard to type something and then export it using the top right share button.
- The second tab is called "Settings", and currently has some, but not all, of the previous app options. Your settings from previous versions should carry over.
- The third tab is called "Dictionary", and gives you full control of all your dictionary entries. You can read, delete or insert new entries using familiar iOS controls. All your dictionary entries from previous versions should carry over.

Thank you for testing!
Kosta & Ashley



Build 80

Chuck Dean
 

Build 80

Hello,
Ok, I see what you are doing here, unifying the two keyboards.
Everything seems to be working ok, but I have a suggestion.
I assume the keyboard must be dismissed in order to access the control buttons at the top and the tabs at the bottom. I think the dismiss and next keyboard buttons should be turned on by default for those who have trouble with the flick and hold gesture.

Also the flick left and hold no longer does a rapid delete, and closing the App no longer does a copy and erase. Both of those features were huge, in my opinion, while using the App.

Btw I am using the App to type this.


Re: Build 80

Ed Worrell
 

Hello Kosta and Ashley,

This is awesome! The new container application simplifies things greatly. I love the new ability to add words to the dictionary. Great job!

On a bug note: I have been noticing that the flick up to add emojis and the flick up and hold to switch keyboards is kicking me back to the home screen as my iPhone X seems to think that I am performing the home gesture. I am about a1/2 inch from the bottom of the keyboard when I am typing. This behavior has gotten worse in the first build of iOS 12(Just FYI). I canโ€™t seem to get it to do this every time as of right now, it seems to be at random. This honestly could be human error as well. Just wanted to point out the issue.

Thanks again for all of the great work you two are doing.

Ed Worrell

On Jun 6, 2018, at 9:54 AM, FlickType <@FlickType> wrote:

Please note: This update replaces the container app with an entirely new app, and some features are not yet implemented. If you need the old container app for any reason, you can always switch back to an older build from TestFlight.

What's new:
- Brand new container app which helps us set the right foundation for the future.
- The first tab is called "Type", and is where you can use the built-in keyboard to type something and then export it using the top right share button.
- The second tab is called "Settings", and currently has some, but not all, of the previous app options. Your settings from previous versions should carry over.
- The third tab is called "Dictionary", and gives you full control of all your dictionary entries. You can read, delete or insert new entries using familiar iOS controls. All your dictionary entries from previous versions should carry over.

Thank you for testing!
Kosta & Ashley



Build 80

 

Please note: This update replaces the container app with an entirely new app, and some features are not yet implemented. If you need the old container app for any reason, you can always switch back to an older build from TestFlight.

What's new:
- Brand new container app which helps us set the right foundation for the future.
- The first tab is called "Type", and is where you can use the built-in keyboard to type something and then export it using the top right share button.
- The second tab is called "Settings", and currently has some, but not all, of the previous app options. Your settings from previous versions should carry over.
- The third tab is called "Dictionary", and gives you full control of all your dictionary entries. You can read, delete or insert new entries using familiar iOS controls. All your dictionary entries from previous versions should carry over.

Thank you for testing!
Kosta & Ashley


Sorry about OKing the email from Colton Hill

Chuck Dean
 

Hello Kosta, and everyone,
I am sorry about the email I approved from Colton Hill which has some profanity. I read the first paragraph, which seemed ok, but he snuck in a bunch of profanity later in the email. He was talking about the dictionary, but he didn't need to be so graphic.

I believe he did this on purpose, and if not removed, he should be monitored closely.

From now on, I will not approve any email without reading the complete text.


Re: Bild 75

Chuck Dean
 

The flick left works for me.
Perhaps in the future the announcements could be made to turn off after the keyboard has been used X amount of times.

On Jun 2, 2018, at 4:22 PM, Chanelle Allen <chanellem.allen@...> wrote:


Hello,
I agree that less feedback when FlickType starts would be nice. I will try flicking left to stop the initial message though.
Chanelle


On Jun 2, 2018, at 16:54, Ed Worrell <ed.worrell@...> wrote:

I actually agree. I would like to have the option for less feedback. Maybe when the keyboard is launched it could say FlickType ready. This would be much more welcome.

Ed
On Jun 2, 2018, at 2:45 AM, Paul Sutton <sutty_p@...> wrote:


Hi,
I just wondered if in a later release it would be possible to have an option to disable the VoiceOver hints when launching FlickType as it's a little distracting when I want to start typing straight away.
Kind regards, Paul.
On 29 May 2018, at 23:19, FlickType <@FlickType> wrote:

- Don't add a space when deleting manually entered characters.






Re: Bild 75

Chanelle Allen
 

Hello,
I agree that less feedback when FlickType starts would be nice. I will try flicking left to stop the initial message though.
Chanelle

On Jun 2, 2018, at 16:54, Ed Worrell <ed.worrell@...> wrote:

I actually agree. I would like to have the option for less feedback. Maybe when the keyboard is launched it could say FlickType ready. This would be much more welcome.

Ed
On Jun 2, 2018, at 2:45 AM, Paul Sutton <sutty_p@...> wrote:


Hi,
I just wondered if in a later release it would be possible to have an option to disable the VoiceOver hints when launching FlickType as it's a little distracting when I want to start typing straight away.
Kind regards, Paul.
On 29 May 2018, at 23:19, FlickType <@FlickType> wrote:

- Don't add a space when deleting manually entered characters.





Re: Bild 75

Ed Worrell
 

I actually agree. I would like to have the option for less feedback. Maybe when the keyboard is launched it could say FlickType ready. This would be much more welcome.

Ed

On Jun 2, 2018, at 2:45 AM, Paul Sutton <sutty_p@...> wrote:


Hi,
I just wondered if in a later release it would be possible to have an option to disable the VoiceOver hints when launching FlickType as it's a little distracting when I want to start typing straight away.
Kind regards, Paul.
On 29 May 2018, at 23:19, FlickType <@FlickType> wrote:

- Don't add a space when deleting manually entered characters.




Re: Bild 75

Salman Haider
 

I personally don't find them intrusive since they are interrupted right away when I switch to FlickType and begin typing.
One thing you could try is, once you have the FlickType keyboard up, simply do a quick swipe to the left. Which will result in VoiceOver announcing beginning of document. That can be used to interrupt the longer list of hints that you get. Also. You don't really have to wait until the entire list of hints is announced before you begin typing. You can very easily interrupt them by simply beginning to type and swipe.
Not something that bother's me personally. But just giving some suggestions for you to try, to interrupt the hints being spoken.

On Jun 2, 2018, at 4:45 AM, Paul Sutton <sutty_p@...> wrote:


Hi,
I just wondered if in a later release it would be possible to have an option to disable the VoiceOver hints when launching FlickType as it's a little distracting when I want to start typing straight away.
Kind regards, Paul.
On 29 May 2018, at 23:19, FlickType <@FlickType> wrote:

- Don't add a space when deleting manually entered characters.



Re: Bild 75

Paul Sutton
 

Hi,
I just wondered if in a later release it would be possible to have an option to disable the VoiceOver hints when launching FlickType as it's a little distracting when I want to start typing straight away.
Kind regards, Paul.

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

- Don't add a space when deleting manually entered characters.



Re: Unpredictable cursor

Ed Worrell
 

Hey Kosta,

I think you're correct. I seem to remember my business partner, whom is low vision and doesn't use VoiceOver seeing this behavior only on the iPad of which there is a dismiss keyboard button. Most people that don't use Voiceover never have a reason to dismiss the keyboard. This honestly has only happened a few times to me and isn't much of an actual problem as a minor annoyance.


Ed

On Jun 1, 2018, at 4:20 PM, FlickType <@FlickType> wrote:

It seems that dismissing the keyboard, any keyboard including the iOS one, will not preserve the cursor position but will instead move it at the beginning of the document the next time you double tap to edit that field. Please correct me if I'm wrong, but I think it's rare that people dismiss the iOS keyboard when using VoiceOver, hence the issue appears to be more prominent with FlickType even though it's not specific to FlickType. Sighted users will routinely move their finger downwards in order to scroll up and read earlier messages in an iMessage thread for example, the act of which slowly and interactively pushes the keyboard down to eventually be dismissed once it goes too low. But scrolling the message thread using VoiceOver will leave the keyboard up if it's visible. And FlickType has a dedicated button or gesture for dismissing it, whereas the iOS keyboard doesn't.

I've added this as a known issue in the wiki, and I'm not sure if there will ever be a workaround for that other than trying to move the cursor before editing the field, or moving the cursor with the VoiceOver gestures when FlickType has a half-screen mode.

Kosta



Re: Build 75 and manual punctuation

David Nason
 

Thanks Kosta.
Yes I think going back to letters would be the desired behaviour. Personally, I would not want any announcement though, I would find that distracting as you suggested.

Dave

On 1 Jun 2018, at 23:11, FlickType <@FlickType> wrote:

Thank you David.

When I was considering what to do with a short tap in the numbers or symbols layout, taking you back to letters seemed like a somewhat appropriate choice, as well as a very easy one technically. But I do think that the tap should count towards your typing of the next word, it was just a bit more complicated to implement so we'll address that soon. I assume this would be the desired behavior, please let us know if you or anyone else has any other ideas. Also one thing to consider is if we should announce the switch to letters, which while informative, could be a bit jarring or distracting if it feels like it's happening while you've started typing out a word - it might make you wonder if that first tap was registered, even if it was.

Thanks for the feedback, smile!

Kosta



Re: Unpredictable cursor

 

It seems that dismissing the keyboard, any keyboard including the iOS one, will not preserve the cursor position but will instead move it at the beginning of the document the next time you double tap to edit that field. Please correct me if I'm wrong, but I think it's rare that people dismiss the iOS keyboard when using VoiceOver, hence the issue appears to be more prominent with FlickType even though it's not specific to FlickType. Sighted users will routinely move their finger downwards in order to scroll up and read earlier messages in an iMessage thread for example, the act of which slowly and interactively pushes the keyboard down to eventually be dismissed once it goes too low. But scrolling the message thread using VoiceOver will leave the keyboard up if it's visible. And FlickType has a dedicated button or gesture for dismissing it, whereas the iOS keyboard doesn't.

I've added this as a known issue in the wiki, and I'm not sure if there will ever be a workaround for that other than trying to move the cursor before editing the field, or moving the cursor with the VoiceOver gestures when FlickType has a half-screen mode.

Kosta


Re: Build 75 and manual punctuation

 

Thank you David.

When I was considering what to do with a short tap in the numbers or symbols layout, taking you back to letters seemed like a somewhat appropriate choice, as well as a very easy one technically. But I do think that the tap should count towards your typing of the next word, it was just a bit more complicated to implement so we'll address that soon. I assume this would be the desired behavior, please let us know if you or anyone else has any other ideas. Also one thing to consider is if we should announce the switch to letters, which while informative, could be a bit jarring or distracting if it feels like it's happening while you've started typing out a word - it might make you wonder if that first tap was registered, even if it was.

Thanks for the feedback, smile!

Kosta


Re: Build 75 minor disappearinh text bug

 

Thank you David.

I did notice that sometime ago and it had since slipped my mind. We won't spend time on fixing this now, but if there's more reports of it we'll prioritize it accordingly. Thank you for the report.

On the issue of unwanted spaces, there are a lot of different situations and edge cases,. We can't simply not add spaces in the case of quotation marks, for example, because you do want a space after the closing mark, and it's not trivial to accurately guess if a mark is opening or closing the quotation. Anyone who experiences similar issues, please let us know here in the group so we can eventually get a good sense of what the most common problematic cases are with unwanted spaces, and we'll address the most common ones soon.

Kosta


Build 75 and manual punctuation

David Nason
 

Hi again,

I've noticed a minor irritation when entering punctuation manually.
After typing the punctuation character manually, my next tap is not registered. So I need to tap the screen once to bring the keyboard back to life.

Dave


Build 75 minor disappearinh text bug

David Nason
 

Hi Kosta and Ashley,

I've just discovered a disappearing text bug in build 75, though it's not particularly serious.
Steps to reproduce:
1. Ensure that " shake to undo " is switched on in settings. It can be found under General >Accessibility.
2. Open a text field and start typing using the FlickType custom keyboard.
3. Shake the phone to bring up the undo option.
4. Even if you select Cancel, the text you typed since most recently opening FlickType will be deleted.

Clearly not a deal breaker but I do occasionally envoke the shake to undo by accident.

Dave

PS. Above you can again see the issues with spaces with when using punctuation like quotes and brackets.


Unpredictable cursor

Chuck Dean
 

I just tried to duplicate it here but failed.
It seems to be prevalent in the notes app.
Hi Kosta,
This was mentioned a few days ago, but when I am typing in notes or email

The cursor sometimes goes to the beginning of the last line, instead of the end.

You will notice that the cursor went to the beginning of this email after I dismissed the keyboard the second time.
Not a deal breaker but, it makes typing unpredictable. Chuck


Re: Adding two letter words to the dictionary

 

Hi Nozi,

For now, you cannot add words that are less than 3 letters to the dictionary. We do this because when there are only 2 letters in a word there is less context for the autocorrect to figure out what you're trying to type and important two letter words get pushed down far on the list of suggestions. The fix to add the context and ranking of newly added words to the dictionary is on our list of future fixes, but this is very involved in will take many days to complete so we are not able to address it now, but we do have another possible solution that we hope to implement soon.

Thanks!
Ashley


Re: Build 75

Ed Worrell
 

Hello Kosta,

Thatโ€™s great to hear. Congrats on getting the build out to the rest of the testers. I hope that they are as happy with the first fully functioning build as I am. Words being manually entered to the keyboard seems like a great option. Will there be any way to remove words in the future? I know you can manually type the word in the app and then swipe up to remove it. Will we have a list of words that we can simply just remove a unwanted word? I am really enjoying the current build. I do have two requests and I believe that you have replied, but I am not sure:

1. Phonetics when manually typing a word.

2. The use of the return key as a jump to the next field in the mail program.

3. Use of the return key for search fields.

4. Quick delete function. I am really missing this feature from the original Fleksy app.

5. The ability to jump to the top or bottom of a text field. I know that we can navigate by lines. This would be nice as you can do this with the default VoiceOver commands. This is as simple as double tapping in the text field to jump to the top or bottom when using the default keyboard.

I know that I have mentioned these before. This list is arranged in the most important to the least important for me.


Other than these few things the keyboard is great.

Ed Worrell

On May 30, 2018, at 10:13 AM, FlickType <@FlickType> wrote:

Thank you Maria.

David, adding words to the dictionary will most likely be automatic and there will also be a way to view and edit all your custom entries from the main app.

FYI, build 75 was just released to the beta group, thank you all for helping us get a good release out the door! ๐Ÿ˜

Kosta