Calling .remove(func) on a C# static event after a .add(func) makes further .add()'s fail to be called

[TheMightyGit]

These steps happen in my code (using 0.9.8)...

• I have a C# static event, and in Lua code I myEvent.add(lua_func) to it. Event triggers lua code just fine. Hooray!
• I use myEvent.remove(lua_func) to remove it from the event. Event no longer triggers lua code, as expected.
• I use myEvent.add(another_lua_func) on event. But this code is not called when the event triggers :(

If I put in a dummy delegate before the above - it all works as expected.

So I think that when I remove the last delegate from the event it somehow resets its state, and for some reason from then on Moonsharp is no longer looking at the same event? As if returning the event it to null actually created a new event object (I'm no C# expert, but it seems that events/delegate do some magic in their null state).

Does this sound plausible?

NOTE: I have previously noticed that I need to Unregister and Register classes with static events in them if I null any of the static events, otherwise they no longer work - this seems like its the same(?) issue.

[TheMightyGit]

Using net35 in Unity (4.6.8f1), I should add.

[xanathar]

Event management in MoonSharp is enormously complex, so a bug there is not unlikely !

Will check this asap. (Ideally I want to go 1.0 pretty soon, so I'll try to fix sooner than later!)

[TheMightyGit]

Cool :) For now I can use my work around. Good luck bug hunting. Let me know if you have any trouble reproducing it, if you do then I can try and make a minimal Unity project that exhibits the problem.

[xanathar]

Solved on master (not yet deployed on binaries!)

[TheMightyGit]

Confirmed working using latest src in Unity project. \o/ Thank you :D

[xanathar]

You're welcome :)