Pia Baltazar

oh, sorry, I forgot to change one object in the abstraction - it is now committed and here is the patcher: ----------begin_max5_patcher---------- 653.3oc6VssiaBCD8Y3qHhmoHrgvk9IzegpJjC3l0q.6HiYaRix+dGeABjtM Jaa1VUo7PHLiG6wmim4XN56ErQrm1Gr5iq97JOui9ddFWZGdNaufNx95VRuI rftgVEquk0PkAg1w4CchAUKUYh.67tiHIcTEUVQ4jMsT8XwtwpEbUCQQz9PN e8v7UGrwM4azQvXtrIRcXG0togAfeq9x3DXe2t.Ym2aL93VCMs0T0Ow3aqjz ZkccRiwQwgqRPIQqg+VGqsPIqihOu1TErV.YXmgMhYiyZL6Twlm+.NOP66ju u9Q3CpEnphr6ByV96vrb52fIOBTEcuxtf88LRjj1ITzJhTRNrpVzJjQGQ4QQ I3SW+X3MSglEeDiH75zxP3k7xr37B8aEkoHTwRr+FYYbBVSynhbiE90Ywj3G 0mSLGt7d14m8fYufYKWeWHVz6ZieUOsE12S8+QQnro1+VFmVKF3p4GE+GnIX...

How would the modifiers messages work, then? Wouldn't we need press and release?

also, would that work from a client, i.e. remotely (that would be great !)

thinking again about names for this: - we agreed that ossia.node was a good, more generic name for what is currently called ossia.model - thinking again about it, I would...

I forgot to mention the usual suspects: @reno- @jln- @avilleret

this can come later, I think, as those are additions (and if we decide to use those names, we can always set aliases to model and view so they can...

I just tested and, nope, it doesn't work - the parameter is created under the “closest" parent model I guess it's interesting to keep this idea here, so I've just...

yes, that would be the more sensible way to do it... but AFAIK there is no reliable way in Max to know that a patcher has been loaded (my usual...

You mean that the user would have to click a button for that ?

I believe that loadtimes might be dramatically increased with nested models, mutliple devices, etc… could you cook us this kind of test patcher for testing purposes, @jln- ?