Bugs item #2865402, was opened at 2009-09-23 20:31
Message generated for change (Comment added) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2865402&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: pd-devel
>Group: v0.43
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
>Assigned to: Hans-Christoph Steiner (eighthave)
Summary: expr
Initial Comment:
expr and expr~ dont load correctly with pd-0.43.0-extended for mac osx.
----------------------------------------------------------------------
>Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-04-13 00:08
Message:
This is fixed in recent nightly builds.
http://autobuild.puredata.info/auto-build/latest/
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2865402&group_…
Bugs item #2879422, was opened at 2009-10-14 20:14
Message generated for change (Settings changed) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2879422&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Pending
Resolution: None
Priority: 5
Private: No
Submitted By: João Pais (jmmmp)
Assigned to: Nobody/Anonymous (nobody)
Summary: general audio meter
Initial Comment:
audio meters are very nice, but not 100% helpful. the sound level is connected to the actual sound volume of the system, and not to pd dac~ output (independently of how many there are). wouldn't the latter make more sense?
----------------------------------------------------------------------
>Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-04-12 23:43
Message:
I am not sure which audio meters you mean. As far as I know, the meters in
the Pd window are related to dac~ output, but I could be wrong.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2879422&group_…
Bugs item #2890661, was opened at 2009-11-02 06:59
Message generated for change (Settings changed) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2890661&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: pd-extended
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: georg (fricklr)
Assigned to: Miller Puckette (millerpuckette)
>Summary: dsp on/off shortcuts crash pd winxp and "use callbacks"
Initial Comment:
using the shortcuts ctrl+/ or ctrl+. crashes pd
tested on winxp ext 0.42.5 an 0.43
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-01-27 18:02
Message:
There might be an issue related to "use callbacks", since that is new and
relatively untested. Does the same crash happen for you when using
Pd-vanilla?
----------------------------------------------------------------------
Comment By: georg (fricklr)
Date: 2010-01-27 03:09
Message:
i found out it crashes only if "use callbacks" is on maybe really just an
issue with my driver
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-01-26 18:36
Message:
I can't reproduce this on WinXP fully updated using Pd-extended
0.42.5-20100120 or Pd-devel 0.43.0-20100120
I am guessing it might be an issue with your audio interface or driver.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2890661&group_…
Bugs item #2886083, was opened at 2009-10-25 15:40
Message generated for change (Comment added) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2886083&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
>Category: pd-extended
>Group: v0.42
>Status: Pending
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: gnd gnd (gndgnd)
>Assigned to: Hans-Christoph Steiner (eighthave)
Summary: Pd-extended doesnt install under Ubuntu 9.10
Initial Comment:
The 9.10 version of Ubuntu is out in 4 days from now. I tried installing pd-extended for 9.04 version but it misses dependencies - libmagick++1. In 9.10 there is libmagick++2. If i force the install PD runs OK, GEM doesnt load because opf missing libmagick++1 libraries. However if i compile GEM from sources, it is OK. Please fix the dependencies issue for Ubuntu 9.10 and make a .deb package.
----------------------------------------------------------------------
>Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-04-12 23:40
Message:
The font issue has been fixed, plus there are Ubuntu Karmic 9.10 nightly
builds now, try one:
http://autobuild.puredata.info/auto-build/latest/
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2009-10-27 16:44
Message:
Hey, this is great! You should post it to the pd-list and/or forum for
other users. I'll try it once I upgrade my machine.
As for the bitstream font issue, that will be fixed in Pd-extended 0.42.5.
If you want to try fixing it in your package, look in pd/src/u_main.tk and
pd/src/s_main.c and replace "Bitstream Vera Sans Mono" with "DejaVu Sans
Mono" (I think, double-check that). Then edit
packages/linux_make/debian/control to change the package dependency.
----------------------------------------------------------------------
Comment By: gnd gnd (gndgnd)
Date: 2009-10-27 16:32
Message:
i think this will be of interest to you:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=461308
"
please remove ttf-bitstream-vera, it is completely superseeded by its
improved version named ttf-dejavu.
"
----------------------------------------------------------------------
Comment By: gnd gnd (gndgnd)
Date: 2009-10-27 16:19
Message:
geez, the last two comments are mine - i forgot to login ..
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2009-10-27 16:18
Message:
ah and one more thing - i had to manually install ttf-bitstream-vera
because it isnt in Ubuntu 9.10
is it possible to make pd use sth else then vera ?
The package is uninstalable like this because of the missing package.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2009-10-27 16:04
Message:
hello, I compiled it and you can find the package here:
http://gondapeter.sk/files/Pd-0.41.4-extended.deb
I did one change in the code because without it i couldnt compile GEM:
http://lists.puredata.info/pipermail/gem-dev/2009-10/004211.html
but i think its not important ..
cheers...
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2009-10-25 21:59
Message:
I don't have access to a 9.10 machine yet. It should be pretty easy to
build there tho. Try it out, and we can post your build for others. FIrst
install the required packages:
http://puredata.info/docs/developer/Debian
Then build the pd-extended package:
http://puredata.info/docs/developer/BuildingPdExtended
If you have any troubles, try irc://irc.freenode.net/dataflow and/or the
pd-dev list: http://puredata.info/community/lists
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2886083&group_…
Bugs item #2929298, was opened at 2010-01-10 09:17
Message generated for change (Comment added) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2929298&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: pd-extended
>Group: v0.42
>Status: Pending
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: max (maxn)
Assigned to: Hans-Christoph Steiner (eighthave)
Summary: 10.6 + Audio on + Gem = pd hangs
Initial Comment:
turning audio on, opening a gem window and plugging in headphones Pd-0.43.0-devel-20091215 and Pd-0.42.5-extended-20091222 on 10.6 will make Pd hang. See attached patch.
----------------------------------------------------------------------
>Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-04-12 23:38
Message:
I am pretty sure this has been fixed by updating the portaudio code, try a
recent nightly build:
http://autobuild.puredata.info/auto-build/latest/Pd-0.42.5-extended-macosx1…
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2929298&group_…
Bugs item #2957058, was opened at 2010-02-23 01:11
Message generated for change (Settings changed) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2957058&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Open
Resolution: None
Priority: 7
Private: No
Submitted By: Jonathan Wilkes (jancsika1)
Assigned to: Nobody/Anonymous (nobody)
Summary: pointer to [route symbol]-[print] crashes pd
Initial Comment:
[namecanvas foo]
[traverse foo, bang(
|
[pointer]
|
[route symbol]
|
[print]
1) a pointer message is erroneously routed as a symbol
2) this crashes Pd
3) [route pointer] doesn't route a pointer
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-04-12 23:31
Message:
There are a number of "types" in pd:
[symbol] [float] [list] [bang] [pointer]
[trigger symbol float list bang pointer]
[route] does [route symbol float list bang] so it is inconsistent that
[route pointer] would not route the "pointer" atom type, and instead route
based on the "pointer" as a symbolic selector. That right there is a bug
IMHO.
As for the crash, I could also reproduce it using Pd version
0.42.5-extended-20100410 or pd-gui-rewrite 0.43 on Mac OS X 10.5.8/Intel.
The crash is actually in the [print], not the [route]. When I remove the
[print], it doesn't crash.
----------------------------------------------------------------------
Comment By: Jonathan Wilkes (jancsika1)
Date: 2010-03-01 16:58
Message:
Oops, I didn't realize that when lists get distributed the atoms are
interpreted, just like the [list] object classes. E.g., I though the
following would output an error but it works fine:
[list one two(
|
[select symbol]
You know, since [route list] has different behaviors depending on whether
the first element is a float or symbol, the same could be done for [route
pointer]-- strip the selector off of anythings, pass gpointer messages
through unchanged. That way there is at least some consistency, in the
sense that the selector is always being matched.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2010-03-01 13:41
Message:
Hi Jonathan,
that's not really what I meant. You can use pointers in a list-message of
course ("list <pt1> <pt2> <pt3>") or [pack/unpack] many of them and so on.
Even [pipe] works with pointers and lists of pointers now.
But when you strip a lone pointer from it's selector then the pointer
itself could become the selector like: "list set 2"->[route list] becomes
"set 2" and this will call the "set"-method of the next object. If this is
a message box it will be set to "2".
But with a pointer you'd get "pointer <pt>" -> [route pointer] -> "<pt>",
so now it would try to use some "<pt>" method, which is probably
undefined. BTW: I guess that's what leads to the crash here. I think
selectors must be symbols.
So to make use of the pointless pointer (pun intended :) one probably has
to attach a selector again with [list] or [pointer] or something.
Anyway I guess we're now talking about the usefulness of route's
implementation, which is debatable and led to the development of several
nicer variants in GridFlow.
----------------------------------------------------------------------
Comment By: Jonathan Wilkes (jancsika1)
Date: 2010-03-01 12:48
Message:
Hi Frank,
Is it really useless? If you send a gpointer through the following,
it works:
[rewind $1(
|
[pointer]
That's a meta message consisting of a symbol-atom and a pointer-atom. And
the pointer atom gets sent successfully to the right inlet. However, I
can't currently find a way to test sending a single pointer-atom to the
left inlet. (If you try to strip it with list trim you always end up with
the "list" selector.)
----------------------------------------------------------------------
Comment By: Frank Barknecht (fbar)
Date: 2010-03-01 07:16
Message:
I meant to write:
useless just like a "gem_state" stripped of its *selector*.
----------------------------------------------------------------------
Comment By: Frank Barknecht (fbar)
Date: 2010-03-01 07:15
Message:
First I have to correct myself: The selector of a pointer-message is indeed
"pointer", as can be seen with zexy's new rawprint object or by exploiting
the error message of an object like [select] when sent a pointer which is
"no method for 'pointer'".
So "route pointer" could or maybe should indeed route a "pointer"
meta-message just like it can route a "gem_state" message However as
[route] also strips off the selector you would be left with just the
pointer that is more or less useless just like a "gem_state" stripped of
its pointer cannot be used in the gem chain anymore.
----------------------------------------------------------------------
Comment By: Jonathan Wilkes (jancsika1)
Date: 2010-02-28 22:11
Message:
(pointer) with the g missing is what is specified in m_atom.c for
displaying a pointer atom. So I assume there's a difference between a
pointer message and a pointer atom.
There are two reasons to [route] pointer messages.
1) Didactic-- [route] is a common object people use to learn about the
behavior of messages in Pd. It would be nice to show all the predefined
message types going to different outlets, which can't currently happen
because [route] doesn't differentiate between pointers and anythings.
2) Because anythings and pointers aren't differentiated, this diminishes
the flexibility of an abstraction inlet. So a data-structure related
abstraction that wants to take "set," "flush", "clear", and pointer
messages to the left inlet and do something else with the right inlet has
to add an additional inlet. The [pointer] object can differentiate between
a pointer and "rewind," for example. An abstraction should be able to have
the same flexibility.
----------------------------------------------------------------------
Comment By: Frank Barknecht (fbar)
Date: 2010-02-25 11:37
Message:
Yep, a gpointer is not simply a message composed of "pointer" and some
actual pointer blob. I don't know the exact details myself and don't really
understand the source code, but they seem to be something very "special"
just like signals are. As you know, [print] shows them as a not very
helpful "(gpointer)", but if you pass a pointer to [list prepend set]-[list
trim] and into a message box: There pointers show up as "(pointer)" with
the "g" missing. Anyway don't bother trying [route (pointer)], it doesn't
work either. :)
In the end we probably have to accept that gpointers don't have a
"printable" selector, just like audio signals don't have one. Introducing a
print- and routable selector as "pointer" may be useful, or maybe it's not,
as some people may already use "pointer" as a meta-message in their
patches, for example to handle mouse-"pointer" events or so.
----------------------------------------------------------------------
Comment By: Jonathan Wilkes (jancsika1)
Date: 2010-02-25 00:54
Message:
Hm, I'm just not understanding something about gpointers-- I'd just assumed
when you send a pointer message it consists of the selector "pointer"
followed by the gpointer itself (gridflow's [display] seems to confirm
this). But clearly something else is going on because [route pointer]
doesn't currently work for gpointers, nor will [pointer] accept a gpointer
that has passed through [pointer $1( (though [route] will, without
crashing, and output a usable gpointer that has the selector "list").
It also seems like "pointer 1 2 3" is an unchecked case of "bad arguments
to message 'pointer'". So I guess I'm saying I agree that [route pointer]
should route according to the selector "pointer", I just don't understand
why a gpointer wouldn't match under those conditions.
----------------------------------------------------------------------
Comment By: Frank Barknecht (fbar)
Date: 2010-02-23 03:40
Message:
Hi Jonathan,
I raised the priority as crashes are really serious. I disagree with your
item 3), though. [route pointer] should not route GPointers, but
meta-messages starting with the symbol "pointer" e.g.
[pointer 1 2 3(
|
[route pointer]
|
It does that just fine.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2957058&group_…
Bugs item #2957058, was opened at 2010-02-23 01:11
Message generated for change (Comment added) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2957058&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Pending
Resolution: None
Priority: 7
Private: No
Submitted By: Jonathan Wilkes (jancsika1)
Assigned to: Nobody/Anonymous (nobody)
Summary: pointer to [route symbol]-[print] crashes pd
Initial Comment:
[namecanvas foo]
[traverse foo, bang(
|
[pointer]
|
[route symbol]
|
[print]
1) a pointer message is erroneously routed as a symbol
2) this crashes Pd
3) [route pointer] doesn't route a pointer
----------------------------------------------------------------------
>Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-04-12 23:31
Message:
There are a number of "types" in pd:
[symbol] [float] [list] [bang] [pointer]
[trigger symbol float list bang pointer]
[route] does [route symbol float list bang] so it is inconsistent that
[route pointer] would not route the "pointer" atom type, and instead route
based on the "pointer" as a symbolic selector. That right there is a bug
IMHO.
As for the crash, I could also reproduce it using Pd version
0.42.5-extended-20100410 or pd-gui-rewrite 0.43 on Mac OS X 10.5.8/Intel.
The crash is actually in the [print], not the [route]. When I remove the
[print], it doesn't crash.
----------------------------------------------------------------------
Comment By: Jonathan Wilkes (jancsika1)
Date: 2010-03-01 16:58
Message:
Oops, I didn't realize that when lists get distributed the atoms are
interpreted, just like the [list] object classes. E.g., I though the
following would output an error but it works fine:
[list one two(
|
[select symbol]
You know, since [route list] has different behaviors depending on whether
the first element is a float or symbol, the same could be done for [route
pointer]-- strip the selector off of anythings, pass gpointer messages
through unchanged. That way there is at least some consistency, in the
sense that the selector is always being matched.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2010-03-01 13:41
Message:
Hi Jonathan,
that's not really what I meant. You can use pointers in a list-message of
course ("list <pt1> <pt2> <pt3>") or [pack/unpack] many of them and so on.
Even [pipe] works with pointers and lists of pointers now.
But when you strip a lone pointer from it's selector then the pointer
itself could become the selector like: "list set 2"->[route list] becomes
"set 2" and this will call the "set"-method of the next object. If this is
a message box it will be set to "2".
But with a pointer you'd get "pointer <pt>" -> [route pointer] -> "<pt>",
so now it would try to use some "<pt>" method, which is probably
undefined. BTW: I guess that's what leads to the crash here. I think
selectors must be symbols.
So to make use of the pointless pointer (pun intended :) one probably has
to attach a selector again with [list] or [pointer] or something.
Anyway I guess we're now talking about the usefulness of route's
implementation, which is debatable and led to the development of several
nicer variants in GridFlow.
----------------------------------------------------------------------
Comment By: Jonathan Wilkes (jancsika1)
Date: 2010-03-01 12:48
Message:
Hi Frank,
Is it really useless? If you send a gpointer through the following,
it works:
[rewind $1(
|
[pointer]
That's a meta message consisting of a symbol-atom and a pointer-atom. And
the pointer atom gets sent successfully to the right inlet. However, I
can't currently find a way to test sending a single pointer-atom to the
left inlet. (If you try to strip it with list trim you always end up with
the "list" selector.)
----------------------------------------------------------------------
Comment By: Frank Barknecht (fbar)
Date: 2010-03-01 07:16
Message:
I meant to write:
useless just like a "gem_state" stripped of its *selector*.
----------------------------------------------------------------------
Comment By: Frank Barknecht (fbar)
Date: 2010-03-01 07:15
Message:
First I have to correct myself: The selector of a pointer-message is indeed
"pointer", as can be seen with zexy's new rawprint object or by exploiting
the error message of an object like [select] when sent a pointer which is
"no method for 'pointer'".
So "route pointer" could or maybe should indeed route a "pointer"
meta-message just like it can route a "gem_state" message However as
[route] also strips off the selector you would be left with just the
pointer that is more or less useless just like a "gem_state" stripped of
its pointer cannot be used in the gem chain anymore.
----------------------------------------------------------------------
Comment By: Jonathan Wilkes (jancsika1)
Date: 2010-02-28 22:11
Message:
(pointer) with the g missing is what is specified in m_atom.c for
displaying a pointer atom. So I assume there's a difference between a
pointer message and a pointer atom.
There are two reasons to [route] pointer messages.
1) Didactic-- [route] is a common object people use to learn about the
behavior of messages in Pd. It would be nice to show all the predefined
message types going to different outlets, which can't currently happen
because [route] doesn't differentiate between pointers and anythings.
2) Because anythings and pointers aren't differentiated, this diminishes
the flexibility of an abstraction inlet. So a data-structure related
abstraction that wants to take "set," "flush", "clear", and pointer
messages to the left inlet and do something else with the right inlet has
to add an additional inlet. The [pointer] object can differentiate between
a pointer and "rewind," for example. An abstraction should be able to have
the same flexibility.
----------------------------------------------------------------------
Comment By: Frank Barknecht (fbar)
Date: 2010-02-25 11:37
Message:
Yep, a gpointer is not simply a message composed of "pointer" and some
actual pointer blob. I don't know the exact details myself and don't really
understand the source code, but they seem to be something very "special"
just like signals are. As you know, [print] shows them as a not very
helpful "(gpointer)", but if you pass a pointer to [list prepend set]-[list
trim] and into a message box: There pointers show up as "(pointer)" with
the "g" missing. Anyway don't bother trying [route (pointer)], it doesn't
work either. :)
In the end we probably have to accept that gpointers don't have a
"printable" selector, just like audio signals don't have one. Introducing a
print- and routable selector as "pointer" may be useful, or maybe it's not,
as some people may already use "pointer" as a meta-message in their
patches, for example to handle mouse-"pointer" events or so.
----------------------------------------------------------------------
Comment By: Jonathan Wilkes (jancsika1)
Date: 2010-02-25 00:54
Message:
Hm, I'm just not understanding something about gpointers-- I'd just assumed
when you send a pointer message it consists of the selector "pointer"
followed by the gpointer itself (gridflow's [display] seems to confirm
this). But clearly something else is going on because [route pointer]
doesn't currently work for gpointers, nor will [pointer] accept a gpointer
that has passed through [pointer $1( (though [route] will, without
crashing, and output a usable gpointer that has the selector "list").
It also seems like "pointer 1 2 3" is an unchecked case of "bad arguments
to message 'pointer'". So I guess I'm saying I agree that [route pointer]
should route according to the selector "pointer", I just don't understand
why a gpointer wouldn't match under those conditions.
----------------------------------------------------------------------
Comment By: Frank Barknecht (fbar)
Date: 2010-02-23 03:40
Message:
Hi Jonathan,
I raised the priority as crashes are really serious. I disagree with your
item 3), though. [route pointer] should not route GPointers, but
meta-messages starting with the symbol "pointer" e.g.
[pointer 1 2 3(
|
[route pointer]
|
It does that just fine.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2957058&group_…
Bugs item #2957057, was opened at 2010-02-23 01:06
Message generated for change (Settings changed) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2957057&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
>Category: externals
>Group: v0.42
>Status: Pending
Resolution: None
Priority: 5
Private: No
Submitted By: Jonathan Wilkes (jancsika1)
>Assigned to: Hans-Christoph Steiner (eighthave)
Summary: pddplink and pddp/dsp don't play well together
Initial Comment:
If you use pddplink and pddp/dsp in the same patch, pddplink gives the following error:
pddplink: internal error (open [path to the file shown in the link] )
This is caused by [r pd] in pddp/dsp. (Matju wrote something on the list about why this happens, but I can't seem to find it at the moment)
----------------------------------------------------------------------
>Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-04-12 23:21
Message:
I couldn't reproduce this with Pd version 0.42.5-extended-20100405 on Mac
OS X 10.5.8/Intel but I suspect it was also fixed by recent pddplink
changes for bugs 2960967 and 2959373
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2957057&group_…
Bugs item #2959373, was opened at 2010-02-25 22:26
Message generated for change (Settings changed) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2959373&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: externals
>Group: v0.42
>Status: Pending
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Jonathan Wilkes (jancsika1)
>Assigned to: Hans-Christoph Steiner (eighthave)
Summary: pddplink doesn't handle relative paths correctly
Initial Comment:
The attached example shows the problem clearly. If you use the link in main.pd it will open ./myPatch.pd, but myPatch.pd will erroneously inherit the path of the canvas that contains the link. Thus helperAbstraction won't create because ./folder is not searched.
You can see this clearly in the window heading of myPatch.pd after you follow the link: it lists the object as "./folder/myPatch.pd" and the path as that of main.pd. But if you make an object [./folder/myPatch.pd] in main.pd and open it, you can see it correctly lists the object as "myPatch.pd" and makes ./folder part of the path. This is what pddplink should do, too.
----------------------------------------------------------------------
>Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-04-12 23:10
Message:
Fixed with this commit:
http://pure-data.svn.sourceforge.net/viewvc/pure-data?view=rev&revision=134…
And also fixed it within the menu_doc_open command in pd-extended and
pd-gui-rewrite:
http://pure-data.svn.sourceforge.net/viewvc/pure-data?view=rev&revision=134…
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2959373&group_…