Topics

Build 54


Chuck Dean
 

Build 54
Hello, the period is now announced. Thank you.
The custom keyboard seems sluggish to me and much less forgiving. I need to be much more accurate with my taps, especially with letters on periphery; for example, the w, p, l, and a. Perhaps this is my particular way of typing, but I am slower on the custom keyboard than the app.

Even though I have some vision I find that I do not look at the words appearing on the screen at all. My focus is on the key position, and since the letters are announced there is no need for eye balling. Personally, I'd rather be able to see the app I am typing in, so I look forward to the option of a half screen keyboard.
Keep up the good work!


Chuck


Chuck Dean
 

Build 54
Hello,
I tried the two and three finger flick right and left to move the cursor. This feature works great! I can review my typing and edit my mistakes; which are many... :)
Good job!


Chuck


Chuck Dean
 

Build 54
BTW, I like the white bars indicating the key rows, but they are a little too bright. Perhaps, in the future, we could have the option to change color of the bars. I


Chuck


Chuck Dean
 

Build 54
Hi Kosta,
This is not a priority request; but could the "delete taps " voice feedback be included in the app version of FlickType? I find it very helpful.

Also while your under the hood, a way to move the cursor, like in the custom keyboard would be great.
I know your concentration is on the custom keyboard, but I know myself, and I'll probably use the stand alone app... You can't teach an old dog new tricks. :)


Chuck


Paul Sutton
 

Hey, sorry if this has already been brought up but I haven't had chance to check other peoples feedback yet.
When using the system wide keyboard, I have noticed that sometimes when I am flicking through the list of suggestions the word that is being spoken stutters. Also in the stand alone app is becoming a little sluggish.
Keep up the good work,
Paul.


Chuck Dean
 

Build 54
Hi Kosta,
I noticed when I use the custom keyboard to reply to an email; the first letter in the reply is not capitalized.


Chuck


Chuck Dean
 

Build 54
Hi Kosta,
I tried replying to a few emails to myself, and on all of the replies, the first letter is never capitalized.

Also, in a previous email I asked if the delete taps could be incorporated in the app, I meant clear taps.
Thanks,


Chuck


George Cham
 

I have no problems with the first letter starting with a capital. However when I'm typing I'm not seen the letters appearing straightaway. There is seems to be a bit of a delay between typing and when the words appear on the screen. I'm not relying on the words on the screen, as I am using voice-over, but entering words is becoming more more difficult because I have to swipe down through a whole heap of suggestions even though I'm typing the words accurately. Still don't like the white background representing the two rows of keys.

Kind Regards,

George Cham


________________________________
From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Chuck Dean <cadean329@...>
Sent: Thursday, May 3, 2018 7:15:39 AM
To: Alpha
Subject: [FlickType-alpha] Build 54

Build 54
Hi Kosta,
I tried replying to a few emails to myself, and on all of the replies, the first letter is never capitalized.

Also, in a previous email I asked if the delete taps could be incorporated in the app, I meant clear taps.
Thanks,


Chuck


Chuck Dean
 

this only happens when I reply to an email... All other times are ok.

Chuck

On May 2, 2018, at 2:29 PM, George Cham <George.cham@...> wrote:

I have no problems with the first letter starting with a capital. However when I'm typing I'm not seen the letters appearing straightaway. There is seems to be a bit of a delay between typing and when the words appear on the screen. I'm not relying on the words on the screen, as I am using voice-over, but entering words is becoming more more difficult because I have to swipe down through a whole heap of suggestions even though I'm typing the words accurately. Still don't like the white background representing the two rows of keys.

Kind Regards,

George Cham


________________________________
From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Chuck Dean <cadean329@...>
Sent: Thursday, May 3, 2018 7:15:39 AM
To: Alpha
Subject: [FlickType-alpha] Build 54

Build 54
Hi Kosta,
I tried replying to a few emails to myself, and on all of the replies, the first letter is never capitalized.

Also, in a previous email I asked if the delete taps could be incorporated in the app, I meant clear taps.
Thanks,


Chuck






Chuck Dean
 

