• 0 Posts
  • 20 Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle


  • One of the biggest thing is the actual swipe detection success rate - I have tried heli and others and I find that you need to swipe slower and more precisely for words to register. Also, when wrong word is detected, Swype will typically have the right word suggested in bar above keyboard for a one tap correction, not the case for me on others where no word is often the wrong word is suggested to correct. For example, almost like some of them suggest too literally and lack context - this is tough to describe, so bear worth me, so I try to swipe the word “she” let’s say, and the board detects “the” and the suggested words to correct have more of a relationship to “the”, so think “then” “them” “theirs” maybe, but the logic isn’t starting with other derivations of three letter words ending with “he” that have relevant letters near the “T” on a qwerty keyboard (which Swype feels less likely to do in my experience).

    Otherwise, there are customizing options and other UI choices that I prefer with Swype. It’s definitely gotten worse over the years since it stopped being actively supported, but I’m so glad it’s still functional in some capacity. I wish everyone with FOSS skill would really deep to replicate the Swype experience with the APKs still floating around.




  • You’re not, OP…

    also, feels pretty obvious you haven’t been involved in bidding jobs before - these initial numbers set expectations. If “dad” valued the kid’s talent and time, he would have said, “they’ll give you a number” and/or the message to kid would not have been closed, it would have been open. So instead of, “you’ll do this, thanks bye” it would be a question to kid prior saying, “I know a lot goes into your work, is $500 a good ballpark to give my friend for something like this?”

    It’s about expectations and entitlement - you’re essentially my property, so I decided it would be this is indicative of a problem with “dad’s” approach.