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

mouse click-release actives items #768

Closed
wharlox opened this issue Sep 24, 2022 · 0 comments · Fixed by #932
Closed

mouse click-release actives items #768

wharlox opened this issue Sep 24, 2022 · 0 comments · Fixed by #932

Comments

@wharlox
Copy link

wharlox commented Sep 24, 2022

when click-hold and dragging gui windows within gw2, a mouse-release on top of blish-hud items activates many items.

Expected behavior:
clicking down on an item should only activate said item if mouse-location is in the activate-able region of said object (aka not in some other area of the screen); (even GW2's ui has this inconsistently implemented)

A good working example within Gw2-itself is switching Build Templates; mouse must be over each Tab to click-down and click-up for it to activate; another is right click an item and clicking on a menu item and click+hold mail, and un-clicking in gnarnia does not activate mail-menu; and lastly click+hold an item in the Daily hero panel (like Daily Completionist) and un-clicking far away does not drill into details.

Examples of unexpected behavior:

  • move gw2-inventory window and un-clicking while hovering over the blish-hud icon at the top of the screen will open the Blish Hud UI.
  • move gw2-inventory window and un-clicking while hovering over the blish-hud main window will activate: Module Repo, Overlay Settings (and even trigger many menus within)
  • active on plugins too such as ToDo's; moving a gw2-window behind the ToDo's window and un-clicking will toggle any checkbox or item within ToDos
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

Successfully merging a pull request may close this issue.

1 participant