Date   

Re: New FlicktypeBeta

Chuck Dean
 

Just open  TestFlight, it will tell you what to look for.
               

Chuck  (mobile)
Pleez x cuze enny tie ping or spelin air ores.


On Jul 19, 2020, at 4:54 PM, Benny Barber <benny.barber55@...> wrote:

I see there is a new beta. Does anyone know what this version addresses? Thanks.
Benny



New FlicktypeBeta

Benny Barber
 

I see there is a new beta. Does anyone know what this version addresses? Thanks.
Benny


Re: Second crash fix included with new build #282

Salman Haider
 

I have not experienced this issue. I too have the latest version of iOS installed, and have an iphone SE (2nd Generation)and an iPhone SE (1st Generation).
Salman

On Jul 11, 2020, at 5:26 AM, Benny Barber <benny.barber55@...> wrote:

Kosta,
I am not getting phonetic feedback on flicktype. I have not gotten phonetic feedback on the last 2 betas. I checked and I have that setting turned on. I am on the latest iOS. I have an iPhone 6S. thanks.
Benny

On Jul 8, 2020, at 3:02 PM, FlickType <@FlickType> wrote:

Hi all,

The latest beta (build #282) includes another important crash fix for the iOS keyboard. If you can't access the beta for any reason, you can sign up here: https://testflight.apple.com/join/jO9VT6Ei

Warmly,
Kosta



Re: Second crash fix included with new build #282

George Cham
 

How about the option to add more emojis.

Kind Regards,
George Cham

Get Outlook for iOS


From: beta@flicktype.groups.io <beta@flicktype.groups.io> on behalf of Benny Barber <benny.barber55@...>
Sent: Saturday, July 11, 2020 10:26:06 AM
To: beta@flicktype.groups.io <beta@flicktype.groups.io>
Subject: Re: [FlickType-beta] Second crash fix included with new build #282
 
Kosta,
I am not getting phonetic feedback on flicktype. I have not gotten phonetic feedback on the last 2 betas. I checked and I have that setting turned on. I am on the latest iOS. I have an iPhone 6S. thanks.
Benny

> On Jul 8, 2020, at 3:02 PM, FlickType <hello@...> wrote:
>
> Hi all,
>
> The latest beta (build #282) includes another important crash fix for the iOS keyboard. If you can't access the beta for any reason, you can sign up here: https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftestflight.apple.com%2Fjoin%2FjO9VT6Ei&amp;data=02%7C01%7C%7C061fa2e95e5b40ed7cff08d8253103d4%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637300239723478345&amp;sdata=N4DtAMchxtRzHYGk0wb7eVx0jtxkXJ6gIn%2Funvk1d0g%3D&amp;reserved=0
>
> Warmly,
> Kosta
>
>
>




Re: Second crash fix included with new build #282

Benny Barber
 

Kosta,
I am not getting phonetic feedback on flicktype. I have not gotten phonetic feedback on the last 2 betas. I checked and I have that setting turned on. I am on the latest iOS. I have an iPhone 6S. thanks.
Benny

On Jul 8, 2020, at 3:02 PM, FlickType <@FlickType> wrote:

Hi all,

The latest beta (build #282) includes another important crash fix for the iOS keyboard. If you can't access the beta for any reason, you can sign up here: https://testflight.apple.com/join/jO9VT6Ei

Warmly,
Kosta



Re: Second crash fix included with new build #282

Arya
 

Hi Kosta,

Thanks for coming out with this wonderful app.
I would like to bring it to your attention a problem I face while using flick type, in WhatsApp.
I am giving below the steps to reproduce in iPhone 8 plus running IOS 13.5.1

1. Type a message in a chat and hit the send button.
2. Continue to type the second message, after entering the first word and swiping right, voice over will read the earlier message sent instead of the word entered.

Kindly fix this issue.

With regards.

Arya

-----Original Message-----
From: beta@flicktype.groups.io <beta@flicktype.groups.io> On Behalf Of FlickType
Sent: 09 July 2020 01:33
To: beta@flicktype.groups.io
Subject: [FlickType-beta] Second crash fix included with new build #282

Hi all,

The latest beta (build #282) includes another important crash fix for the iOS keyboard. If you can't access the beta for any reason, you can sign up here: https://testflight.apple.com/join/jO9VT6Ei

Warmly,
Kosta


Second crash fix included with new build #282

 

Hi all,

The latest beta (build #282) includes another important crash fix for the iOS keyboard. If you can't access the beta for any reason, you can sign up here: https://testflight.apple.com/join/jO9VT6Ei

Warmly,
Kosta


Re: Important crash fix with build #281

Matthew Janusauskas
 

Thank you Kosta! FlickType has become an essential tool for my productivity that I hope to never be without.

Kind Regards,

Matthew

On Jul 6, 2020, at 6:00 PM, FlickType <@FlickType> wrote:

Hi all,

The latest beta build #281 includes an important crash fix for the iOS keyboard. If you can't access the beta for any reason, sign up here: https://testflight.apple.com/join/jO9VT6Ei

Warmly,
Kosta



Important crash fix with build #281

 

Hi all,

The latest beta build #281 includes an important crash fix for the iOS keyboard. If you can't access the beta for any reason, sign up here: https://testflight.apple.com/join/jO9VT6Ei

Warmly,
Kosta


Re: Build 273

 

Thank you Salman. In my limited testing, I couldn't reproduce the issue that previously necessitated that setting, and in the interest of simplifying everything for both users as well as myself when developing the app, I removed it.

That said, please let me know if you or anyone else still experiences the issue with WhatsApp, and I will consider adding it back. I also have an idea for a better workaround.

Thanks,
Kosta


Re: Build 273

Salman Haider
 

Hi Kosta,

My question is related to usage of Flicktype within apps on iOS, and
not the Watch as I don't own one. I wanted to ask about the "Almost
Full Screen, Workaround" option; I notice that that was removed in
this beta. As you are aware, this was included to prevent crashes in
apps like Whatsapp and Messenger for instance.
These are the apps that I use Flicktype the most in, in addition to
Mail and Messages.
At the time this option had been included, it had been done after days
and days of effort on your part, and feedback from users like myself
who use Flicktype in these apps...it had been concluded that there
really was no solution to the problem apart from making the keyboard
slightly smaller even in Full Screen mode.
My question is, has the issue been resolved completely, so much so
that this option is no longer necessary? I would hate for me to not be
able to use Flicktype in any of these apps in Full Screen mode and
begin experiencing these crashes again.
Can you please shed some light on this and share why the option was
removed? Flicktype is critical in my everyday use of iOS devices, as
it is for a lot of other users, so I really hope that removing this
option doesn't cause the issues as it did previously.

Thanks,

Salman

On 6/4/20, FlickType <@FlickType> wrote:
Hi all,

Please let me know if build 273 works better on Apple Watch. Note that the
new "Slide to Type" feature is not very usable yet for VoiceOver users, so
you might want to turn it off from the FlickType app on your iPhone.

Also note that you can now dismiss the keyboard with a flick down to preview
and send your text. As a reminder, to change suggestions on the watch you
can use the Digital Crown.

If anyone is experiencing any crashes, please let me know.

Thank you,
Kosta




Build 273

 

Hi all,

Please let me know if build 273 works better on Apple Watch. Note that the new "Slide to Type" feature is not very usable yet for VoiceOver users, so you might want to turn it off from the FlickType app on your iPhone.

Also note that you can now dismiss the keyboard with a flick down to preview and send your text. As a reminder, to change suggestions on the watch you can use the Digital Crown.

If anyone is experiencing any crashes, please let me know.

Thank you,
Kosta


New beta link

Daniel McGee
 

Hi all, Kosta has posted a new beta link to the chat list. So thought I'd pass it along, in case any one missed it to the beta list.  see Pasted message below

Hi all,

If you find that you are no longer in the iOS beta for FlickType, please use this link to join: https://testflight.apple.com/join/jO9VT6Ei

Apologies for the inconvenience.

- Kosta


Bug: Flicktype not speaking out the first few letters of a word

Ravi Pinapaka
 

Hello,
When I type with flicktype, it sometimes doesn’t speak the first few letters of a word. It mostly doesn’t speak out the first 2 or 3 letters. It’s not restricted to a single app. And I can’t pinpoint what’s causing it. It seems random. I’m on the latest beta.


Crashed

Chuck Dean
 

Hello, while using the container app running the latest beta, I have had the app crash the last two times.
I am using it now... So far so good.
In both cases I shared the crash data.
This has never happened before these two times??? 

Chuck  (mobile)
Pleez x cuze enny tie ping or spelin air ores.


Re: Explanation needed

Chuck Dean
 

Hello,
A two finger double tap performs the same action as the numbers/letters toggle on the iOS keyboard.

A two finger single tap performs the same action as the shift key on the iOS keyboard. Use it for capital letters and additional symbols.
I hope this helps,

Chuck  (mobile)
Pleez x cuze enny tie ping or spelin air ores.


On Jan 19, 2020, at 8:34 PM, Ng Choon Hwee via Groups.Io <ng_choon_hwee@...> wrote:

• Long-press to access control keys for Numbers, Symbols and Return.
Where do I long press?


Ng Choon Hwee




Explanation needed

Ng Choon Hwee
 

• Long-press to access control keys for Numbers, Symbols and Return.
Where do I long press?


Ng Choon Hwee


Re: Keyboard only visible on long press

Ebrahim Vasta
 

Hi, I was playing around on the type screen and it seems to of been
resolved. I must of accidently switched the typing mode as you
suggest.

On 1/18/20, Chuck Dean <cadean329@...> wrote:
The only thing I can suggest is...
touch typing or direct touch must be enabled for Flicktype to
work. Use the rotor and select touch typing or direct touch



Chuck (mobile)
Pleez x cuze enny tie ping or spelin air ores.

Our 1972 Honda 600 Coupe

Our 1961 Vespa 400

On Jan 18, 2020, at 1:06 AM, Ebrahim Vasta <fascigo@...> wrote:

Hi

I am a voice over user and have been beta testing for a while, ever
since a few versions ago the keyboard section appears grey'ed out and
does not receive gestures. When long-pressing the area the keyboard
appears but then promptly disappears when I lift my finger.
This only appears to be affecting me, I checked with other users and
it seems fine. I tried reinstalling, changing settings, I even
restored my phone to a factory ipsw.
I have the iPhone 7 256GB running IOS13.3





Re: Keyboard only visible on long press

Chuck Dean
 

The only thing I can suggest is...
          touch typing or direct touch must be enabled for Flicktype to work. Use the rotor and select touch typing or direct touch 



Chuck  (mobile)
Pleez x cuze enny tie ping or spelin air ores.


On Jan 18, 2020, at 1:06 AM, Ebrahim Vasta <fascigo@...> wrote:

Hi

I am a voice over user and have been beta testing for a while,  ever
since a few versions ago the keyboard section appears grey'ed out and
does not receive gestures. When long-pressing the area the keyboard
appears but then promptly disappears when I lift my finger.
This only appears to be affecting me, I checked with other users and
it seems fine. I tried reinstalling, changing settings, I even
restored my phone to a factory ipsw.
I have the iPhone 7 256GB running IOS13.3




Keyboard only visible on long press

Ebrahim Vasta
 

Hi

I am a voice over user and have been beta testing for a while, ever
since a few versions ago the keyboard section appears grey'ed out and
does not receive gestures. When long-pressing the area the keyboard
appears but then promptly disappears when I lift my finger.
This only appears to be affecting me, I checked with other users and
it seems fine. I tried reinstalling, changing settings, I even
restored my phone to a factory ipsw.
I have the iPhone 7 256GB running IOS13.3