<br><br><div class="gmail_quote">On Mon, Jun 4, 2012 at 2:52 AM, IOhannes m zmoelnig <span dir="ltr"><<a href="mailto:zmoelnig@iem.at" target="_blank">zmoelnig@iem.at</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<div class="im"><br>
On 2012-06-03 22:30, s p wrote:<br>
> That's a very good point, ... it's a good idea to specify GUI<br>
> infos, for better interoperability, but it should be explicitly<br>
> said that this is optional information<br>
<br>
</div>gui information (e.g. spatial layout) is not always optional,<br>
sometimes it is mandatory (as in: the patch's behaviour depends on the<br>
layout)<br><br></blockquote><div><br></div><div>The spatial layout dictates what connections are made, but in the .pd, doesn't <a href="http://puredata.info/docs/developer/PdFileFormat#r32">this remark</a> (from <a href="http://puredata.info">puredata.info</a>'s docs on connect) still hold true?:</div>
<div><br></div><div>"Objects are virtually numbered in order of appearance in the file, starting from zero. Inlets and outlets of the objects are numbered likewise."</div><div><br></div><div>What I'm trying to say is, the patch is reconstructed based on the order of elements within the .pd file (the proposal suggests using id's in .json). I'm I correct in assuming that spatial location is used by pd to write the patch, but its only use when reading the patch is to decide where it should be drawn?</div>
</div>