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.
<br><br><div class="gmail_quote">On Dec 5, 2007 1:07 PM, Mathieu Bouchard <<a href="mailto:matju@artengine.ca">matju@artengine.ca</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Tue, 4 Dec 2007, Chris McCormick wrote:<br><br>> I think the key point to take from the whole discussion is that Max/MSP<br>> users have a choice, whilst under Pd we have no choice. It's all very
<br>> well justifying how great it is to not have patch chords, but the lack<br>> of that feature/bug definately annoys some [potential] users and puts<br>> them off Pd. If the people want it, why not give it to them?
<br><br></div>Because it's easier to write a condescending justification for the lack of<br>segmented patchcords than to write the code for segmented patchcords.<br><div><div></div><div class="Wj3C7c"><br> _ _ __ ___ _____ ________ _____________ _____________________ ...
<br>| Mathieu Bouchard - tél:+1.514.383.3801, Montréal QC Canada</div></div><br>_______________________________________________<br><a href="mailto:PD-list@iem.at">PD-list@iem.at</a> mailing list<br>UNSUBSCRIBE and account-management ->
<a href="http://lists.puredata.info/listinfo/pd-list" target="_blank">http://lists.puredata.info/listinfo/pd-list</a><br><br></blockquote></div><br>