Date   

Re: Build 55

 

Thank you George. Can you please restart your device and see if that helps?


Re: Build 55

George Cham
 

just installed build 55 on iPhone 8 .Got the memory warning.

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 FlickType <hello@flicktype.com>
Sent: Friday, May 4, 2018 3:32:16 PM
To: alpha@flicktype.groups.io
Subject: [FlickType-alpha] Build 55

- Fixed audio latency. Hopefully it should now feel more like the main app, apart from the tap feedback delay. Please note: you must set VoiceOver typing feedback to "Nothing", otherwise the announcements will be laggy and sound like the voice has a cold and a stutter - no kidding. For some reason the iOS announcements are lower-quality as well as delayed, and because of the delay they almost immediately interrupt the FlickType announcements.
- You can now type your custom dictionary words, as well as some additional built-in words. You must run the main app once after updating for your words to carry over.
- Improved memory management. Hopefully you won't get those memory warnings any more, fingers crossed.
- First word in mail app should now be correctly capitalized.


Build 55

 

- Fixed audio latency. Hopefully it should now feel more like the main app, apart from the tap feedback delay. Please note: you must set VoiceOver typing feedback to "Nothing", otherwise the announcements will be laggy and sound like the voice has a cold and a stutter - no kidding. For some reason the iOS announcements are lower-quality as well as delayed, and because of the delay they almost immediately interrupt the FlickType announcements.
- You can now type your custom dictionary words, as well as some additional built-in words. You must run the main app once after updating for your words to carry over.
- Improved memory management. Hopefully you won't get those memory warnings any more, fingers crossed.
- First word in mail app should now be correctly capitalized.


Re: Build 54

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 <hello@flicktype.com> 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



Re: Build 54

 

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


Build 54

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


Re: Hey George...

George Cham
 

Hi chuck, no I have not. I prefer portrait. But will try it out.

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@gmail.com>
Sent: Friday, May 4, 2018 10:41:29 AM
To: alpha@flicktype.groups.io
Subject: [FlickType-alpha] Hey George...

Hi George,
I know you don't like the large letters displayed in the custom keyboard. Have you tried it in landscape mode? The words are much smaller; so small I cannot read them.
Happy typing!

Chuck

On May 2, 2018, at 7:25 PM, Chuck Dean <cadean329@gmail.com> wrote:

Lol that’s funny George, you really hate these letters don’t you?

Chuck

On May 2, 2018, at 6:57 PM, George Cham <George.cham@hotmail.com> wrote:

I'm wondering if the large text in this new build, is draining the memory in ios? In build50 this problem did not happen. If that's the case, then I would recommend going back to the previous layout.

Kind Regards,

George Cham


________________________________
From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Chuck Dean <cadean329@gmail.com>
Sent: Thursday, May 3, 2018 10:22:44 AM
To: Alpha
Subject: [FlickType-alpha] Memory warning!

Memory warning!
Hi Kosta, I tried typing an email from scratch, you can see the email titled an observation. After typing that amount of text, I had to reboot my iPhone because the Memory Warning! Would pop up about every third word.
I have done 5 reboot's today!


Chuck







Hey George...

Chuck Dean
 

Hi George,
I know you don't like the large letters displayed in the custom keyboard. Have you tried it in landscape mode? The words are much smaller; so small I cannot read them.
Happy typing!

Chuck

On May 2, 2018, at 7:25 PM, Chuck Dean <cadean329@gmail.com> wrote:

Lol that’s funny George, you really hate these letters don’t you?

Chuck

On May 2, 2018, at 6:57 PM, George Cham <George.cham@hotmail.com> wrote:

I'm wondering if the large text in this new build, is draining the memory in ios? In build50 this problem did not happen. If that's the case, then I would recommend going back to the previous layout.

Kind Regards,

George Cham


________________________________
From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Chuck Dean <cadean329@gmail.com>
Sent: Thursday, May 3, 2018 10:22:44 AM
To: Alpha
Subject: [FlickType-alpha] Memory warning!

Memory warning!
Hi Kosta, I tried typing an email from scratch, you can see the email titled an observation. After typing that amount of text, I had to reboot my iPhone because the Memory Warning! Would pop up about every third word.
I have done 5 reboot's today!


Chuck







Re: Build 54 clearing memory.

 

Hi Chuck,

I am hoping to send out a new build later today that hopefully will address that. I do not believe there's anything you can do in the meantime, sorry about that.

Also anyone who doesn't get feedback when moving the cursor sentence by sentence, I am investigating that but I'm not sure why it's happening yet.

- Kosta


Build 54 clearing memory.

Chuck Dean
 

Build 54 clearing memory.
Hello Kosta,
I red online that holding the power button down until the turn off phone screen appears, then holding the home button until the screen disappears and then reappears will clear the iPhone's RAM
Will this take care of the memory warning?
Thanks,


Chuck


Re: Responses

Paul Sutton
 

Hi Chuck, thanks for that. Yes, just tried it and you are indeed write. I can't believe that I didn't realise that, lol.

