I noticed in the documentation, the warnings about /EDIT being a CPU expensive operation are now gone (unless I'm looking in the wrong place). Is this now optimized to not recreate the widget when it's used? I prefer the /EDIT method rather than setting up OSC listeners if possible.
Indeed, /EDIT attempts to update the widget in place if only dynamic properties are modified. Actually it had been that way for some time already and I must have forgotten to update the docs.
Cool! Is there a list of which properties qualify as dynamic?
In the widget reference, all property names followed by a little bolt icon indicate dynamic properties. Also in the the editor, clicking on a property label will bring up a descripting popup that contains this information.
Man...this shit is getting so good! Jean I hope you still have time to make music!
1 Like