Pd-dev June 2005

pd-dev@lists.iem.at

22 participants
69 discussions

Re: [PD-dev] external failure OS X
by steve symons 15 Jun '05

15 Jun '05

Whoa. OK this does explain why PD doesn't seem to find the framework, thanks for putting this together for me Martin. Though I can't help wondering that as the code's for a hardware interface I would be better writing an OSC server, so its external to PD. Not sure that many people outside of this list would go for a recompile. steve > Date: Tue, 14 Jun 2005 20:10:50 +0200 > From: martin pichlmair <pi(a)attacksyour.net> > Subject: Re: [PD-dev] external failure OS X > To: pd-dev <pd-dev(a)iem.kug.ac.at> > Message-ID: <3FA8B2C6-C217-49B6-BB12-BCC5678AECDF(a)attacksyour.net> > Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed > > > it might be a good guess that this is another incident of the well > known osx linking issue: > > from jamie (on may 2nd): > ------------------------8<------ > ...this is probably because you are using that s_loader patched > version of pd, right? If so, then you may need to change the linking > of OSC's compile from flat_namespace to two_level_namespace (which is > default, so you don't really need to add it)...or rather preferably > use -bundle -bundle_loader /where/is/your/installed/pd/binary > ------------------------>8------ > > the "patched version" was talked upon on december 9th 2004 - also > jamie: > ------------------------8<------ > ...the OSX version of pd uses the following in s_loader.c to load > externals: > > ret = NSLinkModule( image, filename, > NSLINKMODULE_OPTION_BINDNOW + NSLINKMODULE_OPTION_PRIVATE ); > > ...pdp2gem will load if I remove NSLINKMODULE_OPTION_PRIVATE, which > brings up my question: will removing this cause other problems? > ------------------------>8------ > > patching + recompiling pd and changing _your external's_ link style > from flat to two-level + bundle(_loader) should work. lest it did for > me when linking to a lib. > > good luck > martin

1 0

zero / one element lists
by Tim Blechmann 15 Jun '05

15 Jun '05

hi miller, hi devs ... i had some problems with one element lists, once again. imo, we should try to avoid zero/one element lists in pd as good as possible.. it's easy to adapt route to do the type conversion (see attached patch) ... cheers ... tim -- mailto:TimBlechmann@gmx.de ICQ: 96771783 http://www.mokabar.tk latest mp3: kMW.mp3 http://mattin.org/mp3.html latest cd: Goh Lee Kwang & Tim Blechmann: Drone http://www.geocities.com/gohleekwangtimblechmannduo/ After one look at this planet any visitor from outer space would say "I want to see the manager." William S. Burroughs

2 2

Re: [PD-dev] small font/display change
by Hans-Christoph Steiner 15 Jun '05

15 Jun '05

Did you look at a text file in Pd with this patch? I guess I should have been more clear about where it applies. The Times font only applies to viewing text files in Pd, not to anything else. You cannot change the font size of a text file in Pd. So I spec'ed Times 14 over Courier 12. The font is definitely big enough, and can easily be made bigger if need be. I think that Times works well there because it clearly distinguishes the text files from the patches. Try opening up 2.control.examples/00.INTRO.txt for example. Its a minor change. Good point on the tk-style font specs, everything should be done that way. I'll try that now... .hc On Jun 9, 2005, at 4:09 PM, B. Bogart wrote: > Times!? please no! > > Keep courier or use a sans-serif like helvetica. > I think switching to tk font specs {helvetica -12 bold| would be better > than sticking with the funny X11 font spec. > > My 2cents. > > Times is just too fine for small text. sans-serif is the way to go. > > b> > > Hans-Christoph Steiner wrote: >> >> I would like to propose a minor font change to make text more >> readable. >> First, in the console, make the text regular rather than bold. >> Usually >> regular fonts are used in terminal windows and bold is only for >> highlights. >> >> -text .printout.text -relief raised -bd 2 -font >> -*-courier-bold--normal--12-* \ >> +text .printout.text -relief raised -bd 2 -font >> -*-courier-regular--normal--12-* \ >> >> Secondly, courier is not a font meant for reading text, but rather >> terminals and things like that. So I propose changing the default >> font >> in text windows (not used very often) to Times Regular 14 point. >> >> - text $name.text -relief raised -bd 2 -font >> -*-courier-bold--normal--12-* \ >> + text $name.text -relief raised -bd 2 -font >> -*-times-regular--normal--14-* \ >> >> Attached is a diff patch file. This should work on all platforms >> since >> those fonts are already used within Pd. Lastly is a Mac OS X only >> change: setting minimun line size for anti-aliasing. If set to 1 or >> 0, >> then every line will be anti-aliased. While this makes connections >> and >> circles in [bng] and such look really good, it makes boxes and >> messages >> look out of focus. Setting this to 2 makes it so only the thick audio >> rate connections are anti-aliased >> >> + set tk::mac::CGAntialiasLimit 2 >> >> .hc >> >> >> ______________________________________________________________________ >> __ >> ____ >> >> News is what people want to keep hidden and everything else is >> publicity. >> >> - Bill Moyers >> >> >> ---------------------------------------------------------------------- >> -- >> >> _______________________________________________ >> PD-dev mailing list >> PD-dev(a)iem.at >> http://lists.puredata.info/listinfo/pd-dev >> ________________________________________________________________________ ____ "The arc of history bends towards justice." - Dr. Martin Luther King, Jr.

2 2

Re: [PD-dev] external failure OS X
by IOhannes m zmoelnig 14 Jun '05

14 Jun '05

please answer to the mailinglist too (i read the mailinglist, but the mailinglist does not read my private mails) there are people there who have far more expertise in osx than me. mfg.asd.r IOhannes steve symons wrote: > Ah Thank you. I get this > > > Reading symbols for shared libraries . done > dyld: /Users/steve/Documents/puredata/Pd-0.38-3.app/Contents/Resources/ > Scripts/../bin/pd Undefined symbols: > _init_muio > pd_gui: pd process exited > > Program exited normally. > (gdb) bt > No stack. > (gdb) > > > Which suggests to me that PD is not finding the framework....? How do > I check its search paths? > > Steve > >

2 1

error compiling zexy on OSX from CVS
by Davide Morelli 14 Jun '05

14 Jun '05

Hi, I get this error compiling zexy on a osx (G4 10.3) am I missing something obvious? [...] cc -bundle -undefined suppress -flat_namespace -o zexy.pd_darwin *.o -lm -lc strip zexy.pd_darwin strip: symbols referenced by indirect symbol table entries that can't be stripped in: zexy.pd_darwin _class_sethelpsymbol _class_addanything _class_addlist _class_addpointer _class_addsymbol _class_doaddfloat _class_addbang _class_addcreator _class_new _outlet_new _pd_new _outlet_bang _outlet_pointer _outlet_symbol _outlet_float _freebytes _outlet_list _gensym _memcpy _getbytes _atom_getsymbol _error _atom_getfloat _strtol _class_addmethod _post _dsp_add _localtime _gmtime _gettimeofday _atom_string _inlet_new _outlet_anything _sys_getsr _floatinlet_new _clock_new _clock_free _clock_delay _clock_unset _copybytes _sqrt _bug _cos _strcmp _atom_getint _pow _endpost _poststring _log _dbtorms _rmstodb _exp _strcpy _strlen _sprintf _canvas_getcurrent _fclose _fwrite _fopen _binbuf_gettext _canvas_makefilename _binbuf_addsemi _binbuf_add _binbuf_free _binbuf_text _read _lseek _sys_bashfilename _strcat _close _open _open_via_path _binbuf_new _canvas_getdir _binbuf_getvec _binbuf_getnatom _postatom _startpost _memcmp _feof _fread _fseek _binbuf_clear _strstr _strtod _strncpy _garray_getfloatarray _pd_findbyclass _garray_redraw _fmod _class_domainsignalin _atom_getfloatarg make: *** [zexy] Error 1

1 0

external failure OS X
by steve symons 14 Jun '05

14 Jun '05

Hi Th have written an external that calls a framework. This basically contains a Struct (called muioObjRef) with a number of sub classes. Other wrappers to this framework are fine, but PD dies as soon as I load a patch that calls the external. Is there something obvious that I am overlooking? so having the line muioObjRef muio; is fine (where muioObjRef is defined within the framework). But then if I add the following in the constructor for the external muio = init_muio(); Where init_muio() returns either null or a completed muioObjRef depending on successful initialisation. PD dies without a even a whimper when I call the external. Any ideas are welcome! Steve

2 1

Apache as example for Pd decision making
by Hans-Christoph Steiner 13 Jun '05

13 Jun '05

Apache provides another example of how to organize a body of developers into a decision making body. http://www.apache.org/foundation/how-it-works.html I don't have time to offer more suggestions now, but I am going to check out the Apache model in depth soon. .hc ________________________________________________________________________ ____ If you are not part of the solution, you are part of the problem. - Eldridge Cleaver

1 0

popup,...
by IOhannes m zmoelnig 13 Jun '05

13 Jun '05

hi ben, hi list i just checked your [popup], like it and have submitted several (imo) improvements to the CVS. namely: - no restriction for max# of "options"; this might be not very interesting (as on my machine i can only display 40 options at one time, so 100 seems to be sufficient anyhow) BUT i added additionally checks whether the max# has been exceeded; this keeps [popup] from segfaulting when you have more than 100 options - using a mixture of user-defined and default values if you provide less than 5 arguments (i thought that 5 args are a bit much to remember) - removed the "loadbang"-constraint (you can now add options and select entries before the object has been drawn the 1st time) since i only tested it on linux, it would be great if somebody could tell me what i've broken... but i have some questions: - why are there 2 inlets ? i noticed you uncommented the class_addsymbol()-method, so it seems like there is some reason for not using the 1st inlet for both numeric and symbolic selection of elements. - even more puzzling: why are there 2 outlets ? for clarification, i don't have any problems with separate outlets for typfixed outlets (1 for numeric indices and 1 for symbolic names), but you are using the first outlet for 2 types (float vs. bang) so you somehow need a route to segregate those types. i would've suggested using either 1 outlet (with either ("bang" and "float" and "symbol") or ("bang" and "list") since now the "loadbang" seems to work, could the "bang" output be removed ? (i find it rather annoying that everytime i switch console (this is: unhide the window), a bang is emitted. but i guess, this would break a lot of patches.... mfg.as.dr IOhannes

3 6

[ pure-data-Patches-1217922 ] fix sendOSC string arg truncation
by SourceForge.net 10 Jun '05

10 Jun '05

Patches item #1217922, was opened at 2005-06-10 04: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=1217922&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 Submitted By: steven pickles (pixid) Assigned to: Nobody/Anonymous (nobody) Summary: fix sendOSC string arg truncation Initial Comment: for some reason, strings in outgoing osc messages are truncated to 80 characters, even when they are being read into a buffer that is 1000 characters long. i made this little fix so the buffer length being send to atom_string is actually the space remaining in the buffer. pd will segfault if you exceed this buffer, but that bug was there before this change. the osc spec doesn't seem to place a limit on the length of string arguments. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1217922&group_…

1 0

cross-platform font size
by Hans-Christoph Steiner 10 Jun '05

10 Jun '05

So a bunch of us are working on workshops and documentation and we are of course butting our heads against the font issue again. Does anyone have a good idea to fix this? I remember some talk about converting the fonts to pixel sizes rather than point sizes. That sounds like exactly what we should do. I've poked around a bit, but my Tcl skills are not so sharp. .hc ________________________________________________________________________ ____ "The arc of history bends towards justice." Dr. Martin Luther King, Jr.

4 6

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 2005