Christof Ressi wrote:
i think something like a "lock" message/method for arrays would be all that's needed in this case.
good idea!
in the meantime, here is a hack to achieve just that (see attached patch). it's based on the fact that data structures show up on the parent canvas even if they fall outside the GOP area, so they are visible but you cannot edit them. you can even change the canvas properties dynamically to sort of lock/unlock them. it also works with 'normal' graphical arrays but since they live in a graph (and not in a subpatch) and the graph is anonymous, you have to use [namecanvas] to give it a name. then you can also send it the |donecanvasdialog( message.
thanks, christof ! that's the best workaround so far !
I used them for the cables in a modular synth project - both for the graphical appearance and the data (source, sink, plugged/unplugged? etc.)
see attached picture.
looks awesome ! is this project public ?
thanks a lot !
oliver