Re: [PD-dev] run-up to release 0.43
On Tue, Aug 31, 2010 at 4:02 AM, Hans-Christoph Steiner h...@at.or.atwrote: That's a bug in the command line flag parsing, you should file a bug report. IMHO, the whole flag parser should be rewritten using on of the standard opt/flag parsing libraries. getopt is in libc but is more limited, I am sure there is a GNU parser that handles -s short and --long options well. http://sourceforge.net/projects/argopt/ (inactive project, wonder if it's usable yet) http://directory.fsf.org/project/popt/ (x11 licence) i don't know is this is serious enough: http://wiki.tcl.tk/22050 Andras ___ Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] run-up to release 0.43
On Tue, 2010-08-31 at 22:04 +0200, András Murányi wrote: On Tue, Aug 31, 2010 at 4:02 AM, Hans-Christoph Steiner h...@at.or.at wrote: That's a bug in the command line flag parsing, you should file a bug report. IMHO, the whole flag parser should be rewritten using on of the standard opt/flag parsing libraries. getopt is in libc but is more limited, I am sure there is a GNU parser that handles -s short and --long options well. http://sourceforge.net/projects/argopt/ (inactive project, wonder if it's usable yet) http://directory.fsf.org/project/popt/ (x11 licence) i don't know is this is serious enough: http://wiki.tcl.tk/22050 Well, we'd want it to be something that is already widely deployed, like something in GNU libc or POSIX. popt looks pretty well used, at least on Debian/Ubuntu, but I think getopt() and getopt_long() are just about everywhere by default now. .hc ___ Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] run-up to release 0.43
That's a bug in the command line flag parsing, you should file a bug report. IMHO, the whole flag parser should be rewritten using on of the standard opt/flag parsing libraries. getopt is in libc but is more limited, I am sure there is a GNU parser that handles -s short and --long options well. .hc On Thu, 2010-08-26 at 12:34 +0200, cyrille henry wrote: hello, i've got a new problem with this test version. yesterday, i add -font-face andale mono in pd startup preference. now, when i try to open this preference dialog, i have this error : (Tcl) UNHANDLED ERROR: extra characters after close-quote while executing pdtk_startup_dialog .gfxstuba0f0fd0 0 -listdev -mididev 1,2,3,4 -font-face andale mono -noautopatch -rt -alsa -alsaadd default -audiooutdev 3 (uplevel body line 5) invoked from within uplevel #0 $cmd_from_pd cheers cyrille Le 19/08/2010 02:06, Miller Puckette a écrit : Hi all, I have only 2 weeks left in the vicinity of my usual collection of testing machines (will be in New York Sept 1 - Jan. 1!) and so should probably try to get 0.43 finalized. I have several bugs to work on but I think the whole thing is ready to put out compiled test versions for people to exercise. I'll try not to add new features but just fix bugs for the next 2 weeks -- I'll have all fall for the next bunch of features (including, perhaps, the ones I've been trying to find time to work on). I'll do my usual compiling and spot testing, hopefully putting out the test versions within the next day. cheers Miller ___ Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev ___ Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] run-up to release 0.43
hello, i've got a new problem with this test version. yesterday, i add -font-face andale mono in pd startup preference. now, when i try to open this preference dialog, i have this error : (Tcl) UNHANDLED ERROR: extra characters after close-quote while executing pdtk_startup_dialog .gfxstuba0f0fd0 0 -listdev -mididev 1,2,3,4 -font-face andale mono -noautopatch -rt -alsa -alsaadd default -audiooutdev 3 (uplevel body line 5) invoked from within uplevel #0 $cmd_from_pd cheers cyrille Le 19/08/2010 02:06, Miller Puckette a écrit : Hi all, I have only 2 weeks left in the vicinity of my usual collection of testing machines (will be in New York Sept 1 - Jan. 1!) and so should probably try to get 0.43 finalized. I have several bugs to work on but I think the whole thing is ready to put out compiled test versions for people to exercise. I'll try not to add new features but just fix bugs for the next 2 weeks -- I'll have all fall for the next bunch of features (including, perhaps, the ones I've been trying to find time to work on). I'll do my usual compiling and spot testing, hopefully putting out the test versions within the next day. cheers Miller ___ Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev ___ Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] run-up to release 0.43
--- On Fri, 8/20/10, Matt Barber brbrof...@gmail.com wrote: From: Matt Barber brbrof...@gmail.com Subject: Re: [PD-dev] run-up to release 0.43 To: Jonathan Wilkes jancs...@yahoo.com Cc: pd-dev@iem.at Date: Friday, August 20, 2010, 5:59 PM As for [initbang] - my only use has been for making abstractions that can spawn a variable number of inlets/outlets. That's the only way I've used it and the only way I've ever seen it used-- if there are other uses maybe someone else on this list can give an example. The [initbang] object gives abstractions the ability to do something that otherwise would only be possible by coding an external in another programming language. For example, with [initbang] I can quickly make an abstraction that can act like Max/MSP's [trigger] object-- where you can specify numeric values as arguments ( like [trigger b 0] ). In other words, you want Pd to include meta capabilities enough that abstractions have all the functionality of coded objects. [initbang] would be one step in this direction, but there would be at least these other requirements: I'm interested in that, too, but the main reason I ask about [initbang] is because its patch has been sitting there on Sourceforge since 2006, and has been used in Pd-ext since then (and I haven't found any bugs so far with it) but not in Vanilla. If you do as the Sourceforge comments suggest and search the archives you'll not only find reasons for why the object is needed as I've suggested here, but also requests by developers (including yourself, I think) for the object to be included as an internal Pd object. To make a max-compatible [trigger] I don't need any of the other meta-features you mention (which are good ideas). I just need [initbang]. It only has one outlet, and I've never needed more than one in an abstraction. So if future-[loadbang]-with-args were implemented tomorrow I'd just need to change one object for my max-compatible [trigger] to work across all Pd versions. -Jonathan ___ Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] run-up to release 0.43
On 08/19/2010 02:06 AM, Miller Puckette wrote: I'll try not to add new features but just fix bugs for the next 2 weeks -- here is one bug (+ fix): pd -version prints garbage. https://sourceforge.net/tracker/?func=detailaid=3050371group_id=55736atid=478072 mgfasdr IOhannes signature.asc Description: OpenPGP digital signature ___ Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] run-up to release 0.43
On 08/21/2010 06:32 PM, IOhannes zmölnig wrote: On 08/19/2010 02:06 AM, Miller Puckette wrote: I'll try not to add new features but just fix bugs for the next 2 weeks -- here is one bug and of course there are several simple bugfixes still pending in the tracker: e.g. 2806049: [bugfix] renamed arrays do not get used by dsp 2835752: floor, ceil functions in expr misdeclared those are really simple, about 2 lines code each. gmasdr IOhannes signature.asc Description: OpenPGP digital signature ___ Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
