[Feature] Pass taps down to the app behind the edge when unused.

[0-BlackSpectrum-0]

If possible can you please add a toggle that will bypass taps, I only want to change brightness when I swipe up and down on edge but it to do nothing when I tap on the edge, since some buttons are there and seek activates when I try to press those buttons and I am unable to press them.

[LSafer]

Enabling swipe gestures causes the seek gesture to require holding your finger for a little bit first to activate. This is done this way to prevent executing the task of seek gestures while swiping.

[LSafer]

I just released 0.3-pre.6. Does it fix the issue?

[0-BlackSpectrum-0]

Hmm... I don't see any option like that, also while typing it still sometimes activates seek instead of pressing letters, so no ig...

[LSafer]

I just improved how the app distinguishes between swipe gestures and seek gestures.

[LSafer]

Sorry, I am not a native English speaker. It took me reading your request multiple times to understand the issue.

You are talking about the edge colliding with apps and buttons, right?

This is a thing that can't be fixed but rather worked around. Making the edge "center-only" with a smaller thickness could be a solution since apps don't usually put content on there.

[LSafer]

Additionally, if the issue is only when specific apps are open. A whiltelist/blacklist feature will be introduced in the future and it might be the fix that you need.

[0-BlackSpectrum-0]

Oh OK it can't be helped I guess, I'm just curious, what you thought was the issue that was fixed in pre6? (Just curious)

[LSafer]

In 0.3-pre.5, I introduced swipe actions. It was a pain to distinguish between swipe gestures and regular seeking. Thus, when any swipe gesture was enabled, I made the app not responding to seeking unless the user didn't move their finger for a little bit (aka. did a "tap"). In the new release, there is a small timeout for the user to swipe with high velocity. If the user didn't do a swipe gesture and the timeout was done. Then the app will register the gesture as a seek gesture.

[LSafer]

Initially, I thought no one would notice. But, many people have complained about swipe gestures and then I saw this issue and I thought I should re-implement the whole strategy for distinguishing between swipe and seek gestures.

[haarp]

I think the point is that when only seek is enabled, taps should be passed through to the app below. I think it's a great idea!

[LSafer]

It is not possible (not without root or maybe device admin) to pass through taps. I can only tell the system that I want to receive touches at this specific area in the screen and that is it.

[haarp]

I think accessibility services should be able to do that, no?

[LSafer]

It seems that yes accessibility permission can be utilized like that. But, still, why not just reduce the thickness of the edge?

[LSafer]

Plus, I think the "bypassed" touch events will not be smooth at all. You click, then, about 100ms later, the app receives the touch event.

[haarp]

Reducing the size makes it almost unusable. I've tried all locations and I still frequently collide with it because I need to tap there for one reason or another. For example I had it in the top-middle, and it usually doesn't get in the way, but trying to activate a browser's address bar there yields in only chaning brightness.