Build 54
Is anyone getting the memory warning! Dialogue when typing for long periods of time with the custom keyboard? I am getting this message about every third word. I had this problem last night and had to reboot the iPhone to get it to stop.


Chuck


Chuck Dean
 

Build 54
Hi Kosta,
I am using an iPhone 8 running iOS 11.3.1.
I find the memory warning!
Appears after typing on the custom keyboard for long periods of time, but I have never seen it in the stand alone App, which I have used for hours at a time.
Re-booting the iPhone seems to clear the problem until I type for another long period of time.
When the warning comes up, I can flick up and see the word I tried to type, until I keep typing, then the memory warning will appear and not go away.
I hope this makes sense,


Chuck


George Cham
 

Hi costa, I'm not seeing the memory warning, I'm running the latest version, of ios. I've also seen the letters change colours when typing or deleting. I'm typing this using the latest build. And I'm getting the hang of the two white bars between the. Top and bottom Rose. But as I type this, I’m using dictation now I have just received the memory warning, will send you a screenshot off list. Using iOS 11. Three with iPhone 8

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<https://aka.ms/qtex0l> for iOS
________________________________
From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Chuck Dean <cadean329@...>
Sent: Thursday, May 3, 2018 9:42:51 AM
To: Alpha
Subject: [FlickType-alpha] Build 54

Build 54
Hi Kosta,
I am using an iPhone 8 running iOS 11.3.1.
I find the memory warning!
Appears after typing on the custom keyboard for long periods of time, but I have never seen it in the stand alone App, which I have used for hours at a time.
Re-booting the iPhone seems to clear the problem until I type for another long period of time.
When the warning comes up, I can flick up and see the word I tried to type, until I keep typing, then the memory warning will appear and not go away.
I hope this makes sense,


Chuck


George Cham
 

Hi Coster, I’m also getting the memory warning on the iPad running the latest version of iOS.

Kind Regards,

George Cham


________________________________
From: George Cham <george.cham@...>
Sent: Thursday, May 3, 2018 10:11:13 AM
To: alpha@flicktype.groups.io; Alpha
Subject: Re: [FlickType-alpha] Build 54

Hi costa, I'm not seeing the memory warning, I'm running the latest version, of ios. I've also seen the letters change colours when typing or deleting. I'm typing this using the latest build. And I'm getting the hang of the two white bars between the. Top and bottom Rose. But as I type this, I’m using dictation now I have just received the memory warning, will send you a screenshot off list. Using iOS 11. Three with iPhone 8

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<https://aka.ms/qtex0l> for iOS
________________________________
From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Chuck Dean <cadean329@...>
Sent: Thursday, May 3, 2018 9:42:51 AM
To: Alpha
Subject: [FlickType-alpha] Build 54

Build 54
Hi Kosta,
I am using an iPhone 8 running iOS 11.3.1.
I find the memory warning!
Appears after typing on the custom keyboard for long periods of time, but I have never seen it in the stand alone App, which I have used for hours at a time.
Re-booting the iPhone seems to clear the problem until I type for another long period of time.
When the warning comes up, I can flick up and see the word I tried to type, until I keep typing, then the memory warning will appear and not go away.
I hope this makes sense,


Chuck


 

First, I'm running build 1.1.-54 on an iPhone 7 running iOS 11.3.1.

The issue I reported under version 53 with the first word spoken when
flicking right after entry sounding muddy or at a lower volume has been
resolved. I have to agree with Chuck that the custom keyboard seems sluggish
and less forgiving. The predictive engine seems more accurate and faster in
the original FlickType app or either my typing accuracy has declined with
the system wide keyboard. I'm not really paying any attention to the size of
the displayed characters but they are large enough that I can make them out
if need be. I just won't be using the visual aspects very often. My biggest
issue is that I'm still not getting all available punctuation when flicking
down after a period is entered. I get a comma but nothing else. And the
worse of it is that what I've typed also disappears after I get the nothing
punctuation. When I do a 2 or 3 finger swipe left, I hear beginning of
document. This punctuation snafu seems to be causing the lloss of what I've
previously typed. I've not heard of this from anyone else so maybe I'm an
unfortunate party of one.

