Pd-dev

pd-dev@lists.iem.at

2 participants
9620 discussions

Re: [PD-dev] roadmap for Pd-0.49?
by Miller Puckette 11 Sep '18

11 Sep '18

To Pd dev - I've finally got a version of Tck/Tk 8.5 patched for macintosh to work around the key-up bug (by back-porting the bugfix from 8.6 and then making a further mod - the fix is on msp.ucsd.edu/tmp/misc/tk8.5.19-pd49-src.tar.gz if anyone else wants to try it. Meanwhile I'm hoping to get 0.49 test1 out today - to do this I'll grab whatever small and uncontroversial PRs I can fold in without too much conflick-resolving and go on and compile everything. Some larger issues are still hanging, for instance, the dollar-zero idea - I don't think I can get these resolved quickly. Also, I have some difficulties dealing with PRs in general that I'd like to open a discussion about in another thread. Meanwhile, going forward, if I've mis-applied PRs (which I bet I have), I'm happy to try to resolve them during the test period, and I'm happy to try to fix remaining reported bugs (when the fix doesn't seem to risk introducing new problems) and merge bug-fixing PRs. cheers - and thanks to everyone who has contributed! Miller

2 2

Re: [PD-dev] roadmap for Pd-0.49?
by Dan Wilcox 10 Sep '18

10 Sep '18

I'd say this is a "paper cut." It's a small issue easily worked around by the addition of an extra step, but that extra step is painful due to it's repetition. Also, I've seen it be a confusing step for many beginners once they learn to use $0 in objects, ie [f $0], [symbol $0], etc. I'm on the side of $0 in message boxes. I don't see how this change would break anything since $0 currently resolves to 0 (I think), and I cannot imagine anyone relying on this. Is it a controversy? > On Sep 4, 2018, at 9:41 AM, pd-dev-request(a)lists.iem.at wrote: > > Date: Mon, 3 Sep 2018 21:02:39 -0700 > From: Miller Puckette <msp(a)ucsd.edu <mailto:msp@ucsd.edu>> > To: Alexandre Torres Porres <porres(a)gmail.com <mailto:porres@gmail.com>> > Cc: Henri Augusto Bisognini <msndohenri(a)hotmail.com <mailto:msndohenri@hotmail.com>>, pd-dev > <pd-dev(a)lists.iem.at <mailto:pd-dev@lists.iem.at>> > Subject: Re: [PD-dev] roadmap for Pd-0.49? > Message-ID: <20180904040239.GF25025(a)ucsd.edu <mailto:20180904040239.GF25025@ucsd.edu>> > Content-Type: text/plain; charset=us-ascii > > This one is mired in controversy. Meanwhile, you can get "$0" functionality > in a message box by preceeding it with "list prepend $0" so that $1 in the > message box is teh patch's $0 and the other $ arguments are renumbered by one. > > cheers > Miller -------- Dan Wilcox @danomatika <http://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>

2 1

Re: [PD-dev] savestate
by Dan Wilcox 10 Sep '18

10 Sep '18

What I was implying, then, is that if [savestate] brings this kind of functionality, albeit tangentially, then why not include specific [initbang] and [closebang] objects as well? That would solve a longstanding feature request without kludging the [savestate] mechanism which may/or may not change. > On Sep 8, 2018, at 12:00 PM, pd-dev-request(a)lists.iem.at wrote: > > Date: Fri, 7 Sep 2018 22:04:14 +0200 > From: IOhannes m zmölnig <zmoelnig(a)iem.at <mailto:zmoelnig@iem.at>> > To: pd-dev(a)lists.iem.at <mailto:pd-dev@lists.iem.at> > Subject: Re: [PD-dev] savestate > Message-ID: <0fc97332-28de-103d-22ab-61433ae33c77(a)iem.at <mailto:0fc97332-28de-103d-22ab-61433ae33c77@iem.at>> > Content-Type: text/plain; charset="utf-8" > > On 9/3/18 3:35 PM, Dan Wilcox wrote: >> Also, does the right outlet effectively act as a "save bang"? This might be tangentially useful for some data structure abstractions... > > what i find even more exiting, is that the left outlet effectively acts > as an "init bang", finally allowing you to create abstractions with a > dynamic number of iolets in Pd-vanilla (in a way that survives saving > both the abstraction and its containing patch). > > gfmard > IOhannes -------- Dan Wilcox @danomatika <http://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>

1 0

Fwd: bug in dollar sign handling
by Antoine Rousseau 07 Sep '18

07 Sep '18

Hi, dollar sign handling seems currently broken on master: [b]-[symbol $0-$0]-[print] returns: print: symbol 1003-\\$01003 I guess it could come from the recent backslashes related additions.

2 3

Re: [PD-dev] [PD] Setting Code::Blocks (MinGW64) to compile pd externals
by Christof Ressi 05 Sep '18

05 Sep '18

just to show you, how simple it is. this is how a complete makefile with pd-lib-builder might look like: --- # Makefile for mylib lib.name = mylib class.sources = myclass1.c myclass2.c datafiles = myclass1-help.pd myclass2-help.pd README.txt LICENSE.txt include Makefile.pdlibbuilder --- and building your external is as simple as: > cd /path/to/source > make PDDIR=/path/to/pd Christof > Gesendet: Mittwoch, 05. September 2018 um 16:33 Uhr > Von: "IOhannes m zmoelnig" <zmoelnig(a)iem.at> > An: pd-list(a)lists.iem.at > Betreff: Re: [PD] Setting Code::Blocks (MinGW64) to compile pd externals > > On 2018-09-05 16:25, alfonso santimone wrote: > > I have no good knowledge of cmake. > > to repeat christophs advice: > >> in your case I'd strongly suggest to use the pd-lib-builder makefile > >> template: https://github.com/pure-data/pd-lib-builder > > > Coding for pd and max is always a moving target :-D > > that's a bit far-fetched for an API that has been pretty stable for > about 20 years. > > fgasmkdr > IOhannes > > _______________________________________________ > Pd-list(a)lists.iem.at mailing list > UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list >

1 0

Re: [PD-dev] keep master on github stable
by Dan Wilcox 04 Sep '18

04 Sep '18

OpenFrameworks initially keep the master branch on the latest stable release and used a develop branch for active work. However, this led to many situations where submitters inadvertently did work on their copy of the develop branch and submitted PRs to the master branch. This led to all sorts of issues, especially to newer developers starting out with git. Thankfully it's *much* easier to change the PR branches now, but it still leads to confusion. For a project where users *only* really build the source code (ie. software libraries), then the "master as stable" approach is useful as it means the default clone is always stable. For projects where the majority of users download pre-built binaries (ie. Pd), I think "master as develop" makes sense since most people cloning will be building/developing the software and those that aren't can checkout a stable tag. So the emphasis is based on the predominant use case: in the former, the master as the release and the latter uses master as develop. > On Sep 4, 2018, at 4:53 AM, pd-dev-request(a)lists.iem.at wrote: > > Date: Tue, 4 Sep 2018 04:52:58 +0200 > From: "Christof Ressi" <christof.ressi(a)gmx.at <mailto:christof.ressi@gmx.at>> > To: "Miller Puckette" <msp(a)ucsd.edu <mailto:msp@ucsd.edu>> > Cc: pd-dev <pd-dev(a)lists.iem.at <mailto:pd-dev@lists.iem.at>> > Subject: Re: [PD-dev] keep master on github stable > Message-ID: > <trinity-24063e5f-6755-4798-b27d-4d08994e7ee5-1536029578754@3c-app-gmx-bs59> > > Content-Type: text/plain; charset=UTF-8 > > I see. The reason I was asking is that many OSS projects have both master and develop branches so people can choose between the latest stable version and the newest stuff (accepting possible regressions). So all the real work would happens on the develop branch and whenever a release is out (after the feedback and bug fixes from the test releases) the master branch gets updated. but this is just an idea for the future. don't bother now :-) > > Christof -------- Dan Wilcox @danomatika <http://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>

3 3

keep master on github stable
by Christof Ressi 04 Sep '18

04 Sep '18

hi, just a small question/suggestion: wouldn't it be better if we keep the current master on github to the last stable release (i.e. 0.48.2) and use a dedicated development branch for adding things? Christof

2 2

Using # in GUI object's label
by Henri Augusto Bisognini 04 Sep '18

04 Sep '18

Hi! I noticed all my labels on GUI objects containing "#" had it replaced with a "$". The only workaround i know of is using dynamic patching to create the object you want with a # in it's label but that's definetely not something that every PD user want/know how to use. Searching the mailing list i found this discussion about the raute2dollar method but it seems it was abandoned. We have any news on that? Discussion i found in the mailing list: https://lists.puredata.info/pipermail/pd-list/2015-11/111972.html On Mon, Nov 2 at 04:57 AM, Ivica Bukvic <ico at vt.edu > wrote: > so this sounds like a bug to me that does some sort of one-way mangling that needs to be fixed and more > so, it seems to me there should be a different ascii character used to preserve $, one that does not exist in the regular text-based ascii > chars... e.g. in pd-l2ork we use \t to substitute for \n and thus preserve endlines in comments and other places. Sounded like a good idea because # is definitely very useful for labels as it looks just like an sharp. I know there is an sharp char in DejaVu Sans Mono (♯) but it looks very small and is hard to read for some reason. So i changed the raute2dollar and the dollar2raute functions To use '\"' (quotation mark) instead of '#' and it broke PD. I even tried using something pretty normal in it's place ('A') but didn't work either. Assuming the replacing char was just that, a replacement, and that any other char would do, it seemed like a good idea. Figured if users couldn't use quotation marks (") in their labels they would just use two apostrophes (') which would look the same. PD loads normally but when you open a new windows you get a TCL error. Call stack is something like this ::pd_bindings::window_focusin .x229b790 ....::pd_menus::configure_for_canvas $mytoplevel ........update_undo_on_menu $mytoplevel ............("update_undo_on_menu" line 3) ............"if {$mytoplevel eq $::undo_toplevel && $::undo_action ne "no"} { ................$menubar.edit entryconfigure 0 -state normal -label [_ "Undo $::undo_action"..." So it seems that not only replacing the $ from some stuff is important but also what replaces it must be a '#'. I'm pretty new here so i can't get my head around what exactly is going on yet and why this is necessary. This Jonathan mail (below) seems to be the only explanation on why it was done this way in the first place but it doesn't go into much deta https://lists.puredata.info/pipermail/pd-list/2015-11/111968.html What exactly is the purpose of this? Is it really needed for the labels? Cheers Henri.

1 0

Re: [PD-dev] Two preferences menus
by Dan Wilcox 03 Sep '18

03 Sep '18

I think that's a mistake and probably a leftover when I last worked on the menus, mainly for macOS, or from deken. Is the menu listing the same for both menus? > On Sep 2, 2018, at 12:00 PM, pd-dev-request(a)lists.iem.at wrote: > > Date: Sun, 2 Sep 2018 03:15:20 +0000 > From: Henri Augusto Bisognini <msndohenri(a)hotmail.com <mailto:msndohenri@hotmail.com>> > To: "pd-dev(a)lists.iem.at <mailto:pd-dev@lists.iem.at>" <pd-dev(a)lists.iem.at <mailto:pd-dev@lists.iem.at>> > Subject: [PD-dev] Two preferences menus > Message-ID: > <RO1PR80MB04112923698ACCEC1B6699F2CC0D0(a)RO1PR80MB0411.lamprd80.prod.outlook.com <mailto:RO1PR80MB04112923698ACCEC1B6699F2CC0D0@RO1PR80MB0411.lamprd80.prod.outlook.com>> > > Content-Type: text/plain; charset="iso-8859-1" > > I've noticed there are two equal preferences menus on Windows and Ubuntu. > > File->Preferences > Edit->Preferences > > Is it intentional or some leftover after a change? -------- Dan Wilcox @danomatika <http://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>

1 1

Two preferences menus
by Henri Augusto Bisognini 02 Sep '18

02 Sep '18

I've noticed there are two equal preferences menus on Windows and Ubuntu. File->Preferences Edit->Preferences Is it intentional or some leftover after a change? Cheers Henri.

2 1

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