Hello,
I don't know if this is possible (because my pd development skills
are null), but is there a way for you developers to code a specific box which the sliders/bangs/etc could be set in so that when you look at the parent abstraction, it will look exactly like how you set it up in the child rather than appearing all scrunched up? The box could set the pixel dimensions of the parent object in some way, and things that the user didn't want to show in the parent could be left outside of the box. If it could be done then the pd-design/layout would look much cleaner and much more flexible. I hope this makes sense to more than just me. -Mark .K
Good idea... there could be some new "frame" object, which, if you had one in a patcher, would make the parent morph into a panel containing whatever was in the frame. This would make it easy to throw comments around too.
One slight complication is how the parent text should be dealt with (such as "pd my-graphic-subpatch"). If that text is larger than the box, I suppose the thing is just to extent the right edge of the box to hold the text.
Perhaps needless to say, the reason I've held off on doing something like this so far is fear of doing it wrong and being stuck keeping everything compatible. The good news is, that with the current scheme, the "frame" could just default to the whole window area so that I could introduce the frame in an easy-to-manage, backward-compatible way.
cheers Miller
On Mon, Jun 23, 2003 at 01:22:44PM -0500, Mark Khemma wrote:
Hello,
I don't know if this is possible (because my pd development skills are null), but is there a way for you developers to code a specific box which the sliders/bangs/etc could be set in so that when you look at the parent abstraction, it will look exactly like how you set it up in the child rather than appearing all scrunched up? The box could set the pixel dimensions of the parent object in some way, and things that the user didn't want to show in the parent could be left outside of the box. If it could be done then the pd-design/layout would look much cleaner and much more flexible. I hope this makes sense to more than just me. -Mark .K
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
Hi,
for me it would be the easiest to have the part of the subpatch drawn that starts on the upper left corner and ends at the most right positioned displayable object and the lowest displayable object. The render size could be 1 on 1, if the parent text is larger than this the rest ist filled up with white. This solution would prevent doing all the ratio-calculating stuff for the developer side and the quite ennoying fine-tuning for the patch-builder.
cheers Michael
PS. at the moment I think of a very simple application that moves all objects that cannot be displayed on parent to the upper left corner (excpet x-position of inlets and outlets). So it could clean up the patch for displaying and is really easy done on the pd-files.
PPS: GOGOP rocks for modular control-patch-development
Am Mon, 2003-06-23 um 21.10 schrieb Miller Puckette:
Good idea... there could be some new "frame" object, which, if you had one in a patcher, would make the parent morph into a panel containing whatever was in the frame. This would make it easy to throw comments around too.
One slight complication is how the parent text should be dealt with (such as "pd my-graphic-subpatch"). If that text is larger than the box, I suppose the thing is just to extent the right edge of the box to hold the text.
Perhaps needless to say, the reason I've held off on doing something like this so far is fear of doing it wrong and being stuck keeping everything compatible. The good news is, that with the current scheme, the "frame" could just default to the whole window area so that I could introduce the frame in an easy-to-manage, backward-compatible way.
cheers Miller
On Mon, Jun 23, 2003 at 01:22:44PM -0500, Mark Khemma wrote:
Hello,
I don't know if this is possible (because my pd development skills are null), but is there a way for you developers to code a specific box which the sliders/bangs/etc could be set in so that when you look at the parent abstraction, it will look exactly like how you set it up in the child rather than appearing all scrunched up? The box could set the pixel dimensions of the parent object in some way, and things that the user didn't want to show in the parent could be left outside of the box. If it could be done then the pd-design/layout would look much cleaner and much more flexible. I hope this makes sense to more than just me. -Mark .K
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
Miller Puckette mpuckett@man104-1.ucsd.edu wrote:
Good idea... there could be some new "frame" object, which, if you had one in a patcher, would make the parent morph into a panel containing whatever was in the frame. This would make it easy to throw comments around too.
I like the frame idea. While in my earlier GOP patches, I fiddled a long time to arrange everything so that it displays usefully, I now just put a canvas object inside the GOP patch, then arrange everything on top of that and put the logic in a single pd-subpatch. Then I resize the GOP in the parent to fit the canvas' size.
Now with your proposed frame object, the frame would take the place of the canvas-object, resizing wouldn't be necessary and I would not need that subpatch with inlets/outlets anymore. Great idea.
On a related topic: I never quite managed to use the data structure graphical objects combined with GOP correctly in a pd-subpatch. As soon as I turn on graph-on-parent in a data structure display subpatch, the resulting grey box on the parent gets really big, I mean it gets *huge* and cannot be resized. Does anyone here know what I'm doing wrong?? Or do data structures don't play well with see-through GOPs?
(sorry for the long lines, I'm forced to use my provider's netmail software currently, that's also why I cannot send an example patch)
Frank Barknecht _ ___footils.org_
Hello
I apologize for posting this in the [PD] list, but actually I subscribed to the [alsa-user] mailing-list. Unfortunately I can only see their messages, and I can't post anything.
The problem is I can't unsubscribe (I tried the body message 'unscubscribe mail@anywhere.xxx' but I still receive messages)
Does anyone know about unsubscribing [alsa-user] ? or the mail adress of an administrator ?
I just want to re-subscribe with another mail adress ...
Thanks, and sorry again
On Mon, 23 Jun 2003, Miller Puckette wrote:
Good idea... there could be some new "frame" object, which, if you had one in a patcher, would make the parent morph into a panel containing whatever was in the frame. This would make it easy to throw comments around too.
Do you think it would be possible to nest "frames" within frames? so say you create an graphical adsr subpatch which has vsliders set next to each other. Then you create another patch (that is also set for GOP)which takes an the graphical adsr for both left and right speakers and say add a graphical filter to it as well to make one large graphical patch.
| | | __gadsr___________ __gadsr___________ filter_ | | | # # # # | | # # # # | |0 0 | | | | # # # # | | # # # # | | | | | | # # # # | | # # # # | |0 0 | | | |_#_#__#____#____| |_#_#_ #____#____| |_____| | | left right lp/hp | |_______________________________________________________|
So I suppose if the frame object could fixed the pixel dimensions of the subpatch on the parent then nestings frames could be possible and not bunch up the graph like it does now.
god I wish I had time to help develop pd!! -Mark .k
One slight complication is how the parent text should be dealt with (such as "pd my-graphic-subpatch"). If that text is larger than the box, I suppose the thing is just to extent the right edge of the box to hold the text.
Perhaps needless to say, the reason I've held off on doing something like this so far is fear of doing it wrong and being stuck keeping everything compatible. The good news is, that with the current scheme, the "frame" could just default to the whole window area so that I could introduce the frame in an easy-to-manage, backward-compatible way.
cheers Miller
On Mon, Jun 23, 2003 at 01:22:44PM -0500, Mark Khemma wrote:
Hello,
I don't know if this is possible (because my pd development skills are null), but is there a way for you developers to code a specific box which the sliders/bangs/etc could be set in so that when you look at the parent abstraction, it will look exactly like how you set it up in the child rather than appearing all scrunched up? The box could set the pixel dimensions of the parent object in some way, and things that the user didn't want to show in the parent could be left outside of the box. If it could be done then the pd-design/layout would look much cleaner and much more flexible. I hope this makes sense to more than just me. -Mark .K
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
Hallo, julien.breval@tremplin-utc.net hat gesagt: // julien.breval@tremplin-utc.net wrote:
I apologize for posting this in the [PD] list, but actually I subscribed to the [alsa-user] mailing-list. Unfortunately I can only see their messages, and I can't post anything.
The problem is I can't unsubscribe (I tried the body message 'unscubscribe mail@anywhere.xxx' but I still receive messages)
Does anyone know about unsubscribing [alsa-user] ? or the mail adress of an administrator ?
Almost all modern mailing lists use the Mailman software for handling subscriptions. ALSA does, pd-* do. With Mailman lists you can just take a look at the header of any list mail. You will find all needed info as "List-*"-header. For example, pd-list has these headers:
<mailto:pd-list-request@iem.at?subject=subscribe>
<mailto:pd-list-request@iem.at?subject=unsubscribe>
Frank Barknecht _ ______footils.org__