Skip to content
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

"Disable" does not disable "Focus follows mouse" #1598

Open
steef435 opened this issue Feb 13, 2024 · 0 comments
Open

"Disable" does not disable "Focus follows mouse" #1598

steef435 opened this issue Feb 13, 2024 · 0 comments

Comments

@steef435
Copy link

Describe the bug
When disabling Amethyst via the Disable button in the menubar icon menu, window focus still follows the mouse.

Applications:
Amethyst

To Reproduce

  • Enable "Focus follows mouse" in the settings.
  • Disable Amethyst via the menubar icon menu.
  • Move the mouse between windows, notice focus follows the mouse.

Expected behavior
As Amethyst is disabled, I expect the "Focus follows mouse" behavior to be disabled as well.

Versions:

  • macOS: 14.2.1
  • Amethyst: 0.20.0 (108)

Debug Info

$ /Applications/Amethyst.app/Contents/MacOS/Amethyst --debug-info
Version: 0.20.0 (108)

OS version: Version 14.2.1 (Build 23C71)

Screens:
	(0.0, 0.0, 1470.0, 956.0) [(0.0, 0.0, 1470.0, 956.0)]

Configuration:
floating: (
)
enables-layout-hud-on-space-change: 1
window-margin-size: 0
use-canary-build: 0
mouse-follows-focus: 0
window-max-count: 0
float-small-windows: 1
screen-padding-left: 0
window-margins: 0
layouts: (
    tall,
    wide,
    fullscreen,
    floating
)
screen-padding-top: 0
ignore-menu-bar: 0
mod1: (
    option,
    shift
)
restore-layouts-on-launch: 1
window-minimum-height: 0
screen-padding-right: 0
debug-layout-info: 0
new-windows-to-main: 0
window-resize-step: 5
focus-follows-mouse: 1
enables-layout-hud: 1
window-minimum-width: 0
screen-padding-bottom: 0
floating-is-blacklist: 1
follow-space-thrown-windows: 1
mod2: (
    option,
    shift,
    control
)

Additional context
As a new user, I am not sure whether this is a bug or intended behavior--if so, apologies for the noise...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant