release event delay applied to hover gestures too?
Opened this issue · 11 comments
The recent release event modification you just did is not just applying on clickable actions, but also to hover actions. Would you not mind giving us atleast the manual toggle of this behaviour? Caz this is driving me insane tbh. It's a complete workflow differentiating factor for me & it's quite a big deal for this changed action.
The problem I get with this, is this scenario:
Have Overview on top left (hover), & App menu on the same top left (click).
Imagine you need to get into appmenu. You click top left > appmenu appears, you move mouse away from corner > appmenu closes (obviously, caz overview gets triggered & closes appmenu).
Try it yourself.
There is no change in how hot corners work. The triggers are built in the mouse pointer barriers and react on "pressure", which is actually a distance the mouse pointer would go behind the barrier if there was no barrier. You can adjust the amount of pressure that is needed to trigger each hot corner. Only if you enable option "Use fallback hot corner triggers" the barriers are replaced by 2x2px objects and the "enter" signal is used to trigger an action. But again, there is no change.
The release signal only affects mouse buttons.
If you open any panel menu, from this moment you can open any menu on the panel by hovering their button without clicking. It also means that the menu closes when you hover another panel button.
So I guess that your problems are not related to CHC-E.
Oh & this happens only on wayland. It's fine on X11. I wonder why the behaviour is different across different display servers...
I'm not sure I understand what you're talking about. Can you show me a screencast?
Clicking to the active hot corner is problematic in any case as you have to be careful not to trigger the hot corner if you want to click. I'd suggest to expand the clickable area vertically or horizontally while keeping the pressure barriers small and clicking the edge outside the corner.
I'm fine with hot corner trigger before click action, atleast for the above example I gave (Overview / AppMenu). That's how I intend to have. Caz appmenu is inside the overview, that's how it should be.
The problem is This particular changelog, which I'm trying to explain.
Asking whether to revert back action to press event from the current release event, or atleast give us the option to select that behaviour.
When the action was press event before you changed it to release event, everything was fine (appmenu doesn't close caz overview already triggered before it). Now the appmenu triggers first (click event) & then overview (which closes the opened appmenu).
But it also happens for hover too.
Action gets triggered only when I move mouse away from hot corner (instead of triggering right away when I hover the corner)
There is no 'hover' as I explained before.
There is no 'hover' as I explained before.
Oh okay. Thank you btw.
Will let you know if fixes this. Don't yet close the issue btw.
For some weird reason, the behaviour changes after couple minutes of standby. Relogging fixes the issue. So strange. This hover issue happens only on wayland. Looks like wayland has the strangest issues on Earth.😅
I still don't understand your use case, so I can't help you with it.
I still don't understand your use case, so I can't help you with it.
Nothing unusual in the extension btw. It's just that my setup is wanky XD.