Rewasd is locking Inputs when using Mute

[Oistea]

Hello,
I am new to this Forum and using this Programm only for a few days now.
I must say it is a bit comlicated to understand the functions and how they relate to each other.



I hope someone can point me to what i am doing wrong.

My main Problem Today is, that Rewasd is locking my Inputs every time in a specific Situation :

1. I have a group (mouse and keyboard)
2. I want to use the backward mouse button to shift to another layer1 when held for half a second and shift back on release
3. For this i have to mute the native input (back) in the layer1

each time i use this function my Mouse keys (not movement) are disabled in windows other than the one currently active
I can´t minimize the Window - i have to close it and wait a few seconds / or press strg_alt_del to switch off rewasd

Config example:
Config 1.rewasd


i have found a similarity to this post from 2019 " https://forum.rewasd.com/forum/rewas...-locking-mouse "



Thanks in advance for the help.

[Kapas]

Hi Instead of using hold mode, try switching to the Toggle function.
That way, pressing the button will activate the shift layer once (no need to keep it held), and pressing again will turn it off. This may be more convenient when using the mouse.

[Oistea]

Thank you for your advice.
You are right - in toggle mode the mouse input is not beeing locked after switching layers.

But in the toggle mode i cant mute the intput of the native key --- when returning from the switched layer the native key input is triggered



I am just not sure if i am doing it wrong ? - are the developers aware of this problem ?
Because i dont think it is intended this way:
- locking inputs on every other window than the one currently active when switching layers with hold mode and muting native input in the switched layer -

[Oistea]

Aaand i apparently cant click to play YouTube Videos after the input has been locked even though i can navigate everything else in Browser.
That may be because the Video is considered another Window / entity from the Browser Tab.

[strokel]

Hi. Could you please send us a video showing this issue?

[Oistea]

[Oistea]

I cant record mouse clicks though.

I want to add: The Problem does not appear for keyboard - but the native key input (even though i muted it in layer 1 too) is applied / triggered here before switching layers)
which is not true for mouse inputs

[Support Agent]

Ok, I think I understand the issue.

Other apps do not accept left-clicks because the [X1] button is still being held, so the focus is forced on the app you used [X1] button on first.
And the [X1] button is being held because you have muted it on the [Shift Layer 1], and the "release button" signal was not sent to the system.

This is not a reWASD issue. It is a misconfiguration that triggers unexpected behavior related to how Windows works with app focus.

[Oistea]

I get it - that makes sense
Thank you for your help with the issue

Though i just tested it with my Logitech Mouse (G502)
The "G-Shift" function allows for the same maneuver and without issues

[Support Agent]

I'm afraid I don't know what "maneuver" does the "G-Shift" function, but if it works, then it does release the [X1] button at some point.