improve language swipe cycling

[codokie]

I've added a setting to adjust the sensitivity of the language swipe/slide gesture distance sensitivity.
The current step value does not work well on some devices like S22+.
Here is the current behavior:

Click to expand

High.mp4

And with the new default Medium option selected:

Click to expand

medium.mp4

fixes #255 and #614

[RHJihan]

Sensitivity 20 is very low for vertical sliding. I am not sure about this approach. Related issue: #255

[codokie]

If you swipe downwards, for sure. But anything higher than 4 may not be feasible as well. That said, if you swipe upwards and have only 2 subtypes, it does make sense.
I could change that to 16 or rename it to "Very Low". There can be a "Very High" setting as well.
How about the following mapping?
4 -> Very high
8 -> High
12 -> Medium
16 -> Low
20 -> Very Low
Alternatively, a slider could be implemented instead, but I think the above options cover most use cases

[RHJihan]

Low sensitivity kind of fixes the flickering problem. However, it requires more travel distance and, so, more time to type. This is a drawback. To address this trade-off, perhaps we could consider other options, like the ones mentioned in #255, such as switching only one language per swipe or stopping the cycle at the end of the enabled language.

This PR is a positive step forward. I'm just curious if there might be an even more optimal solution to this flickering issue.

I'm curious if @nach0 has any thoughts on this approach.

[Helium314]

Just some thoughts, haven't read up on the old issues yet. (so some parts below might be outdated)

If sensitivity is too high for swipe to be usable, does it also apply to cursor movement?
My reasoning was that if a user is able to place the cursor with character accuracy, they should be able to to select a language with quarter that accuracy.
If the general sensitivity is too high, maybe the setting could adjust pointerStep instead?

In my opinion a slider is preferable over a bunch of fixed values, because it allows more fine-grained tuning and requires fewer strings, so less work for translators.

[codokie]

If sensitivity is too high for swipe to be usable, does it also apply to cursor movement?

No, only onLanguageSlide() uses the set value. The calculation for the cursor are different and I have no real issue with them.

a slider is preferable

what a good range would you say it should be? from 1 to 25 ?

switching only one language per swipe

@RHJihan I could implement that very easily but I assume people with many subtypes may not be crazy about it so I might have to add another setting. The other solution is more tricky but I think is feasible. Should I pursue both solutions?

[RHJihan]

Should I pursue both solutions?

I am unsure about which approach would be better. Or implementing both will be a good decision? I think it will be better than the current situation. However, I use only two subtypes, I cannot give a final though on this.
But I don't think anyone would be unhappy if one language change per swipe is a tweakable option.

[codokie]

@RHJihan On a second though I think the 2nd solution is more elegant and renders the first one a bit redundant if there is also a slider for adjusting the sensitivity.
No setting is needed because cycling through all subtypes only once is a desired behavior I believe.
If you have only 2 subtypes, it would be the same as if just one language could be switched per swipe.

In c50acad I've added that functionality as well as the slider ranging from 2 to 18 with a default 10 in between

[codokie]

Oops, I tried to rename the branch but I did not know it will close this PR.

[RHJihan]

works perfectly. loved it

[RHJihan]

@Helium314, just wanted to kindly check in on the status of this PR. I know you're busy, but this PR would be a huge update for me. I’d really appreciate it if it could be reviewed when you have a moment. Thank you!