Another approach for a generic event system#4
Open
FluffySpectre wants to merge 1 commit intoquill18:masterfrom
Open
Another approach for a generic event system#4FluffySpectre wants to merge 1 commit intoquill18:masterfrom
FluffySpectre wants to merge 1 commit intoquill18:masterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi, my approach keeps the event data and the event management logic separate, like your original version, but i converted the EventSystem class into a templated static class which removes the need for a specialized event base class and the explicit type casting.
Check it out, if you want.