Pd-dev May 2008

pd-dev@lists.iem.at

20 participants
187 discussions

[ pure-data-Patches-1704511 ] Delete broken on Windows, key/keyup/keyname misses some keys
by SourceForge.net 09 May '08

09 May '08

Patches item #1704511, was opened at 2007-04-20 13:45 Message generated for change (Comment added) made by eighthave You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1704511&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: puredata >Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Hans-Christoph Steiner (eighthave) Assigned to: Miller Puckette (millerpuckette) >Summary: Delete broken on Windows, key/keyup/keyname misses some keys Initial Comment: Pressing the Del key does nothing. Instead it should remove the character to the right. I tested this on Windows XP with Pd 0.38-4, 0.39-2, and 0.40-2. This works on Mac OS X. I did not test on GNU/Linux. ---------------------------------------------------------------------- >Comment By: Hans-Christoph Steiner (eighthave) Date: 2008-05-09 15:53 Message: Logged In: YES user_id=27104 Originator: YES Attached is a patch that fixed this, and also fixes BackSpace, Delete, Tab, Space, Return, Escape for [key]/[keyup]/[keyname]. This patch also fixes bugs #1728414 and #1728405. http://sourceforge.net/tracker/index.php?func=detail&aid=1728414&group_id=5… http://sourceforge.net/tracker/index.php?func=detail&aid=1728405&group_id=5… File Added: fix_backspace_delete-0.41.4.patch ---------------------------------------------------------------------- Comment By: IOhannes m zmölnig (zmoelnig) Date: 2007-10-16 05:36 Message: Logged In: YES user_id=564396 Originator: NO does it work once you have deleted a key with backspace? (sometimes deleting is weird on linux) apart from that: i just tested it with pd-0.40-1 on linux and both backspace and delete work as expected) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1704511&group_…

1 0

[ pure-data-Bugs-1698780 ] hid misses lots of keyboard events on Intel Mac
by SourceForge.net 09 May '08

09 May '08

Bugs item #1698780, was opened at 2007-04-11 17:03 Message generated for change (Comment added) made by eighthave You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1698780&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.39.2 >Status: Closed >Resolution: Works For Me Priority: 5 Private: No Submitted By: Hans-Christoph Steiner (eighthave) Assigned to: Hans-Christoph Steiner (eighthave) Summary: hid misses lots of keyboard events on Intel Mac Initial Comment: Using Pd-0.39.2-extended-test7 on a MacBook Pro 17", [hid] misses most keyboard events. This works fine on my Powerbook G4. Can anyone else with an Intel Mac confirm this? ---------------------------------------------------------------------- >Comment By: Hans-Christoph Steiner (eighthave) Date: 2008-05-09 15:19 Message: Logged In: YES user_id=27104 Originator: YES this seems to be fixed now in Pd-extended 0.40.3-20080502, but I don't think I changed anything. Perhaps Apple fixed some bugs :) ---------------------------------------------------------------------- Comment By: stffn (stffn) Date: 2007-04-12 10:10 Message: Logged In: YES user_id=1658640 Originator: NO Hmm.. I can't attaches a patch. Here it is in text. Named 1698780-test.pd ---- #N canvas 119 75 454 343 10; #X obj 33 58 loadbang; #X obj 33 120 tgl 15 0 empty empty empty 0 -6 0 8 -262144 -1 -1 0 1 ; #X obj 33 91 t b b; #X msg 63 120 open 0; #X obj 33 150 hid/keyboard 0; #X obj 33 181 unpack symbol float; #X symbolatom 33 217 10 0 0 0 - - -; #X floatatom 161 218 5 0 0 0 - - -; #X text 30 259 Ripping off hig/keyboard-help.pd to test on intel mac. ; #X text 30 285 Steffen; #X text 30 273 Cf. ticket #1698780; #X connect 0 0 2 0; #X connect 1 0 4 0; #X connect 2 0 1 0; #X connect 2 1 3 0; #X connect 3 0 4 0; #X connect 4 0 5 0; #X connect 5 0 6 0; #X connect 5 1 7 0; ---- ---------------------------------------------------------------------- Comment By: stffn (stffn) Date: 2007-04-12 10:08 Message: Logged In: YES user_id=1658640 Originator: NO I don't know [hid], but i ripped of hid/keybord-help.pd to make a test pd patch. I sent it [open 0(, then it gives me a lot of working keys. Might be all keys. It works up to 5 (letter) keys at the same time. Attached is the test patch. Platform is Macbook Intel Dual Core (that's the first generation) OS X.4.9 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1698780&group_…

