[PD] Max/MSP vs. Pd [was: shadow patch bug]

[Frank Barknecht]

Hi,
nihil hat gesagt: // nihil wrote:

> 
> > With graph-on-parent....
> 
> If the issue is expanding the user base, then perhaps
> names for things could be a little clearer. For
> example, Graph On Parent; I'm not a great programmer,
> but I can get by. However, I still have no idea from
> the name what GOP might be....

This is a feature, that is really best explained by an example, and as
it's quite a young feature, it hasn't been used much yet. 

You could download my "angriff" abstraction from footils.org to see
GOP in full effect everywhere. Basically it's just a see-through
feature for subpatches and abstractions, where (only) the GUI objects
are visible from the surrounding patch. Therefore the name: 
"Graph(ical user elements visible) On (the) Parent (patch)"

Or see the attached ezdac~ patch with test, that I now use in all my
patches.

ciao
-- 
 Frank Barknecht                               _ ______footils.org__
-------------- next part --------------
#N canvas 0 0 450 300 10;
#X obj 154 152 ezdac~;
#X obj 193 75 osc~ 440;
#X connect 1 0 0 0;
#X connect 1 0 0 1;
-------------- next part --------------
#N canvas 304 280 450 300 10;
#X obj 224 205 dac~;
#X obj 224 32 inlet~;
#X obj 259 60 inlet~;
#X obj 318 69 tgl 16 0 \$0-d \$0-d DSP 0 -6 1728 8 -260818 -123526
-33289 0 1;
#X msg 318 93 \; pd dsp \$1;
#X obj 69 186 hsl 64 16 0 1 0 0 \$0-v \$0-v volume -2 -6 1728 8 -260818
-123526 -1 3100 1;
#X obj 269 108 r \$0-v;
#X obj 262 206 outlet~;
#X obj 166 206 outlet~;
#X obj 357 28 r pd;
#X obj 357 52 route dsp;
#X obj 269 155 line~;
#X msg 269 132 \$1 10;
#X obj 259 180 *~;
#X obj 224 180 *~;
#X connect 1 0 14 0;
#X connect 2 0 13 0;
#X connect 3 0 4 0;
#X connect 6 0 12 0;
#X connect 9 0 10 0;
#X connect 10 0 3 0;
#X connect 11 0 13 1;
#X connect 11 0 14 1;
#X connect 12 0 11 0;
#X connect 13 0 0 1;
#X connect 13 0 7 0;
#X connect 14 0 0 0;
#X connect 14 0 8 0;
#X coords 0 0 1 1 90 55 1;