Alan Lemly

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of Chuck Dean
Sent: Wednesday, May 02, 2018 11:40 AM
To: Alpha
Subject: [FlickType-alpha] Build 54

Build 54
Hello, the period is now announced. Thank you.
The custom keyboard seems sluggish to me and much less forgiving. I need to
be much more accurate with my taps, especially with letters on periphery;
for example, the w, p, l, and a. Perhaps this is my particular way of
typing, but I am slower on the custom keyboard than the app.

Even though I have some vision I find that I do not look at the words
appearing on the screen at all. My focus is on the key position, and since
the letters are announced there is no need for eye balling. Personally, I'd
rather be able to see the app I am typing in, so I look forward to the
option of a half screen keyboard.
Keep up the good work!


Chuck


 

I forgot to mention one other thing in my below post concerning issues with
build 1.1.-54. When composing text with the system wide keyboard, if I
receive a notification and touch the notification to clear it, the system
acts as if Voiceover is not on and the application associated with the
notification launches when I touch it. Anything I've typed is gone when I
return to the keyboard I guess because I have copy and clear on exit set in
the main app. I get this same behavior with the main app and I suppose it
must be due to FlickType taking over for Voiceover while it is active. Can
anything be done to prevent this behavior other than my turning off
notifications? And for those tempted to reply with a smarmy comment, I know
I can just not touch those notifications when they pop up during FlickType
composition.

It would also be nice if you could add the word FlickType to the dictionary
used by the system wide keyboard. I'm looking forward to inclusion of manual
entry and dictionary access to the system wide keyboard because I really
can't do much typing to thoroughly test it with those existing limitations.
I'm not pressing here because I know how hard y'all are working on this
project and I very much appreciate your efforts. I just believe full
disclosure is better than no communication.

Alan Lemly


First, I'm running build 1.1.-54 on an iPhone 7 running iOS 11.3.1.

The issue I reported under version 53 with the first word spoken when
flicking right after entry sounding muddy or at a lower volume has been
resolved. I have to agree with Chuck that the custom keyboard seems sluggish
and less forgiving. The predictive engine seems more accurate and faster in
the original FlickType app or either my typing accuracy has declined with
the system wide keyboard. I'm not really paying any attention to the size of
the displayed characters but they are large enough that I can make them out
if need be. I just won't be using the visual aspects very often. My biggest
issue is that I'm still not getting all available punctuation when flicking
down after a period is entered. I get a comma but nothing else. And the
worse of it is that what I've typed also disappears after I get the nothing
punctuation. When I do a 2 or 3 finger swipe left, I hear beginning of
document. This punctuation snafu seems to be causing the lloss of what I've
previously typed. I've not heard of this from anyone else so maybe I'm an
unfortunate party of one.

Alan Lemly

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of Chuck Dean
Sent: Wednesday, May 02, 2018 11:40 AM
To: Alpha
Subject: [FlickType-alpha] Build 54

Build 54
Hello, the period is now announced. Thank you.
The custom keyboard seems sluggish to me and much less forgiving. I need to
be much more accurate with my taps, especially with letters on periphery;
for example, the w, p, l, and a. Perhaps this is my particular way of
typing, but I am slower on the custom keyboard than the app.

Even though I have some vision I find that I do not look at the words
appearing on the screen at all. My focus is on the key position, and since
the letters are announced there is no need for eye balling. Personally, I'd
rather be able to see the app I am typing in, so I look forward to the
option of a half screen keyboard.
Keep up the good work!


Chuck


George Cham
 

Hi, just received a test flight notification about build54 .
No update there.

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<https://aka.ms/qtex0l> for iOS


 

Hi George,

I am just about to send out a new build, number 55, but I have no idea why you are getting a notification before I actually send it. What does the notification say exactly, and did anyone else get one already?

- Kosta


Chuck Dean
 

Hello,
I got the same email just a few minutes ago. It seems like all the emails from TestFlight, about 24 hours late.

Chuck

On May 3, 2018, at 10:26 PM, FlickType <@FlickType> wrote:

Hi George,

I am just about to send out a new build, number 55, but I have no idea why you are getting a notification before I actually send it. What does the notification say exactly, and did anyone else get one already?

- Kosta