Whenever you go back to edit existing text, FlickType doesn’t know the entire text because iOS only supplies us with about a sentence or so from where the cursor happens to be. So if you go back to the iOS keyboard and then switch back to FlickType, you will likely only have one or two sentences available to edit and read back, even though the entire text should be in the text field. This may also happen if you remain on FlickType but switch apps.
toggle quoted messageShow quoted text
Hope that makes sense.
On May 28, 2018, at 11:34, Benny Barber <firstname.lastname@example.org> wrote:
Yeah, that is what must be happening to me. Thanks.
On May 28, 2018, at 1:26 PM, Chuck Dean <email@example.com> wrote:
I notice if I am typing, and leave the keyboard for a while, then continue typing, the three finger hold will only read from the point I started typing again.
On May 28, 2018, at 10:30 AM, Benny Barber <firstname.lastname@example.org> wrote:
Also in regards to the 3 finger tap and hold read back, the entire text is not read back sometimes. Thanks.
On May 28, 2018, at 11:54 AM, Chanelle Allen <email@example.com> wrote:
I don't want a physical spacebar either. I like the idea of adding it to the punctuation selection options though. I have also noticed the bug where deleting a character entered manually with FlickType results in incorrect read back. The character that was corrected and the rest of the word are read but not the whole word.
From: firstname.lastname@example.org [mailto:email@example.com] On Behalf Of David Nason
Sent: Monday, May 28, 2018 11:39
Subject: Re: [FlickType-alpha] Build 72
Good point. I would generally want a space between the last word and the emoji.
However, if typing multiple emoji, I would not necessarily want a space between each of them. So perhaps the manual space option is better than the automatic one. I do not want a space bar though.
On 28 May 2018, at 17:17, Benny Barber <firstname.lastname@example.org> wrote:
On May 28, 2018, at 11:12 AM, Ed Worrell <email@example.com> wrote:
The other option is to have the keyboard place a space before the emoji.
This might be much simpler for the end user.
On May 28, 2018, at 10:09 AM, Benny Barber <firstname.lastname@example.org> wrote:
Since we don't have a space bar, maybe Kosta could put a space option on the list of punctuation, where the emojis are at the top of the list. The space could be below punctuation options. Thanks.
On May 28, 2018, at 10:52 AM, Paul Sutton <email@example.com> wrote:
Benny is correct, you are unable to insert a space between the last word that you wrote and an emoji.
On 28 May 2018, at 16:45, Ed Worrell <firstname.lastname@example.org> wrote:
The secret to entering an emoji is to flick right to space, then a second space for punctuation. Instead it of flicking down to change the punctuation, you will now flick up and there will be about 5 or 6 emoji characters.
I hope this helps,
On May 28, 2018, at 9:38 AM, Benny Barber <email@example.com> wrote:
When typing in FlickType mode, I was trying to space after a word and then enter an emoji, but I could not figure out a way to put a space between the last word and the emoji🤔. See the example that I just typed. Thanks.
On May 28, 2018, at 10:08 AM, Ed Worrell <firstname.lastname@example.org> wrote:
A flick right enters a space after a word is typed. In manual entry mode you cab enter as many spaces as you would like, but again I think this is only after typing a word as well. I thought there was mention of the spacebar in manual typing mode, but I can't seem to get that to show up. Maybe it has been removed to unify the gestures accross input modes.
On May 28, 2018, at 8:57 AM, Benny Barber <email@example.com> wrote:
Actually I don't want a new line, but just a space. Thanks.
On May 28, 2018, at 9:50 AM, Ed Worrell <firstname.lastname@example.org> wrote:
Yes there is. The enter or return key at the bottom right corner of the keyboard will insert a new line.
I hope this helps.
On May 28, 2018, at 4:58 AM, Benny Barber <email@example.com> wrote:
Is there a way to enter a manual space in the custom keyboard? Thanks.
On May 27, 2018, at 1:51 AM, FlickType <firstname.lastname@example.org> wrote:
- Added a "Next Keyboard" button for those having trouble with the flick up & hold gesture. If you don't need the button, you can disable it from the main app settings.
- Also added a setting for a "Dismiss" button similar to the above, but this one is off by default since most people didn't seem to have trouble with the flick down & hold gesture. If you do have trouble performing that gesture, you can enable this button from the settings.
- The shift state now resets after entering a single character, so it behaves more like a shift key rather than a caps lock.
- The shift state now affects words that were not manually typed, meaning that if you switch to uppercase in the middle of a sentence and type a word like "banana", it will be capitalized.
- Words will be capitalized after a new line.
- On devices that support 3D Touch, pressing down harder while exploring the keyboard will toggle the secondary layout, meaning the state of shift if you are in letters, or switch between numbers and symbols if you are in either numbers or symbols.