Looking at the example, I was wondering, how far can you go with polling the effect for all it’s parameters each something is changed?
What scheme are you using in real world scenarios where you potentially have lots of parameters?
It’s seems like the effect should maintain a list of dirty flags in order to tell the UI what it should look for.
another related question. how to communicate data beyond just normalized floats between effect and UI without coupling both too tightly.
I was thinking about using something like that in the effect
bool SetProperty(const long id, void *data, const long size); bool GetProperty(const long id, void **data, long *size);
I was also thinking about calling setParameterNotifyingHost() from the effect (which knows how to convert data to a normalized range) in response to a property change. And ensure that the UI widgets only have to deal with meaningfull parameter ranges.
Any comments, good or bad experience with something similar?