[PD] abstraction's knowledge of parent's path
Krzysztof Czaja
czaja at chopin.edu.pl
Fri Nov 8 15:07:24 CET 2002
hi David,
I think there are two reasons for not having 'file...' and
'...path' objects in Pd. One is that nobody is really willing to
write and maintain a spaghetti code. The other is that, outside
of a Windows world, what you need is basically as easy as putting
whatever (eg. ls -t1 *.wav | head -1) into an executable file (eg.
named 'lastwave', eg. placed in a current dir), then putting
[loadbang]->'./lastwave'->[shell] into a patch.
Krzysztof
David Sabine wrote:
...
> When I close and reopen the patch, I'd sure like to be able to look on the
> hard drive for the most recent file, then begin where I left off. Example,
> if "159.wav" was the last file written to the drive, then this new session
> would start at "160.wav".
...
> See, I've been thinking for some time that it would be VERY handy if PD had
> an object available that would allow PD to respond with information about
> the file system. MAX has some objects for this purpose, like;
>
> [absolutepath]
> [filedate]
> [filein]
> [filepath]
> [relativepath]
More information about the Pd-list
mailing list