Re: a few bugs
Hi!toggle quoted messageShow quoted text
Congrats on the new baby!! So sorry it has taken me so long to reply, but I’ve also done some testing in the meantime and now have more info:
1. The strange behavior after new line: I’m not sure if this is new or not, but it’s been around for a while, just haven’t had a chance to report it or figure out when/where it came from. Note that I’ve been using half screen mode since it was introduced in Alpha, so maybe this is specific to just that? Not sure, but I can try in other modes and see if the behavior persists.
2. Kind of same as 1, more stuff about entering new lines, but you said that had already been reported. :)
3. The clear taps and/or adding periods is still happening accidentally for some reason. Again, seems to be something that probably started during half screen mode. While I’m on this subject, I’ll also add that I’ve had occasional times, I think when a new line is added, where I’ll type something like:
But when I go to change the period to a comma, Flicktype inserts multiple periods every time I swipe down, and doubles as it goes. haha so it will insert 1, then 2, then 4, then 8, etc. and when I go to delete the word I’ve just typed, it will say deleted 8 periods, etc.
4. It’s taken me a while to figure this one out, with different case entries in the dictionary, but it seems to be the second time that I’ve typed the word. So if I add "CSA" to the dictionary, and then type the word using Flicktype normally, it will type CSA. But symaltaniously, Flicktype seems to also enter this as a new entry in the dictionary, as "csa". So the next time I type "csa" into FlickType expecting it to come out as "CSA", it writes it as all lowercase "csa" because there’s now 2 entries of it in the dictionary. Not sure if all that makes sense, a lot to try and explain, but that’s the pattern I’ve noticed so far.
Thanks so much,
On Oct 25, 2018, at 3:45 PM, FlickType <email@example.com> wrote: