On 07/01/2013 09:04 AM, IOhannes m zmoelnig wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2013-06-29 15:43, Roman Haefeli wrote:
I don't know any solution off-hand and I also don't know whether Pd was designed with the possibility in mind to read patches with [textfile]. I just want to have it mentioned. And yes, it does break some of my patches (not that this would be a reason not go forward and change Pd's file format).
since my personal preferences for those "," appendices to objects go into the direction of using them for messages that the object itself can understand(e.g. #X obj 100 100 readsf~, open foo.wav; ) i'd rather vote for keeping "meta"-messages (e.g. those that tell the GUI-renderer which color the object should have) separate.
e.g. #X obj 100 100 readsf~; #G width 10;
I second that vote, and also vote to never actually implement #G: * as I've never seen a request for the feature of having a bunch of differently colored object boxes in a patch * since specifying width doesn't solve the problem of making arbitrary line breaks in comments without using a semicolon * since specifying width can be done with a method for comments * since the number of classes that create inside an object box and which would benefit from resizable widths can be counted on no fingers * since specifying gui props with commas separated methods in an object box allows the _user_ to specify both gui and state properties without lifting their hands from the keyboard:
[vsl, label look_ma_no_mouse, label_pos 20 20, size...]
-Jonathan
oh btw, i really don't see a reason to use cryptic 'f' selectors, when we could use meaningful names like "width".
fgamsdr IOhannes
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/
iEYEARECAAYFAlHRfl0ACgkQkX2Xpv6ydvRhVwCg6Rc8o/AGHKAmYAjOxuxXE0SG uEoAoLe4cy6BEikkMIsytCFRFi294cPm =WYqL -----END PGP SIGNATURE-----
Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev