[PD] data structures question ...

[Christof Ressi]

> 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.

> i think before that, i have yet to figure out what data structures can 
> really do, i'm still learning.

to give a personal example, 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. 

Christof
 

> Gesendet: Sonntag, 21. Mai 2017 um 11:40 Uhr
> Von: oliver <oliver at klingt.org>
> An: pd-list at mail.iem.at
> Betreff: Re: [PD] data structures question ...
>
> Dan Wilcox wrote:
> > I think y’all should make a data structure feature request list (if
> > there isn’t one already).
> 
> i think before that, i have yet to figure out what data structures can 
> really do, i'm still learning.
> 
> but for my specific problem (avoid mouse input in already drawn arrays):
> 
> i think something like a "lock" message/method for arrays would be all 
> that's needed in this case.
> 
> would be great for "normal" array graphs as well.
> 
> miller, could this be implemented in the next PD release ?
> 
> 
> @FEDE: thanks for all your thinking !
> 
> best
> 
> oliver
> 
> >
> >> On May 20, 2017, at 5:42 PM, pd-list-request at lists.iem.at
> >> <mailto:pd-list-request at lists.iem.at> wrote:
> >>
> >> *From: *Fede Camara Halac <camarafede at gmail.com
> >> <mailto:camarafede at gmail.com>>
> >> *Subject: **Re: [PD] data structures question ...*
> >> *Date: *May 20, 2017 at 5:42:49 PM MDT
> >> *To: *oliver <oliver at klingt.org <mailto:oliver at klingt.org>>
> >> *Cc: *pd-list at mail.iem.at <mailto:pd-list at mail.iem.at>
> >>
> >>
> >> Hi oliver, thanks for sharing
> >>
> >> I'm trying to wrap my head around this but it seems that arrays in
> >> structs don't provide a "change" flag, making my suggestion null.
> >>
> >> I really cant think of a way to internally block mouse interaction in
> >> a gop patch. You could plot a graph on a canvas with an external, and
> >> have the data structure somewhere hidden, like in an actual array object.
> >>
> >> Hope this helps
> >>
> >> Best,
> >>
> >> fd
> >>
> >> fdch.github.io/tv <http://fdch.github.io/tv>
> >
> > --------
> > Dan Wilcox
> > @danomatika <http://twitter.com/danomatika>
> > danomatika.com <http://danomatika.com>
> > robotcowboy.com <http://robotcowboy.com>
> >
> >
> >
> >
> >
> > _______________________________________________
> > Pd-list at lists.iem.at mailing list
> > UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
> >
> 
> 
> -- 
> \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
> /////////////// http://pendler.klingt.org //////////////
> \\\\\\\\\\\\\\\ http://oliver.klingt.org  \\\\\\\\\\\\\\
> ////////////////////////////////////////////////////////
> 
> _______________________________________________
> Pd-list at lists.iem.at mailing list
> UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: modular.jpg
Type: image/jpeg
Size: 508370 bytes
Desc: not available
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20170521/6ffb0882/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: plot-no-edit.pd
Type: application/octet-stream
Size: 4906 bytes
Desc: not available
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20170521/6ffb0882/attachment-0001.obj>