Also, has the problem with [~ ] and similar objects using special
characters been fixed in 0.42.5 (IIRC 0.41.4 had issues with these
so you
had to invoke those objects using hex ascii values).
That's an issue with hexloader. If you want to use those names, you
need to load
hex loader $Revision: 1.5 $
written by IOhannes m zmölnig, IEM zmoel...@iem.at
compiled on Nov 17 2009 at 19:30:48
compiled against Pd version 0.42.5.extended
load_object: Symbol 0x3e0x7e_setup not found
[~] part of zexy-2.2.3 (compiled: Apr 29 2009)
Just to follow-up.
1) if hexloader is buggy/incomplete what will it take to fix it?
2) if you agree with me that in the interim pd-extended is effectively
broken what can be done to circumvent this problem to make it usable
until hexloader is fixed?
I guess I owe everyone an apology. I've recompiled the
On Nov 17, 2009, at 7:51 PM, Ivica Ico Bukvic wrote:
hex loader $Revision: 1.5 $
written by IOhannes m zmölnig, IEM zmoel...@iem.at
compiled on Nov 17 2009 at 19:30:48
compiled against Pd version 0.42.5.extended
load_object: Symbol 0x3e0x7e_setup not found
[~] part of
On Nov 12, 2009, at 12:18 PM, Ivica Ico Bukvic wrote:
I think its good to get to a point where we don't have to worry much
about backwards compatibility. IMHO, the easiest way to do that is
embed library and other settings in each patch rather than having
libraries loaded by default. The
On Nov 14, 2009, at 1:41 PM, Ivica Ico Bukvic wrote:
In Pd-extended 0.41.4 and newer, and with libdirs, the help patches
should be found when using namespace prefixes. They are in all the
tests I've done.
As for loading by default, I personally think no libraries should be
loaded by default.
No, that works for me. Which help patch isn't working?
In that case it could be because I moved things around not knowing about
hexloader and other interesting stuff.
Also, has the problem with [~ ] and similar objects using special
characters been fixed in 0.42.5 (IIRC 0.41.4 had issues
FWIW, I recently listened to a really entertaining presentation of a
computer systems security expert and one thing he pointed out that IMHO is
currently really bogging Pd development is legacy support.
If PD is currently undergoing a complete rewrite of the GUI this may be a
good opportunity to
I think its good to get to a point where we don't have to worry much
about backwards compatibility. IMHO, the easiest way to do that is
embed library and other settings in each patch rather than having
libraries loaded by default. The pow~ issue highlights that.
You can also already
I think its good to get to a point where we don't have to worry much
about backwards compatibility. IMHO, the easiest way to do that is
embed library and other settings in each patch rather than having
libraries loaded by default. The pow~ issue highlights that.
You can also already use
On Thu, Nov 12, 2009 at 4:57 PM, Hans-Christoph Steiner h...@at.or.atwrote:
I think its good to get to a point where we don't have to worry much about
backwards compatibility. IMHO, the easiest way to do that is embed library
and other settings in each patch rather than having libraries
11 matches
Mail list logo
