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

Remove Signal from Fade #1236

Merged
merged 5 commits into from
Feb 21, 2025
Merged

Remove Signal from Fade #1236

merged 5 commits into from
Feb 21, 2025

Conversation

DanRStevens
Copy link
Collaborator

@DanRStevens DanRStevens commented Feb 21, 2025

Rely on Delegate being optionally passed to the Fade constructor.

This simplifies the API a little, and reduces the bloat needed for simple objects.

Related:

Use the constructor to set a single handler for `onFadeComplete`.
This requires checking the `Delegate` is set before trying to call it. This is because `Delegate` defaults to an empty object with `nullptr` values, and setting the `Delegate` is optional. With `Signal`, the collection would have been empty, so it was just iterating over 0 elements. With the `Signal` code it was assumed that if a `Delegate` was set, it was a valid callable instance.
@DanRStevens DanRStevens merged commit c13660e into main Feb 21, 2025
8 checks passed
@DanRStevens DanRStevens deleted the removeFadeSignal branch February 21, 2025 03:54
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