Pd-dev June 2009

pd-dev@lists.iem.at

16 participants
105 discussions

iemxmlrpc not building on MinGW
by Hans-Christoph Steiner 18 Jun '09

18 Jun '09

The link to pthreadGC2 is failing: g++ -s -shared -o /home/pd/auto-build/pd-extended/externals/iem/ iemxmlrpc/xmlrpc.dll /home/pd/auto-build/pd-extended/externals/iem/ iemxmlrpc/main.o /home/pd/auto-build/pd-extended/externals/iem/ iemxmlrpc/xmlrpc++/src/XmlRpcClient.o /home/pd/auto-build/pd-extended/ externals/iem/iemxmlrpc/xmlrpc++/src/XmlRpcDispatch.o /home/pd/auto- build/pd-extended/externals/iem/iemxmlrpc/xmlrpc++/src/XmlRpcServer.o / home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/xmlrpc++/src/ XmlRpcServerConnection.o /home/pd/auto-build/pd-extended/externals/iem/ iemxmlrpc/xmlrpc++/src/XmlRpcServerMethod.o /home/pd/auto-build/pd- extended/externals/iem/iemxmlrpc/xmlrpc++/src/XmlRpcSocket.o /home/pd/ auto-build/pd-extended/externals/iem/iemxmlrpc/xmlrpc++/src/ XmlRpcSource.o /home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ xmlrpc++/src/XmlRpcUtil.o /home/pd/auto-build/pd-extended/externals/ iem/iemxmlrpc/xmlrpc++/src/XmlRpcValue.o -lm -L/home/pd/auto-build/pd- extended/pd/bin -L/home/pd/auto-build/pd-extended/pd/obj -lpd - lwsock32 -lpthreadGC2 -lkernel32 -luser32 -lgdi32 -lregex C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ main.o:C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/ iemxmlrpc/main.cpp:118: undefined reference to `_imp__pthread_mutex_lock' C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ main.o:C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/ iemxmlrpc/main.cpp:152: undefined reference to `_imp__pthread_mutex_unlock' C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ main.o: In function `RPCServer': C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ main.cpp:265: undefined reference to `_imp__pthread_mutex_init' C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ main.cpp:266: undefined reference to `_imp__pthread_mutex_init' C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ main.cpp:267: undefined reference to `_imp__pthread_mutex_init' C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ main.cpp:265: undefined reference to `_imp__pthread_mutex_init' C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ main.cpp:266: undefined reference to `_imp__pthread_mutex_init' C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ main.o:C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/ iemxmlrpc/main.cpp:267: more undefined references to `_imp__pthread_mutex_init' follow C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ main.o: In function `~RPCServer': C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ main.cpp:278: undefined reference to `_imp__pthread_mutex_destroy' C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ main.cpp:279: undefined reference to `_imp__pthread_mutex_destroy' C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ main.cpp:280: undefined reference to `_imp__pthread_mutex_destroy' C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ main.cpp:278: undefined reference to `_imp__pthread_mutex_destroy' C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ main.cpp:279: undefined reference to `_imp__pthread_mutex_destroy' C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ main.o:C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/ iemxmlrpc/main.cpp:280: more undefined references to `_imp__pthread_mutex_destroy' follow C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ main.o:C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/ iemxmlrpc/main.cpp:289: undefined reference to `_imp__pthread_mutex_lock' C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ main.o:C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/ iemxmlrpc/main.cpp:291: undefined reference to `_imp__pthread_mutex_unlock' C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ main.o:C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/ iemxmlrpc/main.cpp:298: undefined reference to `_imp__pthread_mutex_lock' C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ main.o:C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/ iemxmlrpc/main.cpp:304: undefined reference to `_imp__pthread_mutex_unlock' C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ main.o:C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/ iemxmlrpc/main.cpp:634: undefined reference to `_imp__pthread_mutex_lock' C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ main.o:C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/ iemxmlrpc/main.cpp:650: undefined reference to `_imp__pthread_mutex_unlock' C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ main.o: In function `xmlrpc_new': C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ main.cpp:768: undefined reference to `_imp__pthread_create' C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ main.o:C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/ iemxmlrpc/main.cpp:193: undefined reference to `_imp__pthread_cond_signal' C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ main.o: In function `~Message': C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ main.cpp:186: undefined reference to `_imp__pthread_cond_destroy' C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ main.o:C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/ iemxmlrpc/main.cpp:198: undefined reference to `_imp__pthread_mutex_lock' C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ main.o:C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/ iemxmlrpc/main.cpp:199: undefined reference to `_imp__pthread_cond_wait' C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ main.o:C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/ iemxmlrpc/main.cpp:200: undefined reference to `_imp__pthread_mutex_unlock' C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ main.o: In function `Message': C:/msys/1.0/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ main.cpp:179: undefined reference to `_imp__pthread_cond_init' collect2: ld returned 1 exit status make[2]: *** [/home/pd/auto-build/pd-extended/externals/iem/iemxmlrpc/ xmlrpc.dll] Error 1 make[2]: Leaving directory `/home/pd/auto-build/pd-extended/externals' make[1]: *** [externals_install] Error 2 make[1]: Leaving directory `/home/pd/auto-build/pd-extended/packages' ---------------------------------------------------------------------------- http://at.or.at/hans/

1 0

win xp-filesystem: get folder content?
by Hannes Breitschädel 17 Jun '09

17 Jun '09

Hi List! Windwos XP-Question: is there a way to get the content of a folder within a pd patch? Example: my harddrive could contain something like: .../audio/test1.wav .../audio/test2.wav .../audio/samples/drum.wav .../audio/samples/funny.wav I imagine an object that is sent a message "gimme_content .../audio/" on which it returns "test1.wav", "test2.wav", "samples/" Important: the object should also return foldernames within the specified folder. thanks from a very humid vienna... Hannes

2 3

[ pure-data-Bugs-2794086 ] hexloader problem in 0.41-4 RC2
by SourceForge.net 17 Jun '09

17 Jun '09

Bugs item #2794086, was opened at 2009-05-19 21:15 Message generated for change (Comment added) made by sf-robot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2794086&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.41 >Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Thomas Mayer (elvettsemic) Assigned to: Hans-Christoph Steiner (eighthave) Summary: hexloader problem in 0.41-4 RC2 Initial Comment: Hexloader will not load objects like [>~] in Pd version 0.41.4-extended-rc2 on Debian Lenny i386. Hexloader is loaded: hex loader $Revision: 1.5 $ written by IOhannes m zmlnig, IEM <zmoelnig(a)iem.at> compiled on May 18 2009 at 02:37:31 compiled against Pd version 0.41.4.extended-rc2 but then: >~ $2 ... couldn't create load_object: Symbol "0x3e0x7e_setup" not found error: BUG: hexloader not loading abstraction: /usr/lib/pd/extra/zexy/0x3e0x7e.pd (not yet implemented) The file /usr/lib/pd/extra/zexy/0x3e0x7e.pd exists, as well as /usr/lib/pd/extra/zexy/0x3e0x7e.pd_linux ---------------------------------------------------------------------- >Comment By: SourceForge Robot (sf-robot) Date: 2009-06-17 02:20 Message: This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: Hans-Christoph Steiner (eighthave) Date: 2009-06-02 23:24 Message: This fix should make the hexloader compile correctly for Pd-extended: http://pure-data.svn.sourceforge.net/viewvc/pure-data?view=rev&revision=116… But in order to use it, it needs to be loaded first. Its not loaded by default in Pd-extended. Please test this in tomorrow's builds. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-05-24 20:48 Message: After mv-ing 0x3e0x7e.pd out of the way, I get the following output: tried /usr/lib/pd/extra/zexy/0x3e0x7e.pd_linux and succeeded verbose( 2):hexloader trying /usr/lib/pd/extra/zexy/0x3e0x7e.pd_linux (0x3e0x7e_setup) verbose( 2):hexload object: Symbol "0x3e0x7e_setup" not found verbose( 2):hexloader trying /usr/lib/pd/extra/zexy/0x3e0x7e.pd_linux (setup_0x3e0x7e) verbose( 2):hexload object: Symbol "setup_0x3e0x7e" not found ---------------------------------------------------------------------- Comment By: ClaudiusMaximus (claudiusmaximus) Date: 2009-05-23 18:10 Message: Works fine here with hexloader and zexy --disable-library compiled from SVN trunk against pd-0.41-4 on GNU/Linux/Debian/Lenny/pure:dyne: tried ../zexy/src/0x3e0x7e.pd_linux and succeeded verbose( 2):hexloader trying ../zexy/src/0x3e0x7e.pd_linux (0x3e0x7e_setup) verbose( 2):hexload object: Symbol "0x3e0x7e_setup" not found verbose( 2):hexloader trying ../zexy/src/0x3e0x7e.pd_linux (setup_0x3e0x7e) [>~] part of zexy-2.2.3 (compiled: May 23 2009) Copyright (l) 1999-2008 IOhannes m zmnig, forum::f::umlte & IEM ---------------------------------------------------------------------- Comment By: IOhannes m zmlnig (zmoelnig) Date: 2009-05-23 09:04 Message: no this is not really the problem. hexloader doesn't implement abstraction loading yet (it did once, but this failed to load abstraction recursively so it is disabled for now), which explains perfectly why it doesn't load 0x3e0x7e.pd. however, it should be able to load 0x3e0x7e.pd_linux which it doesn't: tried /usr/lib/pd/extra/zexy/0x3e0x7e.pd_linux and succeeded verbose( 2):hexloader trying /usr/lib/pd/extra/zexy/0x3e0x7e.pd_linux (0x3e0x7e_setup) verbose( 2):hexload object: Symbol "0x3e0x7e_setup" not found verbose( 2):hexloader trying /usr/lib/pd/extra/zexy/0x3e0x7e.pd_linux (setup_0x3e0x7e) verbose( 2):hexload object: Symbol "setup_0x3e0x7e" not found tried ./0x3e~.pd and failed i don't know why. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-05-22 10:31 Message: The problem is of course the lines: tried /usr/lib/pd/extra/zexy/0x3e0x7e.pd and succeeded error: BUG: hexloader not loading abstraction: /usr/lib/pd/extra/zexy/0x3e0x7e.pd (not yet implemented) ---------------------------------------------------------------------- Comment By: Thomas Mayer (elvettsemic) Date: 2009-05-20 10:05 Message: The output in the Pd console when double-verbose and loading [>~]: tried /home/thomas/Shell-Scripte/>~.l_i386 and failed tried /usr/lib/pd/extra/>~.l_i386 and failed tried /home/thomas/Shell-Scripte/pd/abstractions/>~.l_i386 and failed tried /home/thomas/Shell-Scripte/pd/pdmtl/>~.l_i386 and failed tried /usr/lib/pd/extra/zexy/>~.l_i386 and failed tried /usr/lib/pd/extra/flatspace/>~.l_i386 and failed tried /usr/lib/pd/extra/rtc/>~.l_i386 and failed tried /usr/lib/pd/extra/cyclone/>~.l_i386 and failed tried /usr/lib/extra/creb/>~.l_i386 and failed tried /usr/lib/pd/extra/creb/>~.l_i386 and failed tried /usr/lib/pd/extra/ggee/>~.l_i386 and failed tried /home/thomas/pd-externals/>~.l_i386 and failed tried /usr/local/lib/pd-externals/>~.l_i386 and failed tried /usr/lib/pd/extra/>~.l_i386 and failed tried /home/thomas/Shell-Scripte/>~.pd_linux and failed tried /usr/lib/pd/extra/>~.pd_linux and failed tried /home/thomas/Shell-Scripte/pd/abstractions/>~.pd_linux and failed tried /home/thomas/Shell-Scripte/pd/pdmtl/>~.pd_linux and failed tried /usr/lib/pd/extra/zexy/>~.pd_linux and failed tried /usr/lib/pd/extra/flatspace/>~.pd_linux and failed tried /usr/lib/pd/extra/rtc/>~.pd_linux and failed tried /usr/lib/pd/extra/cyclone/>~.pd_linux and failed tried /usr/lib/extra/creb/>~.pd_linux and failed tried /usr/lib/pd/extra/creb/>~.pd_linux and failed tried /usr/lib/pd/extra/ggee/>~.pd_linux and failed tried /home/thomas/pd-externals/>~.pd_linux and failed tried /usr/local/lib/pd-externals/>~.pd_linux and failed tried /usr/lib/pd/extra/>~.pd_linux and failed tried /home/thomas/Shell-Scripte/>~/>~.l_i386 and failed tried /usr/lib/pd/extra/>~/>~.l_i386 and failed tried /home/thomas/Shell-Scripte/pd/abstractions/>~/>~.l_i386 and failed tried /home/thomas/Shell-Scripte/pd/pdmtl/>~/>~.l_i386 and failed tried /usr/lib/pd/extra/zexy/>~/>~.l_i386 and failed tried /usr/lib/pd/extra/flatspace/>~/>~.l_i386 and failed tried /usr/lib/pd/extra/rtc/>~/>~.l_i386 and failed tried /usr/lib/pd/extra/cyclone/>~/>~.l_i386 and failed tried /usr/lib/extra/creb/>~/>~.l_i386 and failed tried /usr/lib/pd/extra/creb/>~/>~.l_i386 and failed tried /usr/lib/pd/extra/ggee/>~/>~.l_i386 and failed tried /home/thomas/pd-externals/>~/>~.l_i386 and failed tried /usr/local/lib/pd-externals/>~/>~.l_i386 and failed tried /usr/lib/pd/extra/>~/>~.l_i386 and failed tried /home/thomas/Shell-Scripte/>~/>~.pd_linux and failed tried /usr/lib/pd/extra/>~/>~.pd_linux and failed tried /home/thomas/Shell-Scripte/pd/abstractions/>~/>~.pd_linux and failed tried /home/thomas/Shell-Scripte/pd/pdmtl/>~/>~.pd_linux and failed tried /usr/lib/pd/extra/zexy/>~/>~.pd_linux and failed tried /usr/lib/pd/extra/flatspace/>~/>~.pd_linux and failed tried /usr/lib/pd/extra/rtc/>~/>~.pd_linux and failed tried /usr/lib/pd/extra/cyclone/>~/>~.pd_linux and failed tried /usr/lib/extra/creb/>~/>~.pd_linux and failed tried /usr/lib/pd/extra/creb/>~/>~.pd_linux and failed tried /usr/lib/pd/extra/ggee/>~/>~.pd_linux and failed tried /home/thomas/pd-externals/>~/>~.pd_linux and failed tried /usr/local/lib/pd-externals/>~/>~.pd_linux and failed tried /usr/lib/pd/extra/>~/>~.pd_linux and failed verbose( 2):calling sys_load with '>~' tried /home/thomas/Shell-Scripte/>~.l_i386 and failed tried /usr/lib/pd/extra/>~.l_i386 and failed tried /home/thomas/Shell-Scripte/pd/abstractions/>~.l_i386 and failed tried /home/thomas/Shell-Scripte/pd/pdmtl/>~.l_i386 and failed tried /usr/lib/pd/extra/zexy/>~.l_i386 and failed tried /usr/lib/pd/extra/flatspace/>~.l_i386 and failed tried /usr/lib/pd/extra/rtc/>~.l_i386 and failed tried /usr/lib/pd/extra/cyclone/>~.l_i386 and failed tried /usr/lib/extra/creb/>~.l_i386 and failed tried /usr/lib/pd/extra/creb/>~.l_i386 and failed tried /usr/lib/pd/extra/ggee/>~.l_i386 and failed tried /home/thomas/pd-externals/>~.l_i386 and failed tried /usr/local/lib/pd-externals/>~.l_i386 and failed tried /usr/lib/pd/extra/>~.l_i386 and failed tried /home/thomas/Shell-Scripte/>~.pd_linux and failed tried /usr/lib/pd/extra/>~.pd_linux and failed tried /home/thomas/Shell-Scripte/pd/abstractions/>~.pd_linux and failed tried /home/thomas/Shell-Scripte/pd/pdmtl/>~.pd_linux and failed tried /usr/lib/pd/extra/zexy/>~.pd_linux and failed tried /usr/lib/pd/extra/flatspace/>~.pd_linux and failed tried /usr/lib/pd/extra/rtc/>~.pd_linux and failed tried /usr/lib/pd/extra/cyclone/>~.pd_linux and failed tried /usr/lib/extra/creb/>~.pd_linux and failed tried /usr/lib/pd/extra/creb/>~.pd_linux and failed tried /usr/lib/pd/extra/ggee/>~.pd_linux and failed tried /home/thomas/pd-externals/>~.pd_linux and failed tried /usr/local/lib/pd-externals/>~.pd_linux and failed tried /usr/lib/pd/extra/>~.pd_linux and failed tried /home/thomas/Shell-Scripte/>~/>~.l_i386 and failed tried /usr/lib/pd/extra/>~/>~.l_i386 and failed tried /home/thomas/Shell-Scripte/pd/abstractions/>~/>~.l_i386 and failed tried /home/thomas/Shell-Scripte/pd/pdmtl/>~/>~.l_i386 and failed tried /usr/lib/pd/extra/zexy/>~/>~.l_i386 and failed tried /usr/lib/pd/extra/flatspace/>~/>~.l_i386 and failed tried /usr/lib/pd/extra/rtc/>~/>~.l_i386 and failed tried /usr/lib/pd/extra/cyclone/>~/>~.l_i386 and failed tried /usr/lib/extra/creb/>~/>~.l_i386 and failed tried /usr/lib/pd/extra/creb/>~/>~.l_i386 and failed tried /usr/lib/pd/extra/ggee/>~/>~.l_i386 and failed tried /home/thomas/pd-externals/>~/>~.l_i386 and failed tried /usr/local/lib/pd-externals/>~/>~.l_i386 and failed tried /usr/lib/pd/extra/>~/>~.l_i386 and failed tried /home/thomas/Shell-Scripte/>~/>~.pd_linux and failed tried /usr/lib/pd/extra/>~/>~.pd_linux and failed tried /home/thomas/Shell-Scripte/pd/abstractions/>~/>~.pd_linux and failed tried /home/thomas/Shell-Scripte/pd/pdmtl/>~/>~.pd_linux and failed tried /usr/lib/pd/extra/zexy/>~/>~.pd_linux and failed tried /usr/lib/pd/extra/flatspace/>~/>~.pd_linux and failed tried /usr/lib/pd/extra/rtc/>~/>~.pd_linux and failed tried /usr/lib/pd/extra/cyclone/>~/>~.pd_linux and failed tried /usr/lib/extra/creb/>~/>~.pd_linux and failed tried /usr/lib/pd/extra/creb/>~/>~.pd_linux and failed tried /usr/lib/pd/extra/ggee/>~/>~.pd_linux and failed tried /home/thomas/pd-externals/>~/>~.pd_linux and failed tried /usr/local/lib/pd-externals/>~/>~.pd_linux and failed tried /usr/lib/pd/extra/>~/>~.pd_linux and failed tried ./>~/>~-meta.pd and failed tried /usr/lib/pd/extra/>~/>~-meta.pd and failed tried /home/thomas/Shell-Scripte/pd/abstractions/>~/>~-meta.pd and failed tried /home/thomas/Shell-Scripte/pd/pdmtl/>~/>~-meta.pd and failed tried /usr/lib/pd/extra/zexy/>~/>~-meta.pd and failed tried /usr/lib/pd/extra/flatspace/>~/>~-meta.pd and failed tried /usr/lib/pd/extra/rtc/>~/>~-meta.pd and failed tried /usr/lib/pd/extra/cyclone/>~/>~-meta.pd and failed tried /usr/lib/extra/creb/>~/>~-meta.pd and failed tried /usr/lib/pd/extra/creb/>~/>~-meta.pd and failed tried /usr/lib/pd/extra/ggee/>~/>~-meta.pd and failed tried /home/thomas/pd-externals/>~/>~-meta.pd and failed tried /usr/local/lib/pd-externals/>~/>~-meta.pd and failed tried /usr/lib/pd/extra/>~/>~-meta.pd and failed verbose( 2):calling sys_load with '0x3e~' tried /home/thomas/Shell-Scripte/0x3e~.l_i386 and failed tried /usr/lib/pd/extra/0x3e~.l_i386 and failed tried /home/thomas/Shell-Scripte/pd/abstractions/0x3e~.l_i386 and failed tried /home/thomas/Shell-Scripte/pd/pdmtl/0x3e~.l_i386 and failed tried /usr/lib/pd/extra/zexy/0x3e~.l_i386 and failed tried /usr/lib/pd/extra/flatspace/0x3e~.l_i386 and failed tried /usr/lib/pd/extra/rtc/0x3e~.l_i386 and failed tried /usr/lib/pd/extra/cyclone/0x3e~.l_i386 and failed tried /usr/lib/extra/creb/0x3e~.l_i386 and failed tried /usr/lib/pd/extra/creb/0x3e~.l_i386 and failed tried /usr/lib/pd/extra/ggee/0x3e~.l_i386 and failed tried /home/thomas/pd-externals/0x3e~.l_i386 and failed tried /usr/local/lib/pd-externals/0x3e~.l_i386 and failed tried /usr/lib/pd/extra/0x3e~.l_i386 and failed tried /home/thomas/Shell-Scripte/0x3e~.pd_linux and failed tried /usr/lib/pd/extra/0x3e~.pd_linux and failed tried /home/thomas/Shell-Scripte/pd/abstractions/0x3e~.pd_linux and failed tried /home/thomas/Shell-Scripte/pd/pdmtl/0x3e~.pd_linux and failed tried /usr/lib/pd/extra/zexy/0x3e~.pd_linux and failed tried /usr/lib/pd/extra/flatspace/0x3e~.pd_linux and failed tried /usr/lib/pd/extra/rtc/0x3e~.pd_linux and failed tried /usr/lib/pd/extra/cyclone/0x3e~.pd_linux and failed tried /usr/lib/extra/creb/0x3e~.pd_linux and failed tried /usr/lib/pd/extra/creb/0x3e~.pd_linux and failed tried /usr/lib/pd/extra/ggee/0x3e~.pd_linux and failed tried /home/thomas/pd-externals/0x3e~.pd_linux and failed tried /usr/local/lib/pd-externals/0x3e~.pd_linux and failed tried /usr/lib/pd/extra/0x3e~.pd_linux and failed tried /home/thomas/Shell-Scripte/0x3e~/0x3e~.l_i386 and failed tried /usr/lib/pd/extra/0x3e~/0x3e~.l_i386 and failed tried /home/thomas/Shell-Scripte/pd/abstractions/0x3e~/0x3e~.l_i386 and failed tried /home/thomas/Shell-Scripte/pd/pdmtl/0x3e~/0x3e~.l_i386 and failed tried /usr/lib/pd/extra/zexy/0x3e~/0x3e~.l_i386 and failed tried /usr/lib/pd/extra/flatspace/0x3e~/0x3e~.l_i386 and failed tried /usr/lib/pd/extra/rtc/0x3e~/0x3e~.l_i386 and failed tried /usr/lib/pd/extra/cyclone/0x3e~/0x3e~.l_i386 and failed tried /usr/lib/extra/creb/0x3e~/0x3e~.l_i386 and failed tried /usr/lib/pd/extra/creb/0x3e~/0x3e~.l_i386 and failed tried /usr/lib/pd/extra/ggee/0x3e~/0x3e~.l_i386 and failed tried /home/thomas/pd-externals/0x3e~/0x3e~.l_i386 and failed tried /usr/local/lib/pd-externals/0x3e~/0x3e~.l_i386 and failed tried /usr/lib/pd/extra/0x3e~/0x3e~.l_i386 and failed tried /home/thomas/Shell-Scripte/0x3e~/0x3e~.pd_linux and failed tried /usr/lib/pd/extra/0x3e~/0x3e~.pd_linux and failed tried /home/thomas/Shell-Scripte/pd/abstractions/0x3e~/0x3e~.pd_linux and failed tried /home/thomas/Shell-Scripte/pd/pdmtl/0x3e~/0x3e~.pd_linux and failed tried /usr/lib/pd/extra/zexy/0x3e~/0x3e~.pd_linux and failed tried /usr/lib/pd/extra/flatspace/0x3e~/0x3e~.pd_linux and failed tried /usr/lib/pd/extra/rtc/0x3e~/0x3e~.pd_linux and failed tried /usr/lib/pd/extra/cyclone/0x3e~/0x3e~.pd_linux and failed tried /usr/lib/extra/creb/0x3e~/0x3e~.pd_linux and failed tried /usr/lib/pd/extra/creb/0x3e~/0x3e~.pd_linux and failed tried /usr/lib/pd/extra/ggee/0x3e~/0x3e~.pd_linux and failed tried /home/thomas/pd-externals/0x3e~/0x3e~.pd_linux and failed tried /usr/local/lib/pd-externals/0x3e~/0x3e~.pd_linux and failed tried /usr/lib/pd/extra/0x3e~/0x3e~.pd_linux and failed tried ./0x3e~/0x3e~-meta.pd and failed tried /usr/lib/pd/extra/0x3e~/0x3e~-meta.pd and failed tried /home/thomas/Shell-Scripte/pd/abstractions/0x3e~/0x3e~-meta.pd and failed tried /home/thomas/Shell-Scripte/pd/pdmtl/0x3e~/0x3e~-meta.pd and failed tried /usr/lib/pd/extra/zexy/0x3e~/0x3e~-meta.pd and failed tried /usr/lib/pd/extra/flatspace/0x3e~/0x3e~-meta.pd and failed tried /usr/lib/pd/extra/rtc/0x3e~/0x3e~-meta.pd and failed tried /usr/lib/pd/extra/cyclone/0x3e~/0x3e~-meta.pd and failed tried /usr/lib/extra/creb/0x3e~/0x3e~-meta.pd and failed tried /usr/lib/pd/extra/creb/0x3e~/0x3e~-meta.pd and failed tried /usr/lib/pd/extra/ggee/0x3e~/0x3e~-meta.pd and failed tried /home/thomas/pd-externals/0x3e~/0x3e~-meta.pd and failed tried /usr/local/lib/pd-externals/0x3e~/0x3e~-meta.pd and failed tried /usr/lib/pd/extra/0x3e~/0x3e~-meta.pd and failed verbose( 2):calling sys_load with '0x3e0x7e' tried /home/thomas/Shell-Scripte/0x3e0x7e.l_i386 and failed tried /usr/lib/pd/extra/0x3e0x7e.l_i386 and failed tried /home/thomas/Shell-Scripte/pd/abstractions/0x3e0x7e.l_i386 and failed tried /home/thomas/Shell-Scripte/pd/pdmtl/0x3e0x7e.l_i386 and failed tried /usr/lib/pd/extra/zexy/0x3e0x7e.l_i386 and failed tried /usr/lib/pd/extra/flatspace/0x3e0x7e.l_i386 and failed tried /usr/lib/pd/extra/rtc/0x3e0x7e.l_i386 and failed tried /usr/lib/pd/extra/cyclone/0x3e0x7e.l_i386 and failed tried /usr/lib/extra/creb/0x3e0x7e.l_i386 and failed tried /usr/lib/pd/extra/creb/0x3e0x7e.l_i386 and failed tried /usr/lib/pd/extra/ggee/0x3e0x7e.l_i386 and failed tried /home/thomas/pd-externals/0x3e0x7e.l_i386 and failed tried /usr/local/lib/pd-externals/0x3e0x7e.l_i386 and failed tried /usr/lib/pd/extra/0x3e0x7e.l_i386 and failed tried /home/thomas/Shell-Scripte/0x3e0x7e.pd_linux and failed tried /usr/lib/pd/extra/0x3e0x7e.pd_linux and failed tried /home/thomas/Shell-Scripte/pd/abstractions/0x3e0x7e.pd_linux and failed tried /home/thomas/Shell-Scripte/pd/pdmtl/0x3e0x7e.pd_linux and failed tried /usr/lib/pd/extra/zexy/0x3e0x7e.pd_linux and succeeded load_object: Symbol "0x3e0x7e_setup" not found tried ./0x3e0x7e/0x3e0x7e-meta.pd and failed tried /usr/lib/pd/extra/0x3e0x7e/0x3e0x7e-meta.pd and failed tried /home/thomas/Shell-Scripte/pd/abstractions/0x3e0x7e/0x3e0x7e-meta.pd and failed tried /home/thomas/Shell-Scripte/pd/pdmtl/0x3e0x7e/0x3e0x7e-meta.pd and failed tried /usr/lib/pd/extra/zexy/0x3e0x7e/0x3e0x7e-meta.pd and failed tried /usr/lib/pd/extra/flatspace/0x3e0x7e/0x3e0x7e-meta.pd and failed tried /usr/lib/pd/extra/rtc/0x3e0x7e/0x3e0x7e-meta.pd and failed tried /usr/lib/pd/extra/cyclone/0x3e0x7e/0x3e0x7e-meta.pd and failed tried /usr/lib/extra/creb/0x3e0x7e/0x3e0x7e-meta.pd and failed tried /usr/lib/pd/extra/creb/0x3e0x7e/0x3e0x7e-meta.pd and failed tried /usr/lib/pd/extra/ggee/0x3e0x7e/0x3e0x7e-meta.pd and failed tried /home/thomas/pd-externals/0x3e0x7e/0x3e0x7e-meta.pd and failed tried /usr/local/lib/pd-externals/0x3e0x7e/0x3e0x7e-meta.pd and failed tried /usr/lib/pd/extra/0x3e0x7e/0x3e0x7e-meta.pd and failed tried ./>~.l_i386 and failed tried /usr/lib/pd/extra/>~.l_i386 and failed tried /home/thomas/Shell-Scripte/pd/abstractions/>~.l_i386 and failed tried /home/thomas/Shell-Scripte/pd/pdmtl/>~.l_i386 and failed tried /usr/lib/pd/extra/zexy/>~.l_i386 and failed tried /usr/lib/pd/extra/flatspace/>~.l_i386 and failed tried /usr/lib/pd/extra/rtc/>~.l_i386 and failed tried /usr/lib/pd/extra/cyclone/>~.l_i386 and failed tried /usr/lib/extra/creb/>~.l_i386 and failed tried /usr/lib/pd/extra/creb/>~.l_i386 and failed tried /usr/lib/pd/extra/ggee/>~.l_i386 and failed tried /home/thomas/pd-externals/>~.l_i386 and failed tried /usr/local/lib/pd-externals/>~.l_i386 and failed tried /usr/lib/pd/extra/>~.l_i386 and failed tried ./>~.pd_linux and failed tried /usr/lib/pd/extra/>~.pd_linux and failed tried /home/thomas/Shell-Scripte/pd/abstractions/>~.pd_linux and failed tried /home/thomas/Shell-Scripte/pd/pdmtl/>~.pd_linux and failed tried /usr/lib/pd/extra/zexy/>~.pd_linux and failed tried /usr/lib/pd/extra/flatspace/>~.pd_linux and failed tried /usr/lib/pd/extra/rtc/>~.pd_linux and failed tried /usr/lib/pd/extra/cyclone/>~.pd_linux and failed tried /usr/lib/extra/creb/>~.pd_linux and failed tried /usr/lib/pd/extra/creb/>~.pd_linux and failed tried /usr/lib/pd/extra/ggee/>~.pd_linux and failed tried /home/thomas/pd-externals/>~.pd_linux and failed tried /usr/local/lib/pd-externals/>~.pd_linux and failed tried /usr/lib/pd/extra/>~.pd_linux and failed tried ./0x3e~.l_i386 and failed tried /usr/lib/pd/extra/0x3e~.l_i386 and failed tried /home/thomas/Shell-Scripte/pd/abstractions/0x3e~.l_i386 and failed tried /home/thomas/Shell-Scripte/pd/pdmtl/0x3e~.l_i386 and failed tried /usr/lib/pd/extra/zexy/0x3e~.l_i386 and failed tried /usr/lib/pd/extra/flatspace/0x3e~.l_i386 and failed tried /usr/lib/pd/extra/rtc/0x3e~.l_i386 and failed tried /usr/lib/pd/extra/cyclone/0x3e~.l_i386 and failed tried /usr/lib/extra/creb/0x3e~.l_i386 and failed tried /usr/lib/pd/extra/creb/0x3e~.l_i386 and failed tried /usr/lib/pd/extra/ggee/0x3e~.l_i386 and failed tried /home/thomas/pd-externals/0x3e~.l_i386 and failed tried /usr/local/lib/pd-externals/0x3e~.l_i386 and failed tried /usr/lib/pd/extra/0x3e~.l_i386 and failed tried ./0x3e~.pd_linux and failed tried /usr/lib/pd/extra/0x3e~.pd_linux and failed tried /home/thomas/Shell-Scripte/pd/abstractions/0x3e~.pd_linux and failed tried /home/thomas/Shell-Scripte/pd/pdmtl/0x3e~.pd_linux and failed tried /usr/lib/pd/extra/zexy/0x3e~.pd_linux and failed tried /usr/lib/pd/extra/flatspace/0x3e~.pd_linux and failed tried /usr/lib/pd/extra/rtc/0x3e~.pd_linux and failed tried /usr/lib/pd/extra/cyclone/0x3e~.pd_linux and failed tried /usr/lib/extra/creb/0x3e~.pd_linux and failed tried /usr/lib/pd/extra/creb/0x3e~.pd_linux and failed tried /usr/lib/pd/extra/ggee/0x3e~.pd_linux and failed tried /home/thomas/pd-externals/0x3e~.pd_linux and failed tried /usr/local/lib/pd-externals/0x3e~.pd_linux and failed tried /usr/lib/pd/extra/0x3e~.pd_linux and failed tried ./0x3e0x7e.l_i386 and failed tried /usr/lib/pd/extra/0x3e0x7e.l_i386 and failed tried /home/thomas/Shell-Scripte/pd/abstractions/0x3e0x7e.l_i386 and failed tried /home/thomas/Shell-Scripte/pd/pdmtl/0x3e0x7e.l_i386 and failed tried /usr/lib/pd/extra/zexy/0x3e0x7e.l_i386 and failed tried /usr/lib/pd/extra/flatspace/0x3e0x7e.l_i386 and failed tried /usr/lib/pd/extra/rtc/0x3e0x7e.l_i386 and failed tried /usr/lib/pd/extra/cyclone/0x3e0x7e.l_i386 and failed tried /usr/lib/extra/creb/0x3e0x7e.l_i386 and failed tried /usr/lib/pd/extra/creb/0x3e0x7e.l_i386 and failed tried /usr/lib/pd/extra/ggee/0x3e0x7e.l_i386 and failed tried /home/thomas/pd-externals/0x3e0x7e.l_i386 and failed tried /usr/local/lib/pd-externals/0x3e0x7e.l_i386 and failed tried /usr/lib/pd/extra/0x3e0x7e.l_i386 and failed tried ./0x3e0x7e.pd_linux and failed tried /usr/lib/pd/extra/0x3e0x7e.pd_linux and failed tried /home/thomas/Shell-Scripte/pd/abstractions/0x3e0x7e.pd_linux and failed tried /home/thomas/Shell-Scripte/pd/pdmtl/0x3e0x7e.pd_linux and failed tried /usr/lib/pd/extra/zexy/0x3e0x7e.pd_linux and succeeded verbose( 2):hexloader trying /usr/lib/pd/extra/zexy/0x3e0x7e.pd_linux (0x3e0x7e_setup) verbose( 2):hexload object: Symbol "0x3e0x7e_setup" not found verbose( 2):hexloader trying /usr/lib/pd/extra/zexy/0x3e0x7e.pd_linux (setup_0x3e0x7e) verbose( 2):hexload object: Symbol "setup_0x3e0x7e" not found tried ./0x3e~.pd and failed tried /usr/lib/pd/extra/0x3e~.pd and failed tried /home/thomas/Shell-Scripte/pd/abstractions/0x3e~.pd and failed tried /home/thomas/Shell-Scripte/pd/pdmtl/0x3e~.pd and failed tried /usr/lib/pd/extra/zexy/0x3e~.pd and failed tried /usr/lib/pd/extra/flatspace/0x3e~.pd and failed tried /usr/lib/pd/extra/rtc/0x3e~.pd and failed tried /usr/lib/pd/extra/cyclone/0x3e~.pd and failed tried /usr/lib/extra/creb/0x3e~.pd and failed tried /usr/lib/pd/extra/creb/0x3e~.pd and failed tried /usr/lib/pd/extra/ggee/0x3e~.pd and failed tried /home/thomas/pd-externals/0x3e~.pd and failed tried /usr/local/lib/pd-externals/0x3e~.pd and failed tried /usr/lib/pd/extra/0x3e~.pd and failed tried ./0x3e~.pat and failed tried /usr/lib/pd/extra/0x3e~.pat and failed tried /home/thomas/Shell-Scripte/pd/abstractions/0x3e~.pat and failed tried /home/thomas/Shell-Scripte/pd/pdmtl/0x3e~.pat and failed tried /usr/lib/pd/extra/zexy/0x3e~.pat and failed tried /usr/lib/pd/extra/flatspace/0x3e~.pat and failed tried /usr/lib/pd/extra/rtc/0x3e~.pat and failed tried /usr/lib/pd/extra/cyclone/0x3e~.pat and failed tried /usr/lib/extra/creb/0x3e~.pat and failed tried /usr/lib/pd/extra/creb/0x3e~.pat and failed tried /usr/lib/pd/extra/ggee/0x3e~.pat and failed tried /home/thomas/pd-externals/0x3e~.pat and failed tried /usr/local/lib/pd-externals/0x3e~.pat and failed tried /usr/lib/pd/extra/0x3e~.pat and failed tried ./0x3e0x7e.pd and failed tried /usr/lib/pd/extra/0x3e0x7e.pd and failed tried /home/thomas/Shell-Scripte/pd/abstractions/0x3e0x7e.pd and failed tried /home/thomas/Shell-Scripte/pd/pdmtl/0x3e0x7e.pd and failed tried /usr/lib/pd/extra/zexy/0x3e0x7e.pd and succeeded error: BUG: hexloader not loading abstraction: /usr/lib/pd/extra/zexy/0x3e0x7e.pd (not yet implemented) tried ./0x3e0x7e.pat and failed tried /usr/lib/pd/extra/0x3e0x7e.pat and failed tried /home/thomas/Shell-Scripte/pd/abstractions/0x3e0x7e.pat and failed tried /home/thomas/Shell-Scripte/pd/pdmtl/0x3e0x7e.pat and failed tried /usr/lib/pd/extra/zexy/0x3e0x7e.pat and failed tried /usr/lib/pd/extra/flatspace/0x3e0x7e.pat and failed tried /usr/lib/pd/extra/rtc/0x3e0x7e.pat and failed tried /usr/lib/pd/extra/cyclone/0x3e0x7e.pat and failed tried /usr/lib/extra/creb/0x3e0x7e.pat and failed tried /usr/lib/pd/extra/creb/0x3e0x7e.pat and failed tried /usr/lib/pd/extra/ggee/0x3e0x7e.pat and failed tried /home/thomas/pd-externals/0x3e0x7e.pat and failed tried /usr/local/lib/pd-externals/0x3e0x7e.pat and failed tried /usr/lib/pd/extra/0x3e0x7e.pat and failed tried ./>~/>~-meta.pd and failed tried /usr/lib/pd/extra/>~/>~-meta.pd and failed tried /home/thomas/Shell-Scripte/pd/abstractions/>~/>~-meta.pd and failed tried /home/thomas/Shell-Scripte/pd/pdmtl/>~/>~-meta.pd and failed tried /usr/lib/pd/extra/zexy/>~/>~-meta.pd and failed tried /usr/lib/pd/extra/flatspace/>~/>~-meta.pd and failed tried /usr/lib/pd/extra/rtc/>~/>~-meta.pd and failed tried /usr/lib/pd/extra/cyclone/>~/>~-meta.pd and failed tried /usr/lib/extra/creb/>~/>~-meta.pd and failed tried /usr/lib/pd/extra/creb/>~/>~-meta.pd and failed tried /usr/lib/pd/extra/ggee/>~/>~-meta.pd and failed tried /home/thomas/pd-externals/>~/>~-meta.pd and failed tried /usr/local/lib/pd-externals/>~/>~-meta.pd and failed tried /usr/lib/pd/extra/>~/>~-meta.pd and failed tried /home/thomas/Shell-Scripte/>~.pd and failed tried /usr/lib/pd/extra/>~.pd and failed tried /home/thomas/Shell-Scripte/pd/abstractions/>~.pd and failed tried /home/thomas/Shell-Scripte/pd/pdmtl/>~.pd and failed tried /usr/lib/pd/extra/zexy/>~.pd and failed tried /usr/lib/pd/extra/flatspace/>~.pd and failed tried /usr/lib/pd/extra/rtc/>~.pd and failed tried /usr/lib/pd/extra/cyclone/>~.pd and failed tried /usr/lib/extra/creb/>~.pd and failed tried /usr/lib/pd/extra/creb/>~.pd and failed tried /usr/lib/pd/extra/ggee/>~.pd and failed tried /home/thomas/pd-externals/>~.pd and failed tried /usr/local/lib/pd-externals/>~.pd and failed tried /usr/lib/pd/extra/>~.pd and failed tried /home/thomas/Shell-Scripte/>~.pat and failed tried /usr/lib/pd/extra/>~.pat and failed tried /home/thomas/Shell-Scripte/pd/abstractions/>~.pat and failed tried /home/thomas/Shell-Scripte/pd/pdmtl/>~.pat and failed tried /usr/lib/pd/extra/zexy/>~.pat and failed tried /usr/lib/pd/extra/flatspace/>~.pat and failed tried /usr/lib/pd/extra/rtc/>~.pat and failed tried /usr/lib/pd/extra/cyclone/>~.pat and failed tried /usr/lib/extra/creb/>~.pat and failed tried /usr/lib/pd/extra/creb/>~.pat and failed tried /usr/lib/pd/extra/ggee/>~.pat and failed tried /home/thomas/pd-externals/>~.pat and failed tried /usr/local/lib/pd-externals/>~.pat and failed tried /usr/lib/pd/extra/>~.pat and failed >~ ... couldn't create ---------------------------------------------------------------------- Comment By: IOhannes m zmlnig (zmoelnig) Date: 2009-05-20 07:07 Message: please run Pd with "-verbose -verbose" (yes, that's 2* verbose) and post the output when trying to load [>~] ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2794086&group_…

1 0

[ pure-data-Bugs-2806856 ] Possible to connect the same in/outlets multiple times
by SourceForge.net 17 Jun '09

17 Jun '09

Bugs item #2806856, was opened at 2009-06-15 18:30 Message generated for change (Comment added) made by eighthave You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2806856&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: Pending Resolution: None Priority: 5 Private: No Submitted By: Johannes (jpburstrom) Assigned to: Nobody/Anonymous (nobody) Summary: Possible to connect the same in/outlets multiple times Initial Comment: When connecting objects through dynamic patching, pd can connect an outlet several times to the same inlet if sending the same message many times. The attached patch shows this behaviour, and why it can lead to strange and hard to find bugs. ---------------------------------------------------------------------- >Comment By: Hans-Christoph Steiner (eighthave) Date: 2009-06-16 19:40 Message: The editor does not let you create duplicate connections. You can see that by reading the .pd file if you save out the patch below before deleting the connection. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-06-16 13:39 Message: eighthave, your test does not necessarily test that, because you don't know in advance whether deleting what looks like a single wire really deletes a single wire or not. Your only quick way of really knowing whether a wire is double, is to try sending messages through a wire that could be double, and see whether the messages get duplicated. Else you have to first demonstrate a way that wires can be really duplicated so that you can show that wire deletion really always deletes one wire at a time... that'd take a lot more than 6 steps. ---------------------------------------------------------------------- Comment By: Hans-Christoph Steiner (eighthave) Date: 2009-06-16 12:17 Message: and for a working illustration of this, try this: 1. create new patch 2. create an [inlet] 3. create an [outlet] 4. connect the [inlet] to the [outlet] 5. connect the [inlet] to the [outlet] again 6. break the connection between the [inlet] and the [outlet] There is only one connection... ---------------------------------------------------------------------- Comment By: Hans-Christoph Steiner (eighthave) Date: 2009-06-16 12:13 Message: IOhannes, its hard to find documentation for things that are not features in software. People usually do not document things that are not included in software, because that documentation would be endless and useless. I can say that duplicate connections is not mentioned in any of the reference materials. Do I need a reference to say that you cannot connect an outlet to the background canvas? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-06-16 10:56 Message: something doesn't have to be a feature OR a bug. it can also be neither, in the grey area, without status nor reason for being whichever way, and there isn't necessarily a reason for it to be any different either. ---------------------------------------------------------------------- Comment By: IOhannes m zmlnig (zmoelnig) Date: 2009-06-16 10:51 Message: was it you that just said "so you can't tell whether it's a bug or a feature, and you can reasonably argue for either"? for instance (totally unrelated) you can just duplicate an object with Ctrl-C Ctrl-V and you cannot visually distinguish the two instances (a common pitfall for newbies and oldies). if this would be removed i would be really upset. however, of course i cannot think of being very upset if the duplicate-connection was removed. i just don't think it's a bug - leaving only the "feature" option... also i am not aware of the truth of "the Pd language as its defined has no way to handle multiple connections from the same outlet to the same inlet". please give a reference. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-06-16 10:37 Message: zmoelnig, whenever you do anything with pd, you must know what you're doing, and it's also easily possible to keep track of multiple connections if the editor allowed them, by using comment (ctrl-5) or a piece of napkin. As a hypothetical question, if canvas_connect disallowed multiple connections, would you really request a multiple connection feature? see also the article "Real Programmers Don't Use Pascal"... ---------------------------------------------------------------------- Comment By: Hans-Christoph Steiner (eighthave) Date: 2009-06-16 10:29 Message: First, the Pd language as its defined has no way to handle multiple connections from the same outlet to the same inlet. The implementation might. The second question then is, is there ever a reason that duplicate connections would be used? They seem to add nothing but confusion. I don't consider confusion a feature. ---------------------------------------------------------------------- Comment By: IOhannes m zmlnig (zmoelnig) Date: 2009-06-16 10:13 Message: i would argue that it is a feature. when programmatically creating patches, you really MUST know what you are doing. it is easily possible to keep track of which connections you have done already, so you don't need to double-connect... ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-06-15 19:21 Message: this happens in canvas_connect in src/g_editor.c and happens in _all_ versions of pd ever, all OSes, etc. it is officially undocumented, so you can't tell whether it's a bug or a feature, and you can reasonably argue for either. ---------------------------------------------------------------------- Comment By: Johannes (jpburstrom) Date: 2009-06-15 19:10 Message: Sorry, here's some more: This is a problem with both pd-0.41.4-extended and pd-0.42.5, on my 64-bit ubuntu 9.04. It seems to happen regardless of sound card and audio API. ---------------------------------------------------------------------- Comment By: Hans-Christoph Steiner (eighthave) Date: 2009-06-15 19:03 Message: Please provide as detailed information as possible including which operating system (OS), CPU type, specific hardware, and the exact distro and version of Pd itself, etc. For example: Pd version 0.41.4-extended Mac OS X 10.5.7/Intel built-in sound ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2806856&group_…

1 0

[ pure-data-Bugs-2806856 ] Possible to connect the same in/outlets multiple times
by SourceForge.net 16 Jun '09

16 Jun '09

Bugs item #2806856, was opened at 2009-06-15 22:30 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2806856&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: Pending Resolution: None Priority: 5 Private: No Submitted By: Johannes (jpburstrom) Assigned to: Nobody/Anonymous (nobody) Summary: Possible to connect the same in/outlets multiple times Initial Comment: When connecting objects through dynamic patching, pd can connect an outlet several times to the same inlet if sending the same message many times. The attached patch shows this behaviour, and why it can lead to strange and hard to find bugs. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-06-16 17:39 Message: eighthave, your test does not necessarily test that, because you don't know in advance whether deleting what looks like a single wire really deletes a single wire or not. Your only quick way of really knowing whether a wire is double, is to try sending messages through a wire that could be double, and see whether the messages get duplicated. Else you have to first demonstrate a way that wires can be really duplicated so that you can show that wire deletion really always deletes one wire at a time... that'd take a lot more than 6 steps. ---------------------------------------------------------------------- Comment By: Hans-Christoph Steiner (eighthave) Date: 2009-06-16 16:17 Message: and for a working illustration of this, try this: 1. create new patch 2. create an [inlet] 3. create an [outlet] 4. connect the [inlet] to the [outlet] 5. connect the [inlet] to the [outlet] again 6. break the connection between the [inlet] and the [outlet] There is only one connection... ---------------------------------------------------------------------- Comment By: Hans-Christoph Steiner (eighthave) Date: 2009-06-16 16:13 Message: IOhannes, its hard to find documentation for things that are not features in software. People usually do not document things that are not included in software, because that documentation would be endless and useless. I can say that duplicate connections is not mentioned in any of the reference materials. Do I need a reference to say that you cannot connect an outlet to the background canvas? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-06-16 14:56 Message: something doesn't have to be a feature OR a bug. it can also be neither, in the grey area, without status nor reason for being whichever way, and there isn't necessarily a reason for it to be any different either. ---------------------------------------------------------------------- Comment By: IOhannes m zmlnig (zmoelnig) Date: 2009-06-16 14:51 Message: was it you that just said "so you can't tell whether it's a bug or a feature, and you can reasonably argue for either"? for instance (totally unrelated) you can just duplicate an object with Ctrl-C Ctrl-V and you cannot visually distinguish the two instances (a common pitfall for newbies and oldies). if this would be removed i would be really upset. however, of course i cannot think of being very upset if the duplicate-connection was removed. i just don't think it's a bug - leaving only the "feature" option... also i am not aware of the truth of "the Pd language as its defined has no way to handle multiple connections from the same outlet to the same inlet". please give a reference. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-06-16 14:37 Message: zmoelnig, whenever you do anything with pd, you must know what you're doing, and it's also easily possible to keep track of multiple connections if the editor allowed them, by using comment (ctrl-5) or a piece of napkin. As a hypothetical question, if canvas_connect disallowed multiple connections, would you really request a multiple connection feature? see also the article "Real Programmers Don't Use Pascal"... ---------------------------------------------------------------------- Comment By: Hans-Christoph Steiner (eighthave) Date: 2009-06-16 14:29 Message: First, the Pd language as its defined has no way to handle multiple connections from the same outlet to the same inlet. The implementation might. The second question then is, is there ever a reason that duplicate connections would be used? They seem to add nothing but confusion. I don't consider confusion a feature. ---------------------------------------------------------------------- Comment By: IOhannes m zmlnig (zmoelnig) Date: 2009-06-16 14:13 Message: i would argue that it is a feature. when programmatically creating patches, you really MUST know what you are doing. it is easily possible to keep track of which connections you have done already, so you don't need to double-connect... ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-06-15 23:21 Message: this happens in canvas_connect in src/g_editor.c and happens in _all_ versions of pd ever, all OSes, etc. it is officially undocumented, so you can't tell whether it's a bug or a feature, and you can reasonably argue for either. ---------------------------------------------------------------------- Comment By: Johannes (jpburstrom) Date: 2009-06-15 23:10 Message: Sorry, here's some more: This is a problem with both pd-0.41.4-extended and pd-0.42.5, on my 64-bit ubuntu 9.04. It seems to happen regardless of sound card and audio API. ---------------------------------------------------------------------- Comment By: Hans-Christoph Steiner (eighthave) Date: 2009-06-15 23:03 Message: Please provide as detailed information as possible including which operating system (OS), CPU type, specific hardware, and the exact distro and version of Pd itself, etc. For example: Pd version 0.41.4-extended Mac OS X 10.5.7/Intel built-in sound ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2806856&group_…

1 0

[ pure-data-Bugs-2806856 ] Possible to connect the same in/outlets multiple times
by SourceForge.net 16 Jun '09

16 Jun '09

Bugs item #2806856, was opened at 2009-06-15 18:30 Message generated for change (Comment added) made by eighthave You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2806856&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: Pending Resolution: None Priority: 5 Private: No Submitted By: Johannes (jpburstrom) Assigned to: Nobody/Anonymous (nobody) Summary: Possible to connect the same in/outlets multiple times Initial Comment: When connecting objects through dynamic patching, pd can connect an outlet several times to the same inlet if sending the same message many times. The attached patch shows this behaviour, and why it can lead to strange and hard to find bugs. ---------------------------------------------------------------------- >Comment By: Hans-Christoph Steiner (eighthave) Date: 2009-06-16 12:17 Message: and for a working illustration of this, try this: 1. create new patch 2. create an [inlet] 3. create an [outlet] 4. connect the [inlet] to the [outlet] 5. connect the [inlet] to the [outlet] again 6. break the connection between the [inlet] and the [outlet] There is only one connection... ---------------------------------------------------------------------- Comment By: Hans-Christoph Steiner (eighthave) Date: 2009-06-16 12:13 Message: IOhannes, its hard to find documentation for things that are not features in software. People usually do not document things that are not included in software, because that documentation would be endless and useless. I can say that duplicate connections is not mentioned in any of the reference materials. Do I need a reference to say that you cannot connect an outlet to the background canvas? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-06-16 10:56 Message: something doesn't have to be a feature OR a bug. it can also be neither, in the grey area, without status nor reason for being whichever way, and there isn't necessarily a reason for it to be any different either. ---------------------------------------------------------------------- Comment By: IOhannes m zmlnig (zmoelnig) Date: 2009-06-16 10:51 Message: was it you that just said "so you can't tell whether it's a bug or a feature, and you can reasonably argue for either"? for instance (totally unrelated) you can just duplicate an object with Ctrl-C Ctrl-V and you cannot visually distinguish the two instances (a common pitfall for newbies and oldies). if this would be removed i would be really upset. however, of course i cannot think of being very upset if the duplicate-connection was removed. i just don't think it's a bug - leaving only the "feature" option... also i am not aware of the truth of "the Pd language as its defined has no way to handle multiple connections from the same outlet to the same inlet". please give a reference. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-06-16 10:37 Message: zmoelnig, whenever you do anything with pd, you must know what you're doing, and it's also easily possible to keep track of multiple connections if the editor allowed them, by using comment (ctrl-5) or a piece of napkin. As a hypothetical question, if canvas_connect disallowed multiple connections, would you really request a multiple connection feature? see also the article "Real Programmers Don't Use Pascal"... ---------------------------------------------------------------------- Comment By: Hans-Christoph Steiner (eighthave) Date: 2009-06-16 10:29 Message: First, the Pd language as its defined has no way to handle multiple connections from the same outlet to the same inlet. The implementation might. The second question then is, is there ever a reason that duplicate connections would be used? They seem to add nothing but confusion. I don't consider confusion a feature. ---------------------------------------------------------------------- Comment By: IOhannes m zmlnig (zmoelnig) Date: 2009-06-16 10:13 Message: i would argue that it is a feature. when programmatically creating patches, you really MUST know what you are doing. it is easily possible to keep track of which connections you have done already, so you don't need to double-connect... ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-06-15 19:21 Message: this happens in canvas_connect in src/g_editor.c and happens in _all_ versions of pd ever, all OSes, etc. it is officially undocumented, so you can't tell whether it's a bug or a feature, and you can reasonably argue for either. ---------------------------------------------------------------------- Comment By: Johannes (jpburstrom) Date: 2009-06-15 19:10 Message: Sorry, here's some more: This is a problem with both pd-0.41.4-extended and pd-0.42.5, on my 64-bit ubuntu 9.04. It seems to happen regardless of sound card and audio API. ---------------------------------------------------------------------- Comment By: Hans-Christoph Steiner (eighthave) Date: 2009-06-15 19:03 Message: Please provide as detailed information as possible including which operating system (OS), CPU type, specific hardware, and the exact distro and version of Pd itself, etc. For example: Pd version 0.41.4-extended Mac OS X 10.5.7/Intel built-in sound ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2806856&group_…

1 0

[ pure-data-Bugs-2806856 ] Possible to connect the same in/outlets multiple times
by SourceForge.net 16 Jun '09

16 Jun '09

Bugs item #2806856, was opened at 2009-06-15 18:30 Message generated for change (Comment added) made by eighthave You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2806856&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: Pending Resolution: None Priority: 5 Private: No Submitted By: Johannes (jpburstrom) Assigned to: Nobody/Anonymous (nobody) Summary: Possible to connect the same in/outlets multiple times Initial Comment: When connecting objects through dynamic patching, pd can connect an outlet several times to the same inlet if sending the same message many times. The attached patch shows this behaviour, and why it can lead to strange and hard to find bugs. ---------------------------------------------------------------------- >Comment By: Hans-Christoph Steiner (eighthave) Date: 2009-06-16 12:13 Message: IOhannes, its hard to find documentation for things that are not features in software. People usually do not document things that are not included in software, because that documentation would be endless and useless. I can say that duplicate connections is not mentioned in any of the reference materials. Do I need a reference to say that you cannot connect an outlet to the background canvas? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-06-16 10:56 Message: something doesn't have to be a feature OR a bug. it can also be neither, in the grey area, without status nor reason for being whichever way, and there isn't necessarily a reason for it to be any different either. ---------------------------------------------------------------------- Comment By: IOhannes m zmlnig (zmoelnig) Date: 2009-06-16 10:51 Message: was it you that just said "so you can't tell whether it's a bug or a feature, and you can reasonably argue for either"? for instance (totally unrelated) you can just duplicate an object with Ctrl-C Ctrl-V and you cannot visually distinguish the two instances (a common pitfall for newbies and oldies). if this would be removed i would be really upset. however, of course i cannot think of being very upset if the duplicate-connection was removed. i just don't think it's a bug - leaving only the "feature" option... also i am not aware of the truth of "the Pd language as its defined has no way to handle multiple connections from the same outlet to the same inlet". please give a reference. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-06-16 10:37 Message: zmoelnig, whenever you do anything with pd, you must know what you're doing, and it's also easily possible to keep track of multiple connections if the editor allowed them, by using comment (ctrl-5) or a piece of napkin. As a hypothetical question, if canvas_connect disallowed multiple connections, would you really request a multiple connection feature? see also the article "Real Programmers Don't Use Pascal"... ---------------------------------------------------------------------- Comment By: Hans-Christoph Steiner (eighthave) Date: 2009-06-16 10:29 Message: First, the Pd language as its defined has no way to handle multiple connections from the same outlet to the same inlet. The implementation might. The second question then is, is there ever a reason that duplicate connections would be used? They seem to add nothing but confusion. I don't consider confusion a feature. ---------------------------------------------------------------------- Comment By: IOhannes m zmlnig (zmoelnig) Date: 2009-06-16 10:13 Message: i would argue that it is a feature. when programmatically creating patches, you really MUST know what you are doing. it is easily possible to keep track of which connections you have done already, so you don't need to double-connect... ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-06-15 19:21 Message: this happens in canvas_connect in src/g_editor.c and happens in _all_ versions of pd ever, all OSes, etc. it is officially undocumented, so you can't tell whether it's a bug or a feature, and you can reasonably argue for either. ---------------------------------------------------------------------- Comment By: Johannes (jpburstrom) Date: 2009-06-15 19:10 Message: Sorry, here's some more: This is a problem with both pd-0.41.4-extended and pd-0.42.5, on my 64-bit ubuntu 9.04. It seems to happen regardless of sound card and audio API. ---------------------------------------------------------------------- Comment By: Hans-Christoph Steiner (eighthave) Date: 2009-06-15 19:03 Message: Please provide as detailed information as possible including which operating system (OS), CPU type, specific hardware, and the exact distro and version of Pd itself, etc. For example: Pd version 0.41.4-extended Mac OS X 10.5.7/Intel built-in sound ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2806856&group_…

1 0

[ pure-data-Bugs-2807222 ] list-view of tables not working on PdX
by SourceForge.net 16 Jun '09

16 Jun '09

Bugs item #2807222, was opened at 2009-06-16 17:27 Message generated for change (Settings changed) made by zmoelnig You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2807222&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.41 Status: Open Resolution: None Priority: 5 Private: No Submitted By: IOhannes m zmlnig (zmoelnig) >Assigned to: Hans-Christoph Steiner (eighthave) Summary: list-view of tables not working on PdX Initial Comment: with the latest and greatest Pd-extended (0.41.4), the list-view of tables does not work any more reproduce: 1 create [table bla] 2 open table 3 right-click->preferences 4 click "view list" in the array-window 5 error 'wrong # args: should be "array_viewlist id"' confirmed on debian, ubuntu hoary, hoary/studio and w32/vista ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2807222&group_…

1 0

[ pure-data-Bugs-2807222 ] list-view of tables not working on PdX
by SourceForge.net 16 Jun '09

16 Jun '09

Bugs item #2807222, was opened at 2009-06-16 17:27 Message generated for change (Tracker Item Submitted) made by zmoelnig You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2807222&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: IOhannes m zmlnig (zmoelnig) Assigned to: Nobody/Anonymous (nobody) Summary: list-view of tables not working on PdX Initial Comment: with the latest and greatest Pd-extended (0.41.4), the list-view of tables does not work any more reproduce: 1 create [table bla] 2 open table 3 right-click->preferences 4 click "view list" in the array-window 5 error 'wrong # args: should be "array_viewlist id"' confirmed on debian, ubuntu hoary, hoary/studio and w32/vista ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2807222&group_…

1 0

[ pure-data-Bugs-2806856 ] Possible to connect the same in/outlets multiple times
by SourceForge.net 16 Jun '09

16 Jun '09

Bugs item #2806856, was opened at 2009-06-15 22:30 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2806856&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: Pending Resolution: None Priority: 5 Private: No Submitted By: Johannes (jpburstrom) Assigned to: Nobody/Anonymous (nobody) Summary: Possible to connect the same in/outlets multiple times Initial Comment: When connecting objects through dynamic patching, pd can connect an outlet several times to the same inlet if sending the same message many times. The attached patch shows this behaviour, and why it can lead to strange and hard to find bugs. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-06-16 14:56 Message: something doesn't have to be a feature OR a bug. it can also be neither, in the grey area, without status nor reason for being whichever way, and there isn't necessarily a reason for it to be any different either. ---------------------------------------------------------------------- Comment By: IOhannes m zmlnig (zmoelnig) Date: 2009-06-16 14:51 Message: was it you that just said "so you can't tell whether it's a bug or a feature, and you can reasonably argue for either"? for instance (totally unrelated) you can just duplicate an object with Ctrl-C Ctrl-V and you cannot visually distinguish the two instances (a common pitfall for newbies and oldies). if this would be removed i would be really upset. however, of course i cannot think of being very upset if the duplicate-connection was removed. i just don't think it's a bug - leaving only the "feature" option... also i am not aware of the truth of "the Pd language as its defined has no way to handle multiple connections from the same outlet to the same inlet". please give a reference. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-06-16 14:37 Message: zmoelnig, whenever you do anything with pd, you must know what you're doing, and it's also easily possible to keep track of multiple connections if the editor allowed them, by using comment (ctrl-5) or a piece of napkin. As a hypothetical question, if canvas_connect disallowed multiple connections, would you really request a multiple connection feature? see also the article "Real Programmers Don't Use Pascal"... ---------------------------------------------------------------------- Comment By: Hans-Christoph Steiner (eighthave) Date: 2009-06-16 14:29 Message: First, the Pd language as its defined has no way to handle multiple connections from the same outlet to the same inlet. The implementation might. The second question then is, is there ever a reason that duplicate connections would be used? They seem to add nothing but confusion. I don't consider confusion a feature. ---------------------------------------------------------------------- Comment By: IOhannes m zmlnig (zmoelnig) Date: 2009-06-16 14:13 Message: i would argue that it is a feature. when programmatically creating patches, you really MUST know what you are doing. it is easily possible to keep track of which connections you have done already, so you don't need to double-connect... ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-06-15 23:21 Message: this happens in canvas_connect in src/g_editor.c and happens in _all_ versions of pd ever, all OSes, etc. it is officially undocumented, so you can't tell whether it's a bug or a feature, and you can reasonably argue for either. ---------------------------------------------------------------------- Comment By: Johannes (jpburstrom) Date: 2009-06-15 23:10 Message: Sorry, here's some more: This is a problem with both pd-0.41.4-extended and pd-0.42.5, on my 64-bit ubuntu 9.04. It seems to happen regardless of sound card and audio API. ---------------------------------------------------------------------- Comment By: Hans-Christoph Steiner (eighthave) Date: 2009-06-15 23:03 Message: Please provide as detailed information as possible including which operating system (OS), CPU type, specific hardware, and the exact distro and version of Pd itself, etc. For example: Pd version 0.41.4-extended Mac OS X 10.5.7/Intel built-in sound ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2806856&group_…

1 0

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 June 2009