this post was submitted on 29 Aug 2024
69 points (96.0% liked)

Lemmy Apps

4992 readers
1 users here now

A home for discussion of Lemmy apps and tools for all platforms.

RULES:


An extensive list of Lemmy apps is available here:

LemmyApps.com

or lemmyapps.netlify.app


Visit our partner Communities!

Lemmy Plugins and Userscripts is a great place to enhance the Lemmy browsing experience. [email protected]

Lemmy Integrations is a community about all integrations with the lemmy API. Bots, Scripts, New Apps, etc. [email protected]

Lemmy Bots and Tools is a place to discuss and show off bots, tools, front ends, etc. you’re making that relate to lemmy. [email protected]

Lemmy App Development is a place for Lemmy builders to chat about building apps, clients, tools and bots for the Lemmy platform. [email protected]

founded 1 year ago
MODERATORS
 

I've had enough of the text editing issue, where when you press backspace it highlights the space before the word and ends up deleting it. The developer passes off responsibility for this to the engine they use and seems to have no intention of addressing it.

What are the pros and cons of the other Android apps? I'm only considering ones on F-Droid, not the Play Store, so that rules out Summit and Boost. Ones I have available are:

  • Thunder (IzzyOnDroid)
  • Interstellar (IzzyOnDroid)
  • Voyager
  • Eternity
  • muffed (IzzyOnDroid)
  • Combustible
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 5 points 2 months ago* (last edited 2 months ago) (2 children)

I've never had this happen, does it need a special set of circumstances?

I get a similar glitch with all keyboards based on AOSP (openboard, etc), where pressing backspace randomly jumps back a few words

I eventually switched back to swiftkey because it was unbearable

[–] [email protected] 3 points 2 months ago (1 children)

I also have never seen that behavior. And even if, would it matter in any way how it handles the backspace key?

[–] [email protected] 2 points 2 months ago (1 children)

It's an absolute pain in the ass. When you press backspace once, the underline for autocorrect extends to the space before the word, then when you press it again it deletes the space, merging it with the word before. It will keep doing this over and over if you keep pressing backspace. You then have to go through and position the cursor just so in the middle of the word to add the spaces back - or, if you don't notice it, you submit the comment and then have to edit it, which marks your comment and makes it dirty (lol, one thing I loved about reddit was the 3 minute leeway for edits).

[–] [email protected] 1 points 2 months ago (1 children)

I still fail to see that this is an issue. I use the backspace key only when I make a mistake. You seem to hang up the whole user experience of an app off it. Just make less mistakes that require you to use backspace.

[–] [email protected] 2 points 2 months ago

I make little typos all the time, and often go back and edit things to change the shape of my comment. The backspace thing is a little thing, but it's persistent and frequently annoying.

Also *fewer :p

[–] [email protected] 3 points 2 months ago (1 children)

Basically when you press backspace the underline for autocorrect extends over the space before the word, then when you press backspace again it deletes that space. Every other press of backspace will delete the space before, completely messing up the text when you're just trying to make a minor correction. You then have the hassle of pixel hunting to get the cursor in the middle of the word where the space was to add it back again.

[–] [email protected] 4 points 2 months ago (1 children)

Ok my bad seems like I recalled incorrectly, your description fits exactly my experience. It's the keyboard

[–] [email protected] 2 points 2 months ago (1 children)

It's not really the keyboard though, the keyboard works fine everywhere else. It's a poor implementation from the text editor that Jerboa uses, one that other keyboards have created a workaround for. But the issue is in the text editor.

It's like when a website only works in Chrome, but doesn't work in Firefox. It isn't because Firefox is broken, it's because the website doesn't follow web standards and has only been tested in Chrome.

[–] [email protected] 2 points 2 months ago

I see, there's the keyboard on one side and the text editor on the other, and they don't mesh well ? that makes more sense