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

Double check code, sim is not operable with mouse after some mixed input interaction #446

Closed
terracoda opened this issue Mar 18, 2022 · 8 comments
Assignees
Labels
type:bug Something isn't working

Comments

@terracoda
Copy link
Contributor

After last commit, in #440 the Preferences menu button can become unclickable and not operable via the keyboard after a little bit of interaction.

@terracoda terracoda added the type:bug Something isn't working label Mar 18, 2022
@terracoda
Copy link
Contributor Author

terracoda commented Mar 18, 2022

This might be resolved when #440 and related issues #381, #441 are all implemented?

@terracoda
Copy link
Contributor Author

Actually, it's more than just the Preferences button. The sim is inoperable with a mouse, unless my hardware is the issue.

@terracoda
Copy link
Contributor Author

Updating, after last commit, the sim can become inoperable with a mouse. It appears to work fine with the keyboard, but I think I did notice at least once that the Preferences button was not operable vi the keyboard after interaction.

@terracoda
Copy link
Contributor Author

A reset does not fix the problem.

@terracoda terracoda changed the title Double check code the Preferences button Double check code sim is not operable with mouse after some mixed input interaction Mar 18, 2022
@terracoda terracoda changed the title Double check code sim is not operable with mouse after some mixed input interaction Double check code, sim is not operable with mouse after some mixed input interaction Mar 18, 2022
@zepumph
Copy link
Member

zepumph commented Mar 18, 2022

When you encounter this problem, have you looked in the console? Is there an error? Make sure you are running with assertions enabled &ea and see if anything is in the console. I cannot reproduce from some fiddling with keyboard/mouse input combinations.

@zepumph
Copy link
Member

zepumph commented Mar 18, 2022

I'm not sure about this, but if you find you're getting this assertion:

Assertion failed: focusable Nodes do not support DAG, and should be connected with an instance if focused.

Then I have reproduced this problem, and it will be fixed in #440.

@zepumph zepumph assigned terracoda and unassigned zepumph Mar 18, 2022
@terracoda
Copy link
Contributor Author

terracoda commented Mar 18, 2022

Checked console, but will check again next time it happens.

@terracoda
Copy link
Contributor Author

This mystery issue is not happening anymore. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants