I think it is really a personal preference then anything else and I was thinking that it could be a nice option. I have used segmented patch cords for a while and I never had a problem with the patch being less readable because the patch cord could be lined up besides another and organized more easily to make the patch cleaner. Also another feature that would be useful that I use in MAX is colored patch cords. This helps organize different types of data. 
<br><br><br><br><div class="gmail_quote">On Dec 4, 2007 10:09 AM, marius schebella &lt;<a href="mailto:marius.schebella@gmail.com">marius.schebella@gmail.com</a>&gt; wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
segmented patchcords can make patches less readable, but most of the<br>time they make patches more readable, and that is when you use so many<br>unsegmented cords that they hide the objects. also when you want to<br>connect an object at the bottom of the patch to an object at the top,
<br>then you can lay the cord at the outside of the patch to make the<br>~feed-back.<br>you don&#39;t want patchcords in situations where it is not clear anymore<br>which cord is going where.<br>a big problem in max is that there is no undo for segmented patchcords.
<br>once segmented, you can only delete them and redraw to make them not<br>segmented. that might be one of the new features of max 5... as well as<br>the infinite number of undos. (true?)<br>marius.<br><br>_______________________________________________
<br><a href="mailto:PD-list@iem.at">PD-list@iem.at</a> mailing list<br>UNSUBSCRIBE and account-management -&gt; <a href="http://lists.puredata.info/listinfo/pd-list" target="_blank">http://lists.puredata.info/listinfo/pd-list
</a><br></blockquote></div><br><br clear="all"><br>-- <br>Joe Reinsel<br>Artist in Residence, Universidad San Francisco de Quito, Ecuador<br><br><a href="http://www.linkedin.com/in/joereinsel">http://www.linkedin.com/in/joereinsel
</a>