1 0

[ pure-data-Bugs-1572310 ] after Save As..., the path remains at the location
by SourceForge.net 09 May '08

09 May '08

Bugs item #1572310, was opened at 2006-10-06 14:20 Message generated for change (Settings changed) made by eighthave You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1572310&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: puredata Group: v0.40.0 Status: Open >Resolution: Later >Priority: 2 Private: No Submitted By: Hans-Christoph Steiner (eighthave) Assigned to: Nobody/Anonymous (nobody) Summary: after Save As..., the path remains at the location Initial Comment: If you open an instance of an abstraction, then Save As... to somewhere else, the path of that abstraction stays at the original location, even though the file was saved to the new location. Clicking File->Save will then save to the original location rather than the new location. Tested on Mac OS X with Pd-0.39.2, Pd-0.39.2-extended-test5, and Pd-0.40-0. ---------------------------------------------------------------------- Comment By: Hans-Christoph Steiner (eighthave) Date: 2008-04-28 17:51 Message: Logged In: YES user_id=27104 Originator: YES Strange, I looked into this. It seems that just the title bar isn't being updated, but the patch does think of itself in the new location. [getdir] will show the new location. It seems that when canvas_rename() is called inside of canvas_savetofile(), the directory is not yet updated, when things get to canvas_reflecttitle(), and therefore canvas_getdir() returns the old location rather than the new one. Since this is now cosmetic, I'll leave it for another day. ---------------------------------------------------------------------- Comment By: Hans-Christoph Steiner (eighthave) Date: 2006-10-07 17:49 Message: Logged In: YES user_id=27104 "Save As..." means write out a new file. A new file means a new class. The instance that started this process remains the old class, therefore is no longer related to this new class. This means its inconsistent to have this instance remain as the original class. Also, from a usability perspective, it makes things much more coherent. In every other app that I use, when I do "Save As...", that current view changes to the new file. It does not remain on the old file. ---------------------------------------------------------------------- Comment By: Frank Barknecht (fbar) Date: 2006-10-07 07:53 Message: Logged In: YES user_id=569446 I'm note sure if that's a bug, though I agree, that it's confusing. But if you open an instance of an abstraction and save that under a different name, this action doesn't affect the name of the abstraction's instance as it is used in the parent patch: This one will stay the same. If you want to use your newly saved abstraction you need to rename the instance to the new name as well first. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1572310&group_…

1 0

[ pure-data-Bugs-1459776 ] weird bug: dot in comment disappears
by SourceForge.net 09 May '08

09 May '08

Bugs item #1459776, was opened at 2006-03-28 00:10 Message generated for change (Settings changed) made by eighthave You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1459776&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: Closed Resolution: Later Priority: 5 Private: No Submitted By: Hans-Christoph Steiner (eighthave) Assigned to: Nobody/Anonymous (nobody) Summary: weird bug: dot in comment disappears Initial Comment: I found a very strange, very specific bug: If have text in a comment that has a . in the second position, and a space in the third position, the . is not saved. But if you dynamically generate that comment, the dot is saved. This is Pd-0.38.4-extended and Miller's 0.39-2 on Mac OS X. ---------------------------------------------------------------------- Comment By: Hans-Christoph Steiner (eighthave) Date: 2006-03-30 20:44 Message: Logged In: YES user_id=27104 >From Matju: > The weird thing is that if you auto-generate the comment > with the 1., then it survives a copy-paste. Try the > patch in the bug tracker, if you haven't already. It's because you make it as a single symbol. In Pd, gensym() can turn any null-terminated string into a symbol. When you copy+paste, the contents of the comment don't change, they point to the same symbol. When you save to a file, however, it gets printed without quoting, because quoting is not supported (or not fully), so for a lot of possible symbols there's no syntax that you can use to produce them literally, you have to go thru gensym() explicitly instead (e.g. [sprintf]). Copy+paste only copies a t_atom[] whereas saving/loading calls binbuf_save/binbuf_eval. ---------------------------------------------------------------------- Comment By: Hans-Christoph Steiner (eighthave) Date: 2006-03-30 20:43 Message: Logged In: YES user_id=27104 from Matju: > Right... I forgot about this. This is probably related > to Pd not having a string type... Yeah, comments are parsed by pd exactly like objectboxes. it's just that no actual object is instantiated (binbuf_eval is not called). That was necessary to avoid having to introduce strings in pd and/or making a special case for comments. ---------------------------------------------------------------------- Comment By: Frank Barknecht (fbar) Date: 2006-03-28 03:23 Message: Logged In: YES user_id=569446 This bug works differently, however. Every number followed by a dot and a space is affected, however comments starting with a letter and a dot aren't. So this comment is okay: a. something but this isn't: numbers: 1. 2. 3. 4. Pd converts floating point numbers in comments if possible, so they don't contain floating points anymore. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1459776&group_…

