[PD-dev] width control breaks parsing with [textfile]

[Roman Haefeli]

On Mon, 2013-07-01 at 15:04 +0200, IOhannes m zmoelnig wrote:
> 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;

Those uses would not interfere with each other as your example would
actually read:

#X obj 100 100 readsf~\, open foo.wav;

(mind the backslash)[1].

Also, the escaped commas do not cause any troubles for Pd file parsing.
It's only the new non-escaped commas that do.


> ) 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;

Yeah, why not? This wouldn't break anything, at least.

> oh btw, i really don't see a reason to use cryptic 'f' selectors, when
> we could use meaningful names like "width".

Agreed.

What is Miller's stance on this?

Roman