[PD-dev] [ pure-data-Bugs-3497473 ] [grid] not working in pd-extended 0.43.1
Bugs item #3497473, was opened at 2012-03-06 02:37 Message generated for change (Tracker Item Submitted) made by hellocatfood You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=478070aid=3497473group_id=55736 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.43 Status: Open Resolution: None Priority: 5 Private: No Submitted By: hellocatfood (hellocatfood) Assigned to: Hans-Christoph Steiner (eighthave) Summary: [grid] not working in pd-extended 0.43.1 Initial Comment: I'm still getting this error when attempting to edit the properties of [grid]: invalid command name pd invalid command name pd while executing pd $cmd (procedure grid_apply line 32) invoked from within grid_apply .gfxstub9fc7918 invoked from within .gfxstub9fc7918.buttonframe.apply invoke (uplevel body line 1) invoked from within uplevel #0 [list $w invoke] (procedure tk::ButtonUp line 22) invoked from within tk::ButtonUp .gfxstub9fc7918.buttonframe.apply (command bound to event) I turned on verbose mode and found that [grid] was being loaded from here: tried /usr/lib/pd-extended/extra/unauthorized/grid.pd_linux and succeeded I've tried removing that file but can't use [grid] without it. It appears it's not/can't load it from anywhere else. Should it be loading it from somewhere else? -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=478070aid=3497473group_id=55736 ___ Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
[PD-dev] [ pure-data-Patches-3497084 ] fix for open_via_path() declaration headfizz
Patches item #3497084, was opened at 2012-03-05 09:41 Message generated for change (Comment added) made by mathieubouchard You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=478072aid=3497084group_id=55736 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-dev Group: None Status: Open Resolution: None Priority: 7 Private: No Submitted By: IOhannes m zmölnig (zmoelnig) Assigned to: Miller Puckette (millerpuckette) Summary: fix for open_via_path() declaration headfizz Initial Comment: m_pd.h says that the parameters for open_via_path() are: open_via_path(name, ext, dir, ...) otoh, s_path.c implements the function as open_via_path(dir, name, ext,...) also the function is used as (dir, name, ext,...) throughout the code. the attached cosmetic patch fixes the function declaration in m_pd.h, so i don't get headfizz whenever i try to find out why i'm using the function correctly. -- Comment By: Mathieu BOUCHARD (mathieubouchard) Date: 2012-03-06 07:34 Message: Just imagine that the ministry of transportation puts the wrong signs on the autobahn. When it's time to fix them, they call the change «cosmetic». So, of course, they ask a beautician to take care of it. Do any changes to the docs also count as «cosmetic» ? Because help-intro.pd always listed classes that never existed, such as [powtorms~] and [rmstopow~]. I suppose that it's cosmetic too ? -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=478072aid=3497084group_id=55736 ___ Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
[PD-dev] problem with routing mail to pd-dev ?
I just wrote a comment in « [grid] not working in pd-extended 0.43.1 » and it didn't go through to the pd-dev list. I'm wondering what the selection process is, for routing those comments to pd-dev. I wrote it while logged in to sourceforge (using my new account, not the one I used years ago). My other comment with the same account went through, today, some minutes before. https://sourceforge.net/tracker/?func=detailatid=478070aid=3497473group_id=55736 __ | Mathieu BOUCHARD - téléphone : +1.514.383.3801 - Montréal, QC___ Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] problem with routing mail to pd-dev ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-03-06 17:46, Mathieu Bouchard wrote: I just wrote a comment in « [grid] not working in pd-extended 0.43.1 » and it didn't go through to the pd-dev list. I'm wondering what the selection process is, for routing those comments to pd-dev. I wrote it while logged in to sourceforge (using my new account, not the one I used years ago). My other comment with the same account went through, today, some minutes before. https://sourceforge.net/tracker/?func=detailatid=478070aid=3497473group_id=55736 i'm not sure i fully understand your problem. since some time, hans has disabled the automatic email notifications of follow-ups in the Bugs tracker. i checked and it seems that in the Patch tracker, still has the notifications for follow-ups enabled. could that be the cause of your troubles? fgmasdr IOhannes PS: on the pd-dev side no special routing is done (apart from allowing all mails coming from sourceforge) PPS: i'm pretty sure that the not/appearance of your mail has anything todo with your new account -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9WQjIACgkQkX2Xpv6ydvRpfQCeMrzcfKx854IUb/RoNiRGrnMk jWwAn3tI/RoWoBQwSSRHXn6ZRjtV6hDI =FKte -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] problem with routing mail to pd-dev ?
Le 2012-03-06 à 17:58:00, IOhannes m zmoelnig a écrit : i'm not sure i fully understand your problem. since some time, hans has disabled the automatic email notifications of follow-ups in the Bugs tracker. i checked and it seems that in the Patch tracker, still has the notifications for follow-ups enabled. could that be the cause of your troubles? Well, I'm not going to say that I'm for nor against having such notifications, but those settings don't seem very consistent, and I cannot guess why this is set up in this manner. I would guess that most other subscribers of pd-dev have no idea either ? __ | Mathieu BOUCHARD - téléphone : +1.514.383.3801 - Montréal, QC___ Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
[PD-dev] [ pure-data-Bugs-3497862 ] midiout sysex fail
Bugs item #3497862, was opened at 2012-03-06 10:42 Message generated for change (Tracker Item Submitted) made by ailo-at You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=478070aid=3497862group_id=55736 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.43 Status: Open Resolution: None Priority: 5 Private: No Submitted By: ailo (ailo-at) Assigned to: Hans-Christoph Steiner (eighthave) Summary: midiout sysex fail Initial Comment: I'm unable to send midi sysex messages through midiout to my external device using pd-extended 0.43-1 (daily build). I've double checked and found that pd vanilla 0.43.1-1 (debian wheezy) does not have this problem. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=478070aid=3497862group_id=55736 ___ Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
