Segmenting, coloring, and/or hiding the patch cords aren't going to magically make every patch clear and easy to follow. Once a patch gets to a certain level of density it is time to rethink how the whole thing is structured or find a different tool. Abstractions and subpatches help quite a bit, but at a certain point going 11 windows deep to find or fix something is nearly as ridiculous as cramming everything into a single spider webbed window.
On Dec 5, 2007 1:07 PM, Mathieu Bouchard <[EMAIL PROTECTED]> wrote: > On Tue, 4 Dec 2007, Chris McCormick wrote: > > > I think the key point to take from the whole discussion is that Max/MSP > > users have a choice, whilst under Pd we have no choice. It's all very > > well justifying how great it is to not have patch chords, but the lack > > of that feature/bug definately annoys some [potential] users and puts > > them off Pd. If the people want it, why not give it to them? > > Because it's easier to write a condescending justification for the lack of > segmented patchcords than to write the code for segmented patchcords. > > _ _ __ ___ _____ ________ _____________ _____________________ ... > | Mathieu Bouchard - tél:+1.514.383.3801, Montréal QC Canada > > _______________________________________________ > [email protected] mailing list > UNSUBSCRIBE and account-management -> > http://lists.puredata.info/listinfo/pd-list > >
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