1 0

readanysf~/osx: flext build errors: 'template with C linkage'
by Damian Stewart 09 May '08

09 May '08

hey, i have the latest flext from CVS and i'm trying to compile flext on OSX, so i can make readanysf~. following through the build system steps, the third time i run build.sh (the time when it actually tries to compile things) i get the following build errors: damians-computer:~/0.inbox/externals/grill/flext damian$ bash build.sh pd gcc make -f ./buildsys/gnumake-sub.mak PLATFORM=mac RTSYS=pd COMPILER=gcc BUILDPATH=./buildsys/ PKGINFO=package.txt BUILDCLASS=flext USRCONFIG=config.txt USRMAKE=build/gnumake-mac-gcc.inc TARGETMODE=release TARGETTYPE=single _build_ buildsys/mac/gnumake-gcc-targets.inc:22: warning: overriding commands for target `pd-darwin/release-single' buildsys/mac/gnumake-gcc-targets.inc:18: warning: ignoring old commands for target `pd-darwin/release-single' mkdir -p pd-darwin/release-single/ g++ -c -DFLEXT_USE_SIMD -DNDEBUG -DFLEXT_EXPORTS -DFLEXT_SYS=2 -DPD -I/Applications/Pd-0.41-4.app/Contents/Resources/src -I/usr/local/include/stk -I/usr/local/include/sndobj source/flext.h -o pd-darwin/release-single/flext.h.gch /usr/include/c++/4.0.0/i686-apple-darwin8/bits/c++locale.h:60: error: template with C linkage /usr/include/c++/4.0.0/bits/stringfwd.h:49: error: template with C linkage /usr/include/c++/4.0.0/bits/stringfwd.h:52: error: template with C linkage /usr/include/c++/4.0.0/bits/stringfwd.h:56: error: template with C linkage /usr/include/c++/4.0.0/bits/postypes.h:81: error: template with C linkage /usr/include/c++/4.0.0/iosfwd:55: error: template with C linkage /usr/include/c++/4.0.0/iosfwd:58: error: template with C linkage /usr/include/c++/4.0.0/iosfwd:61: error: template with C linkage /usr/include/c++/4.0.0/iosfwd:64: error: template with C linkage ... if i take out PRECOMPILE=flext.h from package.txt (as suggested by someone a year or two ago), i get 'no rule to make flext.h.gch' can anyone shed any light on this? thanks d -- damian stewart | +44 7500 543 766 | damian(a)frey.co.nz frey | live art with machines | http://www.frey.co.nz

1 0

osx/intel: 'expected in: flat namespace' loading external
by Damian Stewart 08 May '08

08 May '08

hello, i'm trying to get pvoc~ to work on osx/intel. it compiles fine, with no errors, but then trying to load the external in Pd I get: /Library/PD/pvoc~.d_fat: dlopen(/Library/PD/pvoc~.d_fat, 10): Symbol not found: _fftw_malloc Referenced from: /Library/PD/pvoc~.d_fat Expected in: flat namespace i've tried hacking the makefile to pull out the -flat_namespace switch but that causes symbol undefined problems. i've also tried various combinations of setting CFLAGS and LDFLAGS to -flat_namespace and -twolevel_namespace, again with no luck. ... and trying similar steps with partconv~ i get the same problem. any advice? thanks d -- damian stewart | +44 7500 543 766 | damian(a)frey.co.nz frey | live art with machines | http://www.frey.co.nz

1 1

[ pure-data-Bugs-1960450 ] -schedlib broken on OS X?
by SourceForge.net 08 May '08

08 May '08

Bugs item #1960450, was opened at 2008-05-08 14:40 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1960450&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: 5 Private: No Submitted By: marius schebella (mariusschebella) Assigned to: Nobody/Anonymous (nobody) Summary: -schedlib broken on OS X? Initial Comment: hi, I am running the pdj external on 0.41-4, which is working fine. it also has the possibility to run as -schedlib pdj, but with the -schedlib option pd does not start up. this is vanilla 0.41-4 and os x 10.5 on intel. m. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1960450&group_…

1 0

build error (hidio)
by Tim 08 May '08

08 May '08

Tried to compile pd-extended-0.40.3, got some error in hidio. Looks perhaps like hidio's problem. Any thoughts? As a quick fix, is there some easy way to disable building of certain externals? cc -DPD -O2 -mcpu=i686 -march=i386 -I/home/me/pd-extended/pd/src -Wall -W -ggdb -DUNIX -Dunix -fPIC -o "/home/me/pd-extended/externals/hcs/hid/input_arrays.o" -c "/home/me/pd-extended/externals/hcs/hid/input_ arrays.c" `-mcpu=' is deprecated. Use `-mtune=' or '-march=' instead. cc -DPD -O2 -mcpu=i686 -march=i386 -I/home/me/pd-extended/pd/src -Wall -W -ggdb -DUNIX -Dunix -fPIC -o "/home/me/pd-extended/externals/hcs/hid/hid_linux.o" -c "/home/me/pd-extended/externals/hcs/hid/hid_linux .c" `-mcpu=' is deprecated. Use `-mtune=' or '-march=' instead. /home/me/pd-extended/externals/hcs/hid/hid_linux.c: In function 'hid_convert_linux_buttons_to_numbers': /home/me/pd-extended/externals/hcs/hid/hid_linux.c:68: warning: the address of 'hid_code' will always evaluate as 'true' /home/me/pd-extended/externals/hcs/hid/hid_linux.c: In function 'hid_print_device_list': /home/me/pd-extended/externals/hcs/hid/hid_linux.c:270: warning: the address of 'dev_handle_name' will always evaluate as 'true' /home/me/pd-extended/externals/hcs/hid/hid_linux.c: In function 'hid_open_device': /home/me/pd-extended/externals/hcs/hid/hid_linux.c:445: warning: the address of 'block_device' will always evaluate as 'true' /home/me/pd-extended/externals/hcs/hid/hid_linux.c: In function 'hid_platform_specific_free': /home/me/pd-extended/externals/hcs/hid/hid_linux.c:537: warning: unused parameter 'x' /home/me/pd-extended/externals/hcs/hid/hid_linux.c: In function 'get_device_number_by_id': /home/me/pd-extended/externals/hcs/hid/hid_linux.c:571: warning: unused parameter 'vendor_id' /home/me/pd-extended/externals/hcs/hid/hid_linux.c:571: warning: unused parameter 'product_id' /home/me/pd-extended/externals/hcs/hid/hid_linux.c: In function 'get_device_number_from_usage': /home/me/pd-extended/externals/hcs/hid/hid_linux.c:577: warning: unused parameter 'device_number' /home/me/pd-extended/externals/hcs/hid/hid_linux.c:578: warning: unused parameter 'usage_page' /home/me/pd-extended/externals/hcs/hid/hid_linux.c:579: warning: unused parameter 'usage' /home/me/pd-extended/externals/hcs/hid/hid_linux.c: In function 'hid_ff_autocenter': /home/me/pd-extended/externals/hcs/hid/hid_linux.c:592: warning: unused parameter 'x' /home/me/pd-extended/externals/hcs/hid/hid_linux.c:592: warning: unused parameter 'value' /home/me/pd-extended/externals/hcs/hid/hid_linux.c: In function 'hid_ff_gain': /home/me/pd-extended/externals/hcs/hid/hid_linux.c:598: warning: unused parameter 'x' /home/me/pd-extended/externals/hcs/hid/hid_linux.c:598: warning: unused parameter 'value' /home/me/pd-extended/externals/hcs/hid/hid_linux.c: In function 'hid_ff_motors': /home/me/pd-extended/externals/hcs/hid/hid_linux.c:604: warning: unused parameter 'x' /home/me/pd-extended/externals/hcs/hid/hid_linux.c:604: warning: unused parameter 'value' /home/me/pd-extended/externals/hcs/hid/hid_linux.c: In function 'hid_ff_continue': /home/me/pd-extended/externals/hcs/hid/hid_linux.c:610: warning: unused parameter 'x' /home/me/pd-extended/externals/hcs/hid/hid_linux.c: In function 'hid_ff_pause': /home/me/pd-extended/externals/hcs/hid/hid_linux.c:616: warning: unused parameter 'x' /home/me/pd-extended/externals/hcs/hid/hid_linux.c: In function 'hid_ff_reset': /home/me/pd-extended/externals/hcs/hid/hid_linux.c:622: warning: unused parameter 'x' /home/me/pd-extended/externals/hcs/hid/hid_linux.c: In function 'hid_ff_stopall': /home/me/pd-extended/externals/hcs/hid/hid_linux.c:628: warning: unused parameter 'x' /home/me/pd-extended/externals/hcs/hid/hid_linux.c: In function 'hid_ff_fftest': /home/me/pd-extended/externals/hcs/hid/hid_linux.c:636: warning: unused parameter 'x' /home/me/pd-extended/externals/hcs/hid/hid_linux.c:636: warning: unused parameter 'value' /home/me/pd-extended/externals/hcs/hid/hid_linux.c: In function 'hid_ff_print': /home/me/pd-extended/externals/hcs/hid/hid_linux.c:642: warning: unused parameter 'x' /home/me/pd-extended/externals/hcs/hid/hid_linux.c: In function 'hid_platform_specific_info': /home/me/pd-extended/externals/hcs/hid/hid_linux.c:555: warning: 'my_id.vendor' is used uninitialized in this function /home/me/pd-extended/externals/hcs/hid/hid_linux.c:559: warning: 'my_id.product' is used uninitialized in this function cc -DPD -O2 -mcpu=i686 -march=i386 -I/home/me/pd-extended/pd/src -Wall -W -ggdb -DUNIX -Dunix -fPIC -o "/home/me/pd-extended/externals/hcs/hid/hid.o" -c "/home/me/pd-extended/externals/hcs/hid/hid.c" `-mcpu=' is deprecated. Use `-mtune=' or '-march=' instead. /home/me/pd-extended/externals/hcs/hid/hid.c: In function 'hid_read': /home/me/pd-extended/externals/hcs/hid/hid.c:363: warning: unused parameter 'fd' /home/me/pd-extended/externals/hcs/hid/hid.c: In function 'hid_debug': /home/me/pd-extended/externals/hcs/hid/hid.c:413: warning: unused parameter 'x' cc -Wl,-export_dynamic -shared -o /home/me/pd-extended/externals/hcs/hid/hid.pd_linux \ /home/me/pd-extended/externals/hcs/hid/input_arrays.o /home/me/pd-extended/externals/hcs/hid/hid_linux.o /home/me/pd-extended/externals/hcs/hid/hid.o -lm -lc cc -DPD -O2 -mcpu=i686 -march=i386 -I/home/me/pd-extended/pd/src -Wall -W -ggdb -DUNIX -Dunix -fPIC -o "/home/me/pd-extended/externals/io/hidio/input_arrays.o" -c "/home/me/pd-extended/externals/io/hidio/inpu t_arrays.c" `-mcpu=' is deprecated. Use `-mtune=' or '-march=' instead. cc -DPD -O2 -mcpu=i686 -march=i386 -I/home/me/pd-extended/pd/src -Wall -W -ggdb -DUNIX -Dunix -fPIC -o "/home/me/pd-extended/externals/io/hidio/hidio_linux.o" -c "/home/me/pd-extended/externals/io/hidio/hidio _linux.c" `-mcpu=' is deprecated. Use `-mtune=' or '-march=' instead. /home/me/pd-extended/externals/io/hidio/hidio_linux.c: In function 'hidio_convert_linux_buttons_to_numbers': /home/me/pd-extended/externals/io/hidio/hidio_linux.c:75: warning: the address of 'hidio_code' will always evaluate as 'true' /home/me/pd-extended/externals/io/hidio/hidio_linux.c: In function 'hidio_print_device_list': /home/me/pd-extended/externals/io/hidio/hidio_linux.c:277: warning: the address of 'dev_handle_name' will always evaluate as 'true' /home/me/pd-extended/externals/io/hidio/hidio_linux.c: In function 'hidio_open_device': /home/me/pd-extended/externals/io/hidio/hidio_linux.c:454: warning: the address of 'block_device' will always evaluate as 'true' /home/me/pd-extended/externals/io/hidio/hidio_linux.c: In function 'hidio_platform_specific_free': /home/me/pd-extended/externals/io/hidio/hidio_linux.c:544: warning: unused parameter 'x' /home/me/pd-extended/externals/io/hidio/hidio_linux.c: In function 'get_device_number_by_id': /home/me/pd-extended/externals/io/hidio/hidio_linux.c:578: warning: unused parameter 'vendor_id' /home/me/pd-extended/externals/io/hidio/hidio_linux.c:578: warning: unused parameter 'product_id' /home/me/pd-extended/externals/io/hidio/hidio_linux.c: In function 'get_device_number_from_usage': /home/me/pd-extended/externals/io/hidio/hidio_linux.c:584: warning: unused parameter 'device_number' /home/me/pd-extended/externals/io/hidio/hidio_linux.c:585: warning: unused parameter 'usage_page' /home/me/pd-extended/externals/io/hidio/hidio_linux.c:586: warning: unused parameter 'usage' /home/me/pd-extended/externals/io/hidio/hidio_linux.c: In function 'hidio_write_event': /home/me/pd-extended/externals/io/hidio/hidio_linux.c:594: warning: unused parameter 'instance' /home/me/pd-extended/externals/io/hidio/hidio_linux.c: In function 'hidio_platform_specific_info': /home/me/pd-extended/externals/io/hidio/hidio_linux.c:562: warning: 'my_id.vendor' is used uninitialized in this function /home/me/pd-extended/externals/io/hidio/hidio_linux.c:566: warning: 'my_id.product' is used uninitialized in this function cc -DPD -O2 -mcpu=i686 -march=i386 -I/home/me/pd-extended/pd/src -Wall -W -ggdb -DUNIX -Dunix -fPIC -o "/home/me/pd-extended/externals/io/hidio/hidio_types.o" -c "/home/me/pd-extended/externals/io/hidio/hidio _types.c" `-mcpu=' is deprecated. Use `-mtune=' or '-march=' instead. cc -DPD -O2 -mcpu=i686 -march=i386 -I/home/me/pd-extended/pd/src -Wall -W -ggdb -DUNIX -Dunix -fPIC -o "/home/me/pd-extended/externals/io/hidio/hidio.o" -c "/home/me/pd-extended/externals/io/hidio/hidio.c" `-mcpu=' is deprecated. Use `-mtune=' or '-march=' instead. /home/me/pd-extended/externals/io/hidio/hidio.c: In function 'hidio_write_event': /home/me/pd-extended/externals/io/hidio/hidio.c:305: warning: unused parameter 's' /home/me/pd-extended/externals/io/hidio/hidio.c: In function 'hidio_debug': /home/me/pd-extended/externals/io/hidio/hidio.c:546: warning: unused parameter 'x' /home/me/pd-extended/externals/io/hidio/hidio.c: In function 'hidio_new': /home/me/pd-extended/externals/io/hidio/hidio.c:567: warning: unused parameter 's' cc -Wl,-export_dynamic -shared -o /home/me/pd-extended/externals/io/hidio/hidio.pd_linux \ /home/me/pd-extended/externals/io/hidio/input_arrays.o /home/me/pd-extended/externals/io/hidio/hidio_linux.o /home/me/pd-extended/externals/io/hidio/hidio_types.o /home/me/pd-extended/ext ernals/io/hidio/hidio.o -lm -lc /home/me/pd-extended/externals/io/hidio/hidio.o: In function `hidio_write_event': /home/me/pd-extended/externals/io/hidio/hidio.c:306: multiple definition of `hidio_write_event' /home/me/pd-extended/externals/io/hidio/hidio_linux.o:/home/me/pd-extended/externals/io/hidio/hidio_linux.c:595: first defined here collect2: ld returned 1 exit status make[2]: *** [/home/me/pd-extended/externals/io/hidio/hidio.pd_linux] Error 1 make[2]: Leaving directory `/home/me/pd-extended/externals' make[1]: *** [externals_install] Error 2 make[1]: Leaving directory `/home/me/pd-extended/packages' make: *** [install] Error 2

2 2

[ pure-data-Patches-1959417 ] [unpackOSC] should output a message rather than a list
by SourceForge.net 07 May '08

07 May '08

Patches item #1959417, was opened at 2008-05-07 13:15 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1959417&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: bugfix Status: Open Resolution: None Priority: 5 Private: No Submitted By: IOhannes m zmölnig (zmoelnig) Assigned to: Martin Peach (mrpeach) Summary: [unpackOSC] should output a message rather than a list Initial Comment: the current implementation of [unpackOSC] outputs a list instead of a message. e.g. the OSC-message "/bla 1 2 3" will be output as "list /bla 1 2 3" if you want to use [route] to dispatch the message, you therefore have to [list trim] (or [route list]) the "list"-selector away. ([routeOSC] handles these lists quite well) the attached patch will internally trim the selector away and thus [unpackOSC] will output "/bla 1 2 3" ([routeOSC] handles these quite well as well) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1959417&group_…

1 0

[ pure-data-Bugs-1917574 ] declare not working on osx
by SourceForge.net 06 May '08

06 May '08

Bugs item #1917574, was opened at 2008-03-17 21:01 Message generated for change (Comment added) made by mariusschebella You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1917574&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: 5 Private: No Submitted By: marius schebella (mariusschebella) Assigned to: Nobody/Anonymous (nobody) Summary: declare not working on osx Initial Comment: I am not sure if declare is working the way it is supposed to on OSX the object I am trying to create is [OSCroute]. I can create [oscx/OSCroute], but what I want to accomplish is to avoid the oscx prefix, so I tried [declare -stdpath extra/oscx] [declare -stdpath oscx] [declare -path extra/oscx] [declare -path oscx] [declare -stdlib extra/oscx] [declare -stdlib oscx] [declare -lib extra/oscx] [declare -lib oscx] I even tried [declare -stdpath extra/oscx] in combination with import oscx. and I get a console printout saying [import] loaded library: oscx, but OSCroute ... couldn't create don't know how to track down the error, or if I am maybe doing something wrong. pd-extended-0.40.3-20080222. ---------------------------------------------------------------------- >Comment By: marius schebella (mariusschebella) Date: 2008-05-06 12:45 Message: Logged In: YES user_id=1856112 Originator: YES that's how -stdpath works on os x. it does not work for absolute paths, and seems to be relative to some directory outside of /Applications. I tried all relations with less ../ and from inside /Applications. declare -stdpath ../../../../../../../../Applications/Pd-0.40.3-extended-20080428.app/Contents/Resources/extra/boids maybe this helps. m. ---------------------------------------------------------------------- Comment By: marius schebella (mariusschebella) Date: 2008-05-04 13:35 Message: Logged In: YES user_id=1856112 Originator: YES I just realized that I made some mistakes in the past and that declare actually is working better than I thought. here is what I forgot: 1) declare only takes effect when you open the patch. stupid, I think I read it, but... Some alleged "bugs" were caused by the assumption that it is enough to create a declare object and paths will be set... 2) no absolute paths! absolute paths work for -lib, but not for -path/-stdpath. at least on OS X it is not possible to set absolute paths (or at least I don't know how), all paths have to be relative to Pd (-stdpath) or to the patch (-path). ---------------------------------------------------------------------- Comment By: Roman Haefeli (reduzent) Date: 2008-03-20 09:38 Message: Logged In: YES user_id=1895440 Originator: NO oops... from some quick fix from before i accidently still had a symbolic link from /home/roman/extra pointing to /usr/local/lib/pd/extra/, that is why it found [bar] in that funny place: /home/roman/extra/foo/bar.pd tried again without the symlink: -------------------------------- tried /home/roman/declare_test.pd and succeeded tried /home/roman/../extra/foo/bar.l_i386 and failed tried /home/roman/bar.l_i386 and failed tried /usr/local/lib/pd/extra/bar.l_i386 and failed tried /home/roman/../extra/foo/bar.pd_linux and failed tried /home/roman/bar.pd_linux and failed tried /usr/local/lib/pd/extra/bar.pd_linux and failed tried /home/roman/../extra/foo/bar/bar.l_i386 and failed tried /home/roman/bar/bar.l_i386 and failed tried /usr/local/lib/pd/extra/bar/bar.l_i386 and failed tried /home/roman/../extra/foo/bar/bar.pd_linux and failed tried /home/roman/bar/bar.pd_linux and failed tried /usr/local/lib/pd/extra/bar/bar.pd_linux and failed tried /home/roman/../extra/foo/bar.pd and failed tried /home/roman/bar.pd and failed tried /usr/local/lib/pd/extra/bar.pd and failed tried /home/roman/../extra/foo/bar.pat and failed tried /home/roman/bar.pat and failed tried /usr/local/lib/pd/extra/bar.pat and failed ---------------------------------------------------------------------- Comment By: Roman Haefeli (reduzent) Date: 2008-03-20 07:49 Message: Logged In: YES user_id=1895440 Originator: NO i just did the same test again on my box, ubuntu dapper i686: tried /home/roman/declare_test.pd and succeeded tried /home/roman/extra/foo/bar.l_i386 and failed tried /home/roman/bar.l_i386 and failed tried /usr/local/lib/pd/extra/bar.l_i386 and failed tried /home/roman/extra/foo/bar.pd_linux and failed tried /home/roman/bar.pd_linux and failed tried /usr/local/lib/pd/extra/bar.pd_linux and failed tried /home/roman/extra/foo/bar/bar.l_i386 and failed tried /home/roman/bar/bar.l_i386 and failed tried /usr/local/lib/pd/extra/bar/bar.l_i386 and failed tried /home/roman/extra/foo/bar/bar.pd_linux and failed tried /home/roman/bar/bar.pd_linux and failed tried /usr/local/lib/pd/extra/bar/bar.pd_linux and failed tried /home/roman/extra/foo/bar.pd and succeeded which means: - there is a difference between linux ppc and linux intel - currently linux intel is the _only_ platform where [declare] works as documented. ---------------------------------------------------------------------- Comment By: Roman Haefeli (reduzent) Date: 2008-03-20 07:20 Message: Logged In: YES user_id=1895440 Originator: NO could we give this issue a higher priority? the longer [declare] is not working correctly, the more confusion it will cause. also it currently cannot be used to create portable patches, that work on every platform with every pd-distro, which i find would be the strong point in using [declare]. ---------------------------------------------------------------------- Comment By: Roman Haefeli (reduzent) Date: 2008-03-20 07:11 Message: Logged In: YES user_id=1895440 Originator: NO the same test on a ubuntu ppc machine with pd 0.41-4 compiled from source and installed to the default location gave similar results: output from pd-window: ---------------------- tried /home/olivia/declare_test.pd and succeeded tried /home/olivia/extra/foo/bar.l_i386 and failed tried /home/olivia/bar.l_i386 and failed tried /usr/local/lib/pd/extra/bar.l_i386 and failed tried /home/olivia/extra/foo/bar.pd_linux and failed tried /home/olivia/bar.pd_linux and failed tried /usr/local/lib/pd/extra/bar.pd_linux and failed tried /home/olivia/extra/foo/bar/bar.l_i386 and failed tried /home/olivia/bar/bar.l_i386 and failed tried /usr/local/lib/pd/extra/bar/bar.l_i386 and failed tried /home/olivia/extra/foo/bar/bar.pd_linux and failed tried /home/olivia/bar/bar.pd_linux and failed tried /usr/local/lib/pd/extra/bar/bar.pd_linux and failed tried /home/olivia/extra/foo/bar.pd and failed tried /home/olivia/bar.pd and failed tried /usr/local/lib/pd/extra/bar.pd and failed tried /home/olivia/extra/foo/bar.pat and failed tried /home/olivia/bar.pat and failed tried /usr/local/lib/pd/extra/bar.pat and failed bar ... couldn't create instantiating [foo/bar] works fine, which means, that installation of [bar] is correct and pd finds it in extra/foo. ---------------------------------------------------------------------- Comment By: Roman Haefeli (reduzent) Date: 2008-03-20 06:48 Message: Logged In: YES user_id=1895440 Originator: NO while [declare -stdlib] seems to work, [declare -stdpath] doesn't work on windows as well. i created a folder 'foo' into the extra directory and put a file 'bar.pd' in there. my test setup: -------------- pd installation path: D:\programme\pd-0.41\ pd executable: D:\programme\pd-0.41\bin\pd.exe test-abstraction: D:\programme\pd-0.41\extra\foo\bar.pd test-patch: D:\home\declare_test.pd test-patch contains: [declare -stdpath extra/foo] [bar] pd start command: D:\programme\pd-0.41\bin\pd.exe -verbose -open D:\home\declare_test.pd output from pd-window: ---------------------- tried D:\\home\\declare_test.pd and succeeded tried D:\\home\\..\\extra\\foo\\bar.m_i386 and failed tried D:\\home\\bar.m_i386 and failed tried D:\\programme\\pd-0.41\\extra\\bar.m_i386 and failed tried D:\\home\\..\\extra\\foo\\bar.dll and failed tried D:\\home\\bar.dll and failed tried D:\\programme\\pd-0.41\\extra\\bar.dll and failed tried D:\\home\\..\\extra\\foo\\bar\\bar.m_i386 and failed tried D:\\home\\bar\\bar.m_i386 and failed tried D:\\programme\\pd-0.41\\extra\\bar\\bar.m_i386 and failed tried D:\\home\\..\\extra\\foo\\bar\\bar.dll and failed tried D:\\home\\bar\\bar.dll and failed tried D:\\programme\\pd-0.41\\extra\\bar\\bar.dll and failed tried D:\\home\\..\\extra\\foo\\bar.pd and failed tried D:\\home\\bar.pd and failed tried D:\\programme\\pd-0.41\\extra\\bar.pd and failed tried D:\\home\\..\\extra\\foo\\bar.pat and failed tried D:\\home\\bar.pat and failed tried D:\\programme\\pd-0.41\\extra\\bar.pat and failed bar ... couldn't create it looks like [declare -stdpath] is adding the search path relative to the patch instead of relative to pd. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1917574&group_…

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Pd-dev May 2008