-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Opinion/Suggestion: delay delays recognition to raise, not time to raise #215
Comments
I double checked the code. Lets say you set a delay of 3. Then if within 3 time ticks the mouse moves, another 3 ticks must pass before raising. If however the mouse moves again within those last 3 time ticks, yet another 3 ticks must pass. And so on. In other words: as long as the mouse moves, the window won't be raised. If you combine this with a focusDelay setting of 1, then this should give you the ideal behavior. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems like given the
delay
, the window will raise after thedelay
I found this a bit counter intuitive - I could have accidentally hovered over a window without intention to raise. But if the delay meant it would ignore my mouse for X ms but still focuses (given no focus delay), then its the best of both worlds:
Can now quickly focus and interact without raising -- but hover longer (delay as threshold) when committing to a raise
Hopefully this resonates with some users, thanks for the package!!
The text was updated successfully, but these errors were encountered: