I'm on pd vanilla windows version 0.42-5.
I've a patch that relies heavily on file IO abstractions (sitting happily in the 'extra' folder), which are invoked by the main patch which until recently has been located in a different folder. These abstractions start looking for certain files and folders via 'makefilename' into the 'textfile' object like...
|read ../../$1/$2.txt(
I tried to make an abstraction (also located in 'extra') that was GOP. It used 3 instances of the file IO abstraction, where one instance was visible on parent and the 2 others hidden.
What I found was that the hidden abstractions began their relative path in the 'extra' folder as they should...
|read ../../$1/$2.txt( ... ...worked for the hidden only.
...but the VISIBLE abstractions began their relative path search in the PARENT'S patch folder. Such that...
|read ../$1/$2.txt( ... ...worked for the visible only.
Can anybody replicate this bug/suggest a workaround?
(The paths must be relative, as I need to port this around)
Thanks in advance as always, John.
Anybody?
I'm on pd vanilla windows version 0.42-5.
I've a patch that relies
heavily on file IO abstractions (sitting happily in the 'extra' folder), which are invoked by the main patch which until recently has been located in a different folder. These abstractions start looking for certain files and folders via 'makefilename' into the 'textfile' object like...
|read
../../$1/$2.txt(
I tried to make an abstraction (also located in 'extra')
that was GOP. It used 3 instances of the file IO abstraction, where one instance was visible on parent and the 2 others hidden.
What I found was that the
hidden abstractions began their relative path in the 'extra' folder as they should...
|read ../../$1/$2.txt( ... ...worked for the hidden
only.
...but the VISIBLE abstractions began their relative path search in
the PARENT'S patch folder. Such that...
|read ../$1/$2.txt( ... ...worked
for the visible only.
Can anybody replicate this bug/suggest a
workaround?
(The paths must be relative, as I need to port this
around)
Thanks in advance as always, John.
Another bump.
I do believe this is a bug, no?
Cheers, John.
----- Original Message ----
From: saint saintidle@yahoo.com To: saint saintidle@yahoo.com; pd list pd-list@iem.at Sent: Mon, 26 April, 2010 14:59:31 Subject: Re: Relative path behaviour strange in GOP abstractions
Anybody?
I'm on pd vanilla windows version 0.42-5.
I've a patch that relies
heavily on file IO abstractions (sitting happily in the 'extra' folder), which are invoked by the main patch which until recently has been located in a different folder. These abstractions start looking for certain files and folders via 'makefilename' into the 'textfile' object like...
|read
../../$1/$2.txt(
I tried to make an abstraction (also located in 'extra')
that was GOP. It used 3 instances of the file IO abstraction, where one instance was visible on parent and the 2 others hidden.
What I
found was that the hidden abstractions began their relative path in the 'extra' folder as they should...
|read ../../$1/$2.txt( ...
...worked for the hidden only.
...but the VISIBLE abstractions
began their relative path search in the PARENT'S patch folder. Such that...
|read ../$1/$2.txt( ... ...worked
for the visible only.
Can anybody replicate this bug/suggest a
workaround?
(The paths must be relative, as I need to port this
around)
Thanks in advance as always, John.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
saint wrote:
Another bump.
I do believe this is a bug, no?
dunno.
please send the output when using Pd with "-verbose".
provide information about the pd-version and your platform.
and file a bug report at the sourceforge site.
mgsdft IOhannes