Piotr Majdak wrote:
Hi!
IOhannes m zmoelnig wrote:
but: whitespaces in filenames should be avoided anyhow on windows (the only place where i stumble across whitespaces now and then) you can use those weird "blabla~1.wav"-like filenames instead.
I think you refer to the good-old-DOS-days. They're over now ;-)
are they really ? the ~1.files still work (although you don't see them so easy anymore)
I think pd should support all characters the OS does. For Win >= 2000 there are some special characters like ,'+-; white space and some more. /:*?"<>| are not allowed.
But I know it's hard to implement keeping backwards compatibility to old patches and/or externals...
i don't think that this is the main reason for not allowing some more characters. if you allow backslash as an escaping character in pd, you will get into serious problems when windows users try to load "C:\files\patch.pd", or should it read "C:\Program\ Files\patch.pd" ? what does this mean ??
and windowsers will immediately start using backslash as directory delimiter, while unixers will use it as escape.
but i am really starting to talk too much about things i know too little about....
sorry for all the noise
mfg.a.sdr IOhannes