On Nov 6, 2018, at 5:13 PM, FlickType <hello@flicktype.com> wrote:

‪Please excuse us if we take longer than usual to respond, our newest family member just arrived: 👶☺️‬

Kosta and Ashley

On Nov 6, 2018, at 3:13 PM, FlickType <hello@flicktype.com> wrote:

‪Please excuse us if we take longer than usual to respond, our newest family member just arrived: 👶☺️‬

Kosta and Ashley

On 6 Nov 2018, at 22:13, FlickType <hello@flicktype.com> wrote:

‪Please excuse us if we take longer than usual to respond, our newest family member just arrived: 👶☺️‬

Kosta and Ashley

On 6 Nov 2018, at 22:13, FlickType <hello@flicktype.com> wrote:

‪Please excuse us if we take longer than usual to respond, our newest family member just arrived: 👶☺️‬

Kosta and Ashley

On 6 Nov 2018, at 22:13, FlickType <hello@flicktype.com> wrote:

‪Please excuse us if we take longer than usual to respond, our newest family member just arrived: 👶☺️‬

Kosta and Ashley

‪Please excuse us if we take longer than usual to respond, our newest family member just arrived: 👶☺️‬

Kosta and Ashley

On Nov 6, 2018, at 3:13 PM, FlickType <hello@flicktype.com> wrote:

‪Please excuse us if we take longer than usual to respond, our newest family member just arrived: 👶☺️‬

Kosta and Ashley

On Nov 6, 2018, at 14:13, FlickType <hello@flicktype.com> wrote:

‪Please excuse us if we take longer than usual to respond, our newest family member just arrived: 👶☺️‬

Kosta and Ashley

‪Please excuse us if we take longer than usual to respond, our newest family member just arrived: 👶☺️‬

Kosta and Ashley

On Nov 6, 2018, at 5:13 PM, FlickType <hello@flicktype.com> wrote:

‪Please excuse us if we take longer than usual to respond, our newest family member just arrived: 👶☺️‬

Kosta and Ashley

On Nov 6, 2018, at 2:13 PM, FlickType <hello@flicktype.com> wrote:

‪Please excuse us if we take longer than usual to respond, our newest family member just arrived: 👶☺️‬

Kosta and Ashley

On Nov 6, 2018, at 4:13 PM, FlickType <hello@flicktype.com> wrote:

‪Please excuse us if we take longer than usual to respond, our newest family member just arrived: 👶☺️‬

Kosta and Ashley

On 27 Oct 2018, at 20:05, Alan Lemly <walemly@gmail.com> wrote:


Hi Ashley,

I've determined that after I installed this latest FlickType release, my settings were changed from full screen to half screen mode. After I changed them back to full screen mode, the keyboard is once again behaving as I like without the change to the compact voice or the issue not speaking the period at the end of a sentence. The single finger swipe up and hold to switch keyboards also seems to be working correctly so maybe that was a one time issue for me or we also won't rule out operator error.

Thanks so much for your reply and I'll report any other issues I come across as I continue to update the keyboard.

Alan Lemly

On Oct 27, 2018, at 12:20 PM, FlickType <hello@flicktype.com> wrote:

Hi Alan,

Thanks for reporting and sorry about the issues. We were able to reproduce the voice issue and the period issue. I think it may be related to the voice feedback setting that we recently made some changes to. Kosta will look into this when he gets back from a tech talk at our local low vision center, though it could take a couple days to get through Apple review and into the App Store. As for the 3rd issue with dismissing the keyboard, I am unable to reproduce this issue. Are you using the system keyboard? Does this happen in a specific app? What size keyboard are you using?

Thanks!
Ashley

On Sat, Oct 27, 2018 at 07:43 AM, Alan Lemly wrote:


2. When I swipe again to place a period after the last word in a sentence,
the last word is spoken again as opposed to period being spoken.

On Oct 27, 2018, at 12:20 PM, FlickType <hello@flicktype.com> wrote:

Hi Alan,

Thanks for reporting and sorry about the issues. We were able to reproduce the voice issue and the period issue. I think it may be related to the voice feedback setting that we recently made some changes to. Kosta will look into this when he gets back from a tech talk at our local low vision center, though it could take a couple days to get through Apple review and into the App Store. As for the 3rd issue with dismissing the keyboard, I am unable to reproduce this issue. Are you using the system keyboard? Does this happen in a specific app? What size keyboard are you using?

Thanks!
Ashley

On Sat, Oct 27, 2018 at 07:43 AM, Alan Lemly wrote:


2. When I swipe again to place a period after the last word in a sentence,
the last word is spoken again as opposed to period being spoken.

2.  When I swipe again to place a period after the last word in a sentence,
the last word is spoken again as opposed to period being spoken.

When you type out a plain text email such as the FlickType beta emails, all
works perfectly, but if I reply to an email that was sent in html i.e. has the
footer logo present, fancy fonts, etc, then FlickType simply doesn't work,
types garbage, backspace doesn't work, says it is at the beginning of document
when it isn't, etc.
It is hard to figure out exactly what the list of bugs are, I think the fact
that it is not functional with rich text/html based emails is the key. I just
tested replying to an HTML based email using my gmail app and found that
typing was ok, but backspacing wouldn't delete all the typed text either, so
there certainly seems to be something up with HTML based emails.
Sorry I can't be more specific. If you don't find the issue, I will put out an
exact use case and send you the results.

On 25 Oct 2018, at 20:08, FlickType <hello@flicktype.com> wrote:

Not yet, but it's moving higher up the list and we should be getting to this soon!

Cheers!
Ashley

On Wed, Oct 24, 2018 at 08:46 PM, Daniel McGee wrote:


Hi, is there icloud dictionary sync across multiple devices yet in the latest
beta?