On 3 May 2018, at 22:53, Chuck Dean <cadean329@gmail.com> wrote:

hi Paul, you will hear clear taps when you type letters but do not flick right to enter the word. So if you are typing and make a mistake and flick left to delete the wrong letters you will hear clear taps. I hope this helps.

Chuck

On May 3, 2018, at 1:57 PM, Paul Sutton <sutty_p@hotmail.co.uk> wrote:

Hi, I have updated to the latest iOS software and the lag I was experiencing with the stand alone app has been resolved. However, in the system wide keyboard, every now and then when I am swiping left to delete a word voiceover will announce "clear tabs " or "clear taps " I can't tell which.
Paul.




Re: Build 54 memory warning

Chuck Dean
 

I forgot... Is there a way to clear the memory other than turning off and on the phone?

Chuck

On May 3, 2018, at 3:01 PM, Chuck Dean <cadean329@gmail.com> wrote:

Build 54 memory warning
Hi Kosta,
I just tried to use the system ride keyboard to reply to an email and I got the memory warning! After almost every letter.
I had not been using this keyboard hardly at all today, just for a couple of searches. I had been typing a lot on the stand alone App.
Could what I typed in the App also be filling the memory?
Thanks,


Chuck



Build 54 memory warning

Chuck Dean
 

Build 54 memory warning
Hi Kosta,
I just tried to use the system ride keyboard to reply to an email and I got the memory warning! After almost every letter.
I had not been using this keyboard hardly at all today, just for a couple of searches. I had been typing a lot on the stand alone App.
Could what I typed in the App also be filling the memory?
Thanks,


Chuck


Re: Usage thoughts...

David Nason
 

yes I followed the exact same path. I now believe I can get on board with the full screen keyboard, but it will be important to be able to quickly and seemlessly dismiss and re-invoke the keyboard, for example when engaged in a messaging conversation.
Still interested to see a half screen option tho.

Dave

On 3 May 2018, at 18:46, Chuck Dean <cadean329@gmail.com> wrote:

Hi Ed, I agree with you. I couldn't see how I would use the full screen keyboard, but now I understand... Considering I am using it right now to reply to this email.

Chuck

On May 3, 2018, at 10:39 AM, Ed Worrell <ed.worrell@icloud.com> wrote:

Hello,

I have been inserting flick type more and more into my everyday use. I actually am really starting to like the full screen keyboard idea. When we get the manual typing feature back, being able to insert a new line and see some of the keyboard lab reduced this will be an amazing keyboard. I still would love to see the half screen option. I now am not seeing it as crucial as I thought at the start of testing the keyboard extension.

Ed worrell




Re: Responses

Chuck Dean
 

hi Paul, you will hear clear taps when you type letters but do not flick right to enter the word. So if you are typing and make a mistake and flick left to delete the wrong letters you will hear clear taps. I hope this helps.

Chuck

On May 3, 2018, at 1:57 PM, Paul Sutton <sutty_p@hotmail.co.uk> wrote:

Hi, I have updated to the latest iOS software and the lag I was experiencing with the stand alone app has been resolved. However, in the system wide keyboard, every now and then when I am swiping left to delete a word voiceover will announce "clear tabs " or "clear taps " I can't tell which.
Paul.



Re: Responses

Paul Sutton
 

Hi, I have updated to the latest iOS software and the lag I was experiencing with the stand alone app has been resolved. However, in the system wide keyboard, every now and then when I am swiping left to delete a word voiceover will announce "clear tabs " or "clear taps " I can't tell which.
Paul.


Re: Usage thoughts...

Chuck Dean
 

Hi Ed, I agree with you. I couldn't see how I would use the full screen keyboard, but now I understand... Considering I am using it right now to reply to this email.

Chuck

On May 3, 2018, at 10:39 AM, Ed Worrell <ed.worrell@icloud.com> wrote:

Hello,

I have been inserting flick type more and more into my everyday use. I actually am really starting to like the full screen keyboard idea. When we get the manual typing feature back, being able to insert a new line and see some of the keyboard lab reduced this will be an amazing keyboard. I still would love to see the half screen option. I now am not seeing it as crucial as I thought at the start of testing the keyboard extension.

Ed worrell



Usage thoughts...

Ed Worrell <ed.worrell@...>
 

Hello,

I have been inserting flick type more and more into my everyday use. I actually am really starting to like the full screen keyboard idea. When we get the manual typing feature back, being able to insert a new line and see some of the keyboard lab reduced this will be an amazing keyboard. I still would love to see the half screen option. I now am not seeing it as crucial as I thought at the start of testing the keyboard extension.

Ed worrell


Re: Memory warning!

 

Thanks for reporting, Chuck! The memory warning is due to all the text typed in one session and not the large font of the current word. Each time there is an active session the memory has to stay within the limit set by Apple, so each time we type a large amount of text in one session the active memory is getting strained. Kosta has some ideas to fix this, but we'd like to keep hearing about when this happens and in what context just as your reported, Chuck.

Cheers!
Ashley


Re: Build 54

 

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

1761 - 1780 of 2168