Pia Baltazar
Pia Baltazar
currently, as it doesn't make sense to have a model and a view in a patcher, the second (and next) one(s) created are shown as bogus it would be better...
these are probably linked so I'm creating just one issue for both, pardon me, @avilleret if I'm wrong ;-p - [x] connecting with device names, like (connect mydevice) doesn't work...
- [x] ossia.attributeS (plural) would be a better name, as we address several attributes with one object - [x] changing the clip attribute only happens one parameter by one when...
If we follow the reasoning described in #208 wouldn't it be nice also to add an alias feature to this ? Here's the idea: We could have a second argument...
we discussed that and it seemed an interesting feature. - for ossia.remote: nothing changes - for ossia.model and ossia.parameter: instead of registering under the nearest ossia.model in the patcher hierarchy...
@jln- could you please find a name for that ? thx
- [ ] liste Max - [x] liste Jamoma (avec mot personnalisé) -> autres ???
by testing if it uses pattern-matching testable by replacing ossia.remote_array by ossia.remote_array_select (from the tests folder) in ossia.remote_array.maxhelp
reproduceable by replacing ossia.remote_array by ossia.remote_array_address (from the tests folder) in ossia.remote_array.maxhelp and clicking on the multislider
related to https://github.com/OSSIA/libossia/issues/360 - [ ] ofxOSSIA - [ ] SC - [ ] QML - [ ] python