notion of Pd's start location. I wouldn't mind if all those cases would be changed to relative-to-patch.
or a [getdir] in vanilla
miller?
m
On Tue, Mar 19, 2013 at 7:11 PM, Roman Haefeli reduzent@gmail.com wrote:
On Die, 2013-03-19 at 16:59 -0400, me.grimm wrote:
I was just looking at romans old post:
http://www.mail-archive.com/pd-list@iem.at/msg04869.html
did this ever get fixed? In the help->pd help browser->pd msg->msg_and_pd->open_close.pd i see:
"Sometimes you can get relative paths (./, ../, etc.) to work, but usually not. I don't know why..."
the example under it uses [getdir]
there is no vanilla [getdir] right? and i was assuming the manual example above was a vanilla example...
IDK basically im trying to have a vanilla way to do [pd open $1 $2{ and have $2 relative to where ever my patch is sitting.
but maybe im easily missing the obvious something that was addressed since romans 2007 post...
From what I know, the situation is still the same. Many things in Pd are still relative to Pd's start location. The 'open' message to 'pd' is one of them. Also [openpanel] interprets relative paths relative to Pd's start location. There are quite a lot of externals with the same behavior, too. [moocow/readdir] just pops to my mind.
From a user's perspective, this is simply broken, as a patch hasn't any notion of Pd's start location. I wouldn't mind if all those cases would be changed to relative-to-patch.
Roman
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list