Thanks Jonathan You are a magician. You said it works, so now it does.... no bugs. The only thing I can't get rid of is the datawindow name appearing in the graph on parent. No matter how many times I turn it off, once I save it and load it again, it comes back on. The name of the main graph on parent does not show, only of the subpatch I attached the abstraction here Cheers Eldad
randomPolygon.pd
Description: Binary data
randomPolygon-help.pd
Description: Binary data
On 2012-11-27, at 11:11 PM, Jonathan Wilkes wrote: > ----- Original Message ----- > >> From: eldad tsabary <tazberryd...@gmail.com> >> To: pd-list@iem.at >> Cc: >> Sent: Tuesday, November 27, 2012 10:31 PM >> Subject: Re: [PD] data structures in abstractions >> >> G reat >> It works fairly well with graph on parent of the subpatch (datawindow) >> However, if I try to make the entire patch into an abstraction and have a >> graph >> on parent of the main window containing the graph from the subpatch it >> doesn't work so well. >> It seems to display in another patch but buggy, and it also doesn't allow me >> to drag and drop the polygon joints. >> Do you know if this should work and how? >> Many thanks again >> Eldad > > Works for me-- I don't get any difference between gop subpatch (or nested > subpatches) > vs. gop abstraction. I can click and drag the joints the same as before. > > What is buggy? > > -Jonathan > >> >> >> >> >> >> >> On 2012-11-27, at 3:09 PM, Jonathan Wilkes wrote: >> >>> ----- Original Message ----- >>> >>>> From: eldad tsabary <tazberryd...@gmail.com> >>>> To: pd-list@iem.at >>>> Cc: >>>> Sent: Tuesday, November 27, 2012 1:48 PM >>>> Subject: [PD] data structures in abstractions >>>> >>>> Hello all >>>> Is there a way to include a data structure graphical shape >> (filledpolygon for >>>> example) inside an abstraction's graph on parent? >>>> I saw that when trying to add a graph on parent in the data window it >> messes up >>>> everything. >>>> Thanks >>>> Eldad >>> >>> Hi Eldad, >>> You have to adjust the x range and y range in the canvas properties >>> to >> be "in >>> agreement" with the x and y size in the canvas properties. So if x >> size is 85, make >>> the range 0 to 84, and do a similar process for the y. >>> I think it's done this way for "Put" menu arrays where >> you would have a different >>> y range depending on the situation. However, drawing instructions like >> [plot] give the >>> ability to scale the values of a scalar to some screen pixel range so I >> don't get why >>> this "range" business is part of the canvas properties (or the >> canvas class for that >>> matter). >>> >>> -Jonathan >>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Pd-list@iem.at mailing list >>>> UNSUBSCRIBE and account-management -> >>>> http://lists.puredata.info/listinfo/pd-list >>>> >> >> >> _______________________________________________ >> Pd-list@iem.at mailing list >> UNSUBSCRIBE and account-management -> >> http://lists.puredata.info/listinfo/pd-list >>
_______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list