Skip to content

Fix StandardInput singleton bug#296

Open
eidursveinn wants to merge 1 commit intoTouchScript:developfrom
eidursveinn:fix-standardinput-singleton-bug
Open

Fix StandardInput singleton bug#296
eidursveinn wants to merge 1 commit intoTouchScript:developfrom
eidursveinn:fix-standardinput-singleton-bug

Conversation

@eidursveinn
Copy link

What's the bug?

Previously the logic only checked whether the variable storing the singleton instance was null and if not destroyed it. However that doesn't take into account that the StandardInput component may have been disabled and then re-enabled and that this is the same instance as the one we had previously stored as the singleton instance.

This branch fixes that by adding a check for whether this is the same instance as we stored.

Previously the logic only checked whether the variable storing the singleton instance was null and if not destroyed it. However that doesn't take into account that the StandardInput component may have been disabled and then re-enabled and that this is the same instance as the one we had stored.
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 this pull request may close these issues.

1 participant