<table cellspacing="0" cellpadding="0" border="0"><tr><td valign="top" style="font: inherit;"><div> Regarding ambiguity, I&#39;d say a good rule of thumb is that one should be able to draw the patch on a sheet of paper without introducing any ambiguity.  So things like inlet tool tips and cord shaking don&#39;t resolve ambiguity in the visual representation of the patch, though they may be useful in other ways.</div></td></tr></table>            <div id="_origMsg_">
                <div style="font-family:arial, helvetica, sans-serif:font-size:10pt">
                    <br />
                    <div style="font-family:times new roman, new york, times, serif;font-size:12pt">
                        <font size="2" face="Tahoma">
                            <hr size="1">
                            <b>
                                <span style="font-weight:bold;">From:</span>
                            </b>
                            Andy Farnell &lt;padawan12@obiwannabe.co.uk&gt;;                            <br>
                            <b>
                                <span style="font-weight:bold:">To:</span>
                            </b>
                            Jonathan Wilkes &lt;jancsika@yahoo.com&gt;;                                                     <br>
                            <b>
                                <span style="font-weight:bold:">Cc:</span>
                            </b>
                             &lt;pd-list@iem.at&gt;;                                                                             <br>
                            <b>
                                <span style="font-weight:bold:">Subject:</span>
                            </b>
                            Re: [PD] FLOSS book Lists chapter                            <br>
                            <b>
                                <span style="font-weight:bold;">Sent:</span>
                            </b>
                            Sat, Feb 19, 2011 4:51:51 PM                            <br>
                            </font>
                            <br>
                            <table cellspacing="0" cellpadding="0" border="0">
                                <tbody>
                                    <tr>
                                        <td valign="top" style="font:inherit;">On Fri, 18 Feb 2011 17:48:21 -0800 (PST)<BR>Jonathan Wilkes &lt;<a ymailto="mailto:jancsika@yahoo.com" href="javascript:return">jancsika@yahoo.com</a>&gt; wrote:<BR><BR><BR>&gt;&nbsp; I guess I'm limiting it to unwanted ambiguities that <BR>&gt; _cannot_ be resolved by looking at the patch.&nbsp; <BR><BR>Maybe we could look at it in another way, and ask what information<BR>is hidden in a patch? Most we have mentioned so far:<BR><BR> 1) Values of IEM GUIs<BR> 2) Creation order of cables<BR> 3) Differing implementations of objects<BR> 4) Creation order of objects<BR><BR>In that scheme, obscured things like inlets behind<BR>wires would count. Using real fancy graphics in a modern<BR>interface maybe some use of transparency can be made.<BR>I always liked the VST hosts where you could "shake"<BR>cables.<BR><BR>This made me think of a help to revealing (2). If an interface<BR>were
 to have hover-over tooltips, as has been discussed at times<BR>for outlets/inlets, then a cable could reveal its creation<BR>order on hover.<BR><BR>It wouldn't obviate triggers, but would make a nice debugging<BR>feature.<BR><BR>a.<BR><BR>-- <BR>Andy Farnell &lt;<a ymailto="mailto:padawan12@obiwannabe.co.uk" href="javascript:return">padawan12@obiwannabe.co.uk</a>&gt;<BR></td>
                                    </tr>
                                </tbody>
                            </table>
                    </div>
                </div>
            </div>
<br>