SourceForge.net wrote:
...and periods of course. Part of the problem is that odd characters in filenames can get mangled by intervening software, as in the case of Pd, where you can't use { } or \ in a filename because you can't enter it, you get a message like "keycode 92: dropped" instead.
well, you can navigate to the a weird filename via the [openpanel] browser...
Of course you're right. In my experience of cross-platformity though it's best to use underscores instead of spaces, never start a filename with a number, and otherwise use only alphanumeric characters in file names. It just _always_ works that way.
and don't forget: never exceed 8.3
how about using all of the arguments as the path name? That way you can
personally i think this is a bad idea. we should rather spend time in making it easy to create symbols with spaces than doing ugly hacks to create the illusion of symbols with spaces.
i think it is by design, that a message [open ../sound/bell.aiff 0 200 4 2 b( to [readsf~] will _not_ attempt to open a file "../sound/bell.aiff 0 200 4 2 b"
and iirc, my initial patch for [openpanel]/[savepanel] already included the very functionality (without the list weirdness). this part was not accepted by miller (probably because it gives you zero extra benefit over what you can do now) my idea was to be able to specify additional things like a glob-pattern. which i find more useful than spaces.
here's my original patch: http://sourceforge.net/tracker/index.php?func=detail&aid=1244757&gro...
mfga.sdr IOhannes