On Sat, 2007-03-24 at 10:14 +0800, Chris McCormick wrote:
On Fri, Mar 23, 2007 at 11:20:01PM +0100, Roman Haefeli wrote:
On Fri, 2007-03-23 at 10:04 +0100, Steffen wrote:
On 22/03/2007, at 23.41, Roman Haefeli wrote:
When opening patches by sending messages to pd, the path is
On Sun, Mar 25, 2007 at 07:05:59PM +0200, Roman Haefeli wrote:
On Sat, 2007-03-24 at 10:14 +0800, Chris McCormick wrote:
On Fri, Mar 23, 2007 at 11:20:01PM +0100, Roman Haefeli wrote:
On Fri, 2007-03-23 at 10:04 +0100, Steffen wrote:
On 22/03/2007, at 23.41, Roman Haefeli wrote:
On 22/03/2007, at 23.41, Roman Haefeli wrote:
When opening patches by sending messages to pd, the path is
relative to
pd's startup-location. when loading other files (text-, audio-,
data-files etc) the path is set relative to the location of the patch.
since the patch doesn't know, where
On Fri, 23 Mar 2007 23:20:01 +0100
Roman Haefeli [EMAIL PROTECTED] wrote:
i'd like to have the same
opportunity for the [open(-message.
Me too.
Doesn't Pd have some kind of local special variable $cwd or something?,
that would be nice way to unify all filesystem relative things.
hello everyone
this problem is very old, but never solved. that is why i thought, it
would be ok to post it again.
When opening patches by sending messages to pd, the path is relative to
pd's startup-location. when loading other files (text-, audio-,
data-files etc) the path is set relative to
