[Backswipe from edge] No blacklisting/prioritisation

[Aracnoss]

Affected hardware version

Bangle 2

Your firmware version

2v29

The bug

Describe the bug

Currently the backswipe from edge app is quite sensitive, triggering from fairly small swipe gestures.

So this will, almost guaranteed, trigger on apps that have swipe behaviour themselves, such as keyboards or the quick launcher.

Expected behaviour

Ideally, this should have a blacklisting, or allow some form of supersedable swipe functionality.

Otherwise reducing the senstivity, or providing the option to, so you perform a longer swipe, would reduce the likelihood of triggering this by accident.

Installed apps

cprassist (0.02), files (0.08), widbt (0.09), qmsched (0.10), wid_edit (0.05), oxofocus (0.02), notifyfs (0.12), dragboard (0.10), about (0.15), widalarm (0.02), themesetter (0.05), 2047pp (0.04), diceroll (0.02), a_dndtoggle (0.02), acmaze (0.05), rebbleagenda (0.02), autoreset (0.02), fontext (0.03), reply (0.03), widmessages (0.07), mylocation (0.11), drained (0.08), torch (0.11), dtlaunch (0.28), quicklaunch (0.16), lightswitch (0.11), score (0.04), fileman (0.04), alarm (0.52), gpstime (0.05), compass (0.09), agpsdata (0.06), widgps (0.09), ptlaunch (0.16), poweroff (0.06), imc (0.01), powermanager (0.13), weather (0.31), trex (0.05), snaky (0.01), dvdbounce (0.01), blackjack (0.03), longpressbuzz (0.01), jwalk (0.01), clockinfolist (0.01), sched (0.36), setting (0.82), phoneremind (0.01), widsmartbatt (0.02), smartbatt (0.04), icons (0.03), multitimer (0.12), loadanim (0.02), messages (0.70), schedclock (0.02), android (0.46), dailycolorclk (0.02), messageicons (0.17), boot (0.69), modclock (0.06), messagesoverlay (0.12), clock_info (0.27), exactwords (0.2), popconlaunch (0.05)

[thyttan]

Some background at #4157

tagging @ssievert42 if you want to chime in.

[ssievert42]

First off, cool that someone is getting some use out of my app :)

I guess adding blacklisting does make sense; do you have a specific app where you're accidentally triggering a backswipe?
(Maybe dragboard? I personally use kbswipe.)

Not having any kind of config was to speed up load times, but I never actually tested load times if we were to read some config on boot.

How would we go about changing the sensitivity though?

A swipe already has to start all the way from the right side of the screen; I've just gotten used to not swiping from that edge of the screen like I do on my phone.
Really don't want to wreck that button again, so that's a tradeoff that has been fine for me personally.
Also a fan of quicklaunch and sticking to avoiding swipes from the right edge of the screen has been working fine so far.
I even sometimes use a backswipe to cancel quicklaunch if I accidentally trigger it.

If the swipe had to be longer, that probably wouldn't prevent accidentally triggering a backswipe from quickly swiping across the screen and lifting the finger again.

However adjusting where you've got to start would be possible. Since we've got to adjust for the values we're getting including screen calibration, the position where a backswipe has to start may not always really be as far to the right edge of the screen as possible.

I'm kind of busy with university stuff right now; if anyone else wants to have a go at improving this you're very much welcome to do so :)

[thyttan]

Also, just to mention it, backswipe has a bit more granular control compared to backswipeedge for when it should be active.

[kidneyhex]

Just extra feedback: I switched from backswipe to backswipeedge almost as soon as it merged, and haven't had any unintended back swipes. So it could be a calibration or just user habit/intuition thing.

I don't use keyboards, but quicklauncher, messages, multitimer, and a custom music control where swipes change what buttons are on screen. So a lot of stuff had to be blacklisted that I don't anymore. :)