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

[BUG] After a UI item is deselected from a mouse, select the default UI #44

Open
japtar10101 opened this issue Sep 11, 2019 · 1 comment
Assignees
Labels
bug Something isn't working priority-low Indicates the 2nd lowest priority.

Comments

@japtar10101
Copy link
Member

Describe the bug

If one clicks outside of the menu, none of the buttons will be selected. This is not good if the player is about switch from keyboard or controller. If no UI is selected for a fraction of a second, automatically select the default button for that menu.

To Reproduce

Steps to reproduce the behavior:

  1. Run the Main Menu scene.
  2. Plugin the controller. Confirm the start menu can be navigated.
  3. Use the mouse to hover away from the current UI element.
  4. Attempt to navigate the menu again.

Expected behavior

Controller navigation still responds.

Actual behavior

Controller navigation does not respond. No UI element is highlighted, so navigation is not possible.

Additional context

Carry-over from the old Bitbucket Mercurial project:
https://bitbucket.org/OmiyaGames/hg-template-unity-project/issues/39/after-a-ui-item-is-deselected-from-a-mouse

@japtar10101 japtar10101 added bug Something isn't working needs-priority Indicates the priority of the issue has not been determined yet. This is the default priority. labels Sep 11, 2019
@japtar10101 japtar10101 added this to the Complete migration to Git milestone Sep 11, 2019
@japtar10101 japtar10101 self-assigned this Sep 11, 2019
@japtar10101
Copy link
Member Author

In theory, this is fixed, but needs verification.

@japtar10101 japtar10101 added priority-low Indicates the 2nd lowest priority. and removed needs-priority Indicates the priority of the issue has not been determined yet. This is the default priority. labels Sep 11, 2019
@japtar10101 japtar10101 removed this from the Complete migration to Git milestone Oct 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority-low Indicates the 2nd lowest priority.
Development

No branches or pull requests

1 participant