It would be really cool if it was possible to define a list of named parameters to an event. These could then be saved in the stringValue as a json encoded string. This way it would merely be an improved visual representation of the event data and wouldn't affect load, save, export, import or the runtimes.

I was thinking something along the lines of having a settings file with the definition for each event type, each being a list of (name, value type, valid range?) items. And when you add a new event you not only enter the name but also select a type in a drop down box.
This way a programmer can for example define a project wide "Sound" event with the parameters needed (name, volume, panning, etc) and a non-programmer could then trigger correctly formatted events with ease.

BinaryCats wrote

I have suggested something similar in the past, idea was mostly disliked :sleepy:

Let's hope people like it better like this then. Json encoding the data in the string will have very little impact on anything else while giving great flexibility on usage. It's a win-win

Pharan wrote

I think it's not that it's not useful, it's that it's not portable to different runtimes, especially for binary.

Well that is just the thing... It is super portable and would work out of the box on all the current runtimes, even in binary. Because it doesn't add anything new to the runtime, it's an editor only feature.