handle = addEventHandler ["whatever",{}];
the handle is only known once EH is created and the code is sealed, so there is no way passing this to the code upon EH creating. The only way to use this is to store EH handle in a variable for later use.
Why not pass EH handle to the code upon EH triggering? Like you can pass action ID to action code in addAction? Would make it so much easier to remove them from their own code.
Thank you.
Well, doing that now would break everything, unless it's added to the end of the parameter list. Which would make it in the middle if new parameters were added to the EH.
What they could do is add an overload of the removeEventHandler that takes a code block. The code block that was used when the EH was added.
Eg.
myCallback =
{
player removeEventHandler ["Fired", myCallback]; hint "The player fired! Removing EH!";
}
player addEventHandler ["Fired", myCallback];
Adding new param at the end of param array is not tragic and won't break anything and allow for further expansion. I'd say this is another 5 min job with great outcome. Talking about costs vs benefits, this one is a definite winner.
EH handle could even be passed as a separate variable, not necessarily as part of _this array. Could be _id, to make it easy to copy paste update all event handlers.