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

Emit disable event code only if no active handler exists #1919

Merged
merged 1 commit into from Nov 26, 2019

Conversation

ewpatton
Copy link
Member

The change that produced calls to EventDispatcher's unregister method
for disabled blocks did not account for the scenario where both an
active and inactive event handler exist for the same component-event
combination. This change makes it so that unregister calls are only
output if there isn't a matching active event handler.

Fixes #1918

Change-Id: If33b577f5af03c64f7abb8fe5b587d576886889b

The change that produced calls to EventDispatcher's unregister method
for disabled blocks did not account for the scenario where both an
active and inactive event handler exist for the same component-event
combination. This change makes it so that unregister calls are only
output if there isn't a matching active event handler.

Change-Id: If33b577f5af03c64f7abb8fe5b587d576886889b
@jisqyv jisqyv merged commit b377204 into mit-cml:master Nov 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Mixing active and inactive event handlers of the same (component, event) tuple has mixed results
2 participants