Rich E wrote: > When I first posted about this, it was about the recently new ability to > do this: > > [symbol somedir( > | > [openpanel]
I did not know this yet, cool! > But this only works if "somedir" is at "$HOME/somedir" on linux and > "/usr/blahblah/pdir/somedir" on mac. So if my directly layout is > something like "~/patches/somedir", I have to explicitly write in the > message to [openpanel] "/home/myname/patches/somedir". This will only > work on my directly layout, so if it is a patch I'm going to share, I > cannot use this new feature (might I add I really like the feature). > > I was only suggesting that [openpanel]/[savepanel]'s symbol argument has > the patch's current directory appended to it, unless the "~" sign is > used for home, or a full path is given. I think, as Martin suggested, > this is all handled internally with canvas_getdir() and open_via_path(). > > Regarding the normal operation of [openpanel]/[savepanel], i.e. sending > it a bang, I think it would be nice if the last directory navigated to > is remembered, else the $HOME. I think it is quite easy to distinguish between what is a local path and what is an absolute path. these features that you are talking about would make life much easier! I hope they get added. marius. _______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
