| ▲ | quamserena 3 days ago |
| Omg I thought this was just me. How do I turn this off? On iOS, this has been bugging me for a long time. |
|
| ▲ | devmor 3 days ago | parent | next [-] |
| I would love a way to turn it off as well, this is the source of the majority of my annoying typos. |
| |
| ▲ | sushisource 3 days ago | parent [-] | | Seriously this explains so much. I thought I was going crazy, or just becoming an old man who can't type on a phone any more. |
|
|
| ▲ | shakna 3 days ago | parent | prev [-] |
| There is no builtin setting in iOS to disable it. However most 3rd party keyboards don't have it, as implementing it without OS support is a huge pain. |
| |
| ▲ | nneonneo 3 days ago | parent [-] | | Why is it hard? In principle you render an image instead of discrete buttons, and do your hit testing manually. Sure, it’s more annoying than just having your OS tell you what key got hit, but keyboard makers are doing way fancier stuff just fine (e.g. Swype). | | |
| ▲ | shakna 2 days ago | parent [-] | | Apple's keyboard receives more information, to put it simply. It doesn't get told that a touch was at a particular point, but the entire fuzzy area. Allowing you to use circular occlusion and other things to choose between side-by-side buttons and override the predictive behaviour when it is the wrong choice. A third-party maker gets a single point - usually several in short succession, but still it requires more math to work out where the edges of the finger are pressing, to help determine which direction you're moving. So most just... Don't. | | |
| ▲ | jrmg 2 days ago | parent [-] | | Are you aware of the `majorRadius` and `majorRadiusTolerance` UITouch properties? | | |
| ▲ | shakna 2 days ago | parent [-] | | Apple's software gets the actual mapping matrix that those use. |
|
|
|
|
