Re: Build 136
Thank you Benny and David, got the crash reports. Looking into it. - Kosta
|
|
Re: Build 136
Benny Barber
Kosta,
toggle quoted messageShow quoted text
I sent 3 reports to hello @flicktype. I have 2 more if you want them. Thanks. Benny
On Jul 10, 2018, at 10:36 AM, FlickType <hello@flicktype.com> wrote:
|
|
Re: Build 136
Thank you David and Benny. I have not yet received any crash logs. Could you please send me any flicktype logs you may have from the same day? Settings, privacy, analytics, analytics data.
toggle quoted messageShow quoted text
Thanks, Kosta
On Jul 10, 2018, at 08:26, Benny Barber <rebelben@bellsouth.net> wrote:
|
|
Re: Build 136
Benny Barber
Yes, having crashes due to using quotation marks. Thanks.
toggle quoted messageShow quoted text
Benny
On Jul 10, 2018, at 12:48 AM, FlickType <hello@flicktype.com> wrote:
|
|
Lost text in build 136
David Nason
Hi Kosta,
I have just lost all my text twice when trying to type a reply to the build 136 email, plus was doing some testing of the changes to spaces when using quotation marks at the same time. At about 14:04 and 14:07, having typed some text into the email body, I then performed a swipe up and hold to switch keyboard. FlickType made some kind of announcement I didn't quite catch, but FlickType stayed on screen. I then switched away from it successfully, only to find that all my text was gone. It seems that the changes to the quotation marks are causing the problem. I entered the above text and switched keyboard no problem, then I opened FlickType again within this sane email, typed a couple of sentences with quotation marks in them, did the switch keyboard gesture, and I got the crash and lost text again. Dave
|
|
Re: Build 136
Hi costa,
Still getting announcements when FlickType is launched.
I've also added 11 emoji in settings.
But only 10 are showing up after flicking up after a period.
The announcements are how to dismiss keyboard and how to select numbers.
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 FlickType <hello@...>
Sent: Tuesday, July 10, 2018 3:48:14 PM To: alpha@flicktype.groups.io Subject: [FlickType-alpha] Build 136 Please test the new quote and emoji spacing functionality and report any unexpected behavior, ideally with a small reproducible example.
What's new: - A space will now be inserted before the first typed emoji. No spaces will be inserted between consecutive emojis. - Unwanted spaces around quotes will now be stripped. - FlickType hint announcements have been limited to the first 3 times since launching the keyboard. This will reset whenever the keyboard is relaunched, which happens if you reboot your device, if you update FlickType, if FlickType crashed, or if full access is toggled in the settings. So while this won't prevent the hints entirely for those who really don't need them, it will silence them for the vast majority of the cases. Previously: - Touch typing: last-moment key changes right before touching up are now ignored, to avoid accidentally entering characters adjacent to the intended one. - Touch typing: character phonetic feedback will only be announced while exploring, but not once the character has been entered. - Setting for "Visual Announcements" will now persist between sessions, and is also available in the Settings screen. - Fixed settings screen appearing visually broken when accessibility values for "Large Text" are used. Thanks Harry! Thank you for testing FlickType! Warmly, Kosta and Ashley
|
|
Build 136
Please test the new quote and emoji spacing functionality and report any unexpected behavior, ideally with a small reproducible example.
What's new: - A space will now be inserted before the first typed emoji. No spaces will be inserted between consecutive emojis. - Unwanted spaces around quotes will now be stripped. - FlickType hint announcements have been limited to the first 3 times since launching the keyboard. This will reset whenever the keyboard is relaunched, which happens if you reboot your device, if you update FlickType, if FlickType crashed, or if full access is toggled in the settings. So while this won't prevent the hints entirely for those who really don't need them, it will silence them for the vast majority of the cases. Previously: - Touch typing: last-moment key changes right before touching up are now ignored, to avoid accidentally entering characters adjacent to the intended one. - Touch typing: character phonetic feedback will only be announced while exploring, but not once the character has been entered. - Setting for "Visual Announcements" will now persist between sessions, and is also available in the Settings screen. - Fixed settings screen appearing visually broken when accessibility values for "Large Text" are used. Thanks Harry! Thank you for testing FlickType! Warmly, Kosta and Ashley
|
|
Re: Build 135
Chuck Dean
Hello Kosta,
toggle quoted messageShow quoted text
The last line I typed was lost and replaced with a repeat of the first line. I have tried to duplicate this in the journal and notes app without success. I'll keep you informed if I see it happen again. Chuck
On Jul 9, 2018, at 5:24 PM, FlickType <hello@flicktype.com> wrote:
|
|
Re: Build 135
Ed Worrell
Hey kosta,
toggle quoted messageShow quoted text
The phonetics issue seems to be resolved.👍🏻 Using touch typing doesn't seem to have any more issues like erroneous letters. All seems to be fixed here too.👍🏻 One thing I would like to see though, it a space could be inserted after punctuation and before an emoji is used. I don't even know it this is possible... Thanks again for a great build, and I hope you are feeling better. Ed
On Jul 9, 2018, at 5:07 PM, FlickType <hello@flicktype.com> wrote:
|
|
Re: Build 135
Thank you Chuck. Does that mean you lost the text of the last line? Or did it become the first line instead? And is this reproducible?
toggle quoted messageShow quoted text
Thanks, Kosta
On Jul 9, 2018, at 16:28, Chuck Dean <cadean329@gmail.com> wrote:
|
|
Build 135
Chuck Dean
Hi kosta,
I was typing in my journal app and after I dismissed the keyboard, the last line of text was replaced with a repeat of the first line of text. I had this problem in previous builds. Thanks, Chuck
|
|
Build 135
- Disabled gesture to change keyboard height. We will revisit the non-fullscreen mode once some more foundational work is in place.
- Touch typing: Ignore last-moment key changes right before touching up, to avoid accidentally entering characters adjacent to the intended one. - Touch typing: Don't provide character phonetic feedback after the character has been entered. - Setting for "Visual Announcements" will now persist between sessions, and is also available in the Settings screen. - Fixed settings screen appearing visually broken when accessibility values for "Large Text" are used. Thanks Harry!
|
|
Re: Wishlist
Ed Worrell
Hey Chuck and Kosta,
toggle quoted messageShow quoted text
I agree. I would love to see full functionality added to the standard keyboard. I guess I really don’t understand the current implementation of the standard keyboard…I would really love to see it function just like the full screen version of the keyboard, minus the full screen part of coarse ☺️ Maybe a two finger swipe up could add the text to the field whilst using the standard mode of Flicktype. This would make the ability to see what you have typed with the keyboard using the voiceover rotor, and it would make the send button appear in the messages app… Just a thought that I had last night. Ed Worrell CEO’/Co-Founder: OverHere Consulting LLP “Bringing Technology into Sight” www.overhereconsulting.net
On Jul 8, 2018, at 10:45 PM, FlickType <hello@flicktype.com> wrote:
|
|
Re: Build 133
Benny Barber
Kosta,
toggle quoted messageShow quoted text
I want to reiterate that if we go back to the half screen of build 132, it does not work well in the native iOS mail app. It covers up the message body on the iPhone 5S. It may work well for others, but I have to try to scroll up to get to the message body. That is a difficult task with the 3 finger flick up in such a small area. I wanted to put in my 2 cents. Thanks. Get well soon. Benny
On Jul 7, 2018, at 1:57 AM, FlickType <hello@flicktype.com> wrote:
|
|
Re: Wishlist
Chuck Dean
Hello,
toggle quoted messageShow quoted text
My priority would be the ability to use text replacements, the half screen keyboard, and no intro announcements. Chuck
On Jul 7, 2018, at 5:48 PM, David Nason <dnason@gmail.com> wrote:
|
|
Re: Wishlist
This wishlist is really helpful, as we are looking to re-prioritize the various planned items. I've been sick for the last couple of days, but as soon as I'm feeling better we'll get back on track, smile.
Warmly, Kosta
|
|
Re: Wishlist
Rocco Fiorentino
I also agree, and think this list is a good place to start evaluating things for future releases, etc.
toggle quoted messageShow quoted text
On Jul 8, 2018, at 8:07 AM, Salman Haider <salmanhaider.purdue@gmail.com> wrote:
|
|
Re: Build 133
Chanelle Allen
Hello,
toggle quoted messageShow quoted text
I, also, do not understand the rationale behind having the half screen keyboard only support touch typing. I am not trying to be critical; maybe there is something I am just not understanding. I think that some of you have tried to explain, but I still don't get it. To me, it seems easier to just switch to the iOS keyboard or dismiss FlickType rather than toggling the half screen mode on since VoiceOver navigation is more consistent when FlickType goes away completely. Does this make sense? After typing some text, I flick three fingers down to bring up the half screen or standard mode. Quite often, FlickType reads back what I have written. Then, I place my finger far above where I think the keyboard should be. Problems arise after I have located the edit field where text has been entered and I attempt to use standard VoiceOver gestures to read by word or character. Sometimes, the process works flawlessly, whetting my eagerness to continue testing this new dimension of FlickType and exploring its potential. More often than not, as soon as I begin moving by a specified rotor setting, and the direction I flick my finger makes no difference, I hear the message " FlickType: Flick up with three fingers to switch to full screen mode." but, I just realized something as I have resumed writing the rest of this email. When using VoiceOver navigation, my finger continually needs to remain near the top of the screen. So, if flicking down to read by word, I cannot place my finger somewhere in the middle of the screen where it is more comfortable--even if I have already taken focus away from FlickType by touching the top of the screen. Before figuring out that I need to perform VoiceOver gestures near the top of the screen, sometimes, VoiceOver navigation functioned normally for two or three words/characters before the FlickType message was announced. The gesture for switching between half and full screen modes is great. If we call the half screen mode "standard mode" I wonder if people would confuse that with the way in which FlickType normally operates--that is, as a full screen keyboard. It's something to consider. I also would like to have an option in Settings to choose my default mode. I have never had vision and struggle with spatial orientation, but I think that testing FlickType's full functionality in the size of the iOS keyboard would be interesting. I need to determine the benefit of tap typing in a half screen mode versus dismissing FlickType altogether. As someone on list said, there could be certain situations where a half screen keyboard is more practical and others where a full screen is more appropriate. I am glad that Kosta is giving us different models to think about and explore. Chanelle
On Jul 7, 2018, at 12:05, Benny Barber <rebelben@bellsouth.net> wrote:
|
|
Re: Wishlist
Salman Haider
I would agree with all of what Dave has here.
toggle quoted messageShow quoted text
On Jul 7, 2018, at 8:48 PM, David Nason <dnason@gmail.com> wrote:
Hi all, Some people have been mentioning what they would like to see in terms of development. So I thought I'd send out my own wishlist. Larger dictionary. All too often I tap out relatively common words but find they are not in the dictionary, or not offered to me, so have to type it out manually. More variations / derivitives of words. For example the plural of many common nouns are not in the dictionary. And different tenses of verbs. For example, I try to type "subscribed". FlickType offers me "subscriber" as the first option, showing that I got the pattern right, but neither "subscribed" or "subscribes" appear in the suggestions list at all. Learn what I type. For example, I type my name, "Dave" regularly, signing emails etc. However it almost never offers me "Dave" as the first suggestion, usually offering "face" first, with "Dave" appearing somewhere in the list requiring me to swipe down. No matter how many times I have made this change, it still never offers me "Dave" first. Better accuracy of manual typing. It still sometimes selects the letter beside the one I wanted. Insert a space before the first emoji that comes after words or punctuation. I say this because I would want a space in that case, but I do not want a space between two emoji characters. Fix for issue with FlickType inserting spaces before or after quotation marks. Currently I have to go back through my text with the iOS keyboard to fix these. I'm not sure about this one because sometimes I get unwanted spaces and sometimes I don't, so maybe there is a trick to it, or maybe it behaves differently depending on whether the word inside the quotes was tapped or manually touch typed? Support for text expansion shortcuts. Preferably accessing the ones I've already created in iOS settings. Option to switch off the announcements when you open the keyboard. Related to this, the keyboard is sometimes slow to become responsive when opened. The half screen keyboard would be nice to see too, if full functionality could be added and we could fully interact with the elements of the app in the top half of the screen, but for me the above list would take priority. What do other people think? Dave
|
|
Re: Wishlist
Chuck Dean
Hello Dave,
toggle quoted messageShow quoted text
The only thing I can comment on is the quotation marks. It has been my experience when I manually type a word with quotation marks there is not a space between the last letter and the quotation mark, but if I am using tap typing, there will be a space between the last letter and the quotation mark. Chuck
On Jul 7, 2018, at 5:48 PM, David Nason <dnason@gmail.com> wrote:
|
|