-
Notifications
You must be signed in to change notification settings - Fork 148
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
Add "initRetro" event to addClassEventHandler #324
Conversation
Runs init code on all current and future objects
Looks interesting |
Looks useful. I'm pondering if there are other ways of naming the event. Still thinking... |
Why not make the |
I was thinking the same, but that function has two optional parameters already, and I have two wacky alt proposals:
|
I was not sure about the event name; I think commy2 's idea would look like this: Parameters: To Call:
If we like this way more, I will make the changes |
I like the optional argument more, don't really see a need for a completely separate event. |
Agree - I prefer to have it as an optional argument to CBA_fnc_addClassEventHandler. |
Updated |
I added another check to not do weird stuff with events that are not "init" and "initPost" |
As far as I can tell, it should be spelled |
Example usage:
Normal "init" would have no effect on existing units because unit's init event has already happened by the time the settingsInit event has happened.