As I didn't find related posts using the search feature, I wanted to drop a note here for future reference should someone run into the same issue (that is, I'm not requesting help but rather just pointing out an undocumented implicit constraint with the current EventDelegate implementation).
My UIToggle handler delegates weren't getting invoked when I switched toggle button states. I used a utility method like this that hid the static UIToggle.current.value from the handler:
public static void SubscribeToggle(UIToggle toggle, Notification<bool> handler)
{
EventDelegate.Add(toggle.onChange, delegate
{
handler.Invoke(UIToggle.current.value);
});
}
where Notification<bool> inputs a bool and returns void.
The code above creates an anonymous delegate to be subscribed for onChange. However EventDelegate.Set initializes the handler target as
mTarget = call.Target as MonoBehaviour;
As the handler is an anonymous delegate and not a member of a derived MonoBehaviour, mTarget gets a null value. This causes the EventDelegate.isValid property to return false, and the handler won't be invoked.
I wonder if this is a necessary limitation; the only place where mTarget appears to be used as MonoBehaviour is in the EventDelegate.isEnabled property. This, however, is not used by NGUI.
