Support more complex clusters of event registration refnums

[Intaris]

Currently, we have the option to cluster event registration refnums when working with the Event structure to allow for some modicum of organisation.

A co-worker recently tried to wire up a cluster of clusters of event registration refnums and was surprised that it didn't work.  I thought he'd made a mistake but to my dismay I could not get it working.  It seems that there's a one-cluster rule when working with event registration refnums with the event structure.

I think everyone would agree that more hierarchical organisation of User Events is a good thing so my proposal is that far more complex clusters be supported by the event structure, allowing us for more hierarchical structure of events.

My example does not include a name for the topmost cluster of the lower example - obviously naming the clusters / events would be far more useful when using events.

[Yamaeda]

If it's any comfort, it works well to build an array of the events and use Array to cluster before registering 🙂

/Y

[Intaris]

Arrays only work if the event types are the same.  This is often not the case.

[Hooovahh]

I like the multi-level tree, and I like the clusters of clusters.

As for the array, we have a publisher subscriber architecture, which uses arrays of user events, where they all use the variant data type, which is then type cased to the control type associated with the name of the event (pulled from the variant attribute).  This scales well for us as long as the same types are used.  To help with this we have some scripting code to make the sender, receiver, and replier code.