Bugs item #1738289, was opened at 2007-06-16 12:06 Message generated for change (Comment added) made by zmoelnig You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1738289...
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: Open
Resolution: Fixed
Priority: 3 Private: No Submitted By: Frank Barknecht (fbar) Assigned to: Miller Puckette (millerpuckette) Summary: "View list" listview broken for arrays with $0 in name
Initial Comment: The "View list" function in the Properties context menu of arrays is broken, if the name of the array contains a $0. This only affects visible arrays in graphs, arrays in [table] objects work correctly with $0-names.
See attached test patch for a demonstration.
The error message given by Tk is:
can't read "0": no such variable can't read "0": no such variable while executing "array_viewlist .gfxstub82e3a78 $0-array 0" invoked from within ".gfxstub82e3a78.listview invoke" ("uplevel" body line 1) invoked from within "uplevel #0 [list $w invoke]" (procedure "tk::ButtonUp" line 22) invoked from within "tk::ButtonUp .gfxstub82e3a78.listview" (command bound to event)
----------------------------------------------------------------------
Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2007-09-17 14:23
Message: Logged In: YES user_id=564396 Originator: NO
btw, the bug appeared with all uses of $args (e.g. $1-table is as bad as $0-array)
however, the tiny attached diff (against todays cvs of 0.41) fixes this bug by removing unneeded variables. File Added: array_viewlist.diff
----------------------------------------------------------------------
Comment By: Frank Barknecht (fbar) Date: 2007-06-18 11:09
Message: Logged In: YES user_id=569446 Originator: YES
Please don't use spaces in filenames here, their names get mangled by Sourceforge. I deleted the new example patch to not confuse readers. I think the first example I posted already was illustrating the bug sufficiently.
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave) Date: 2007-06-17 18:49
Message: Logged In: YES user_id=27104 Originator: NO
Yup, same for me on Mac OS X 10.4.9 using Pd-0.39.2-extended-rc4 and Pd 0.40-2. File Added: array with dollar zero.pd
----------------------------------------------------------------------
Comment By: Frank Barknecht (fbar) Date: 2007-06-17 11:14
Message: Logged In: YES user_id=569446 Originator: YES
It seems any version is affected.
I tested with CVS HEAD (0.4x) and pd-ext 0.39 rc-2.
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave) Date: 2007-06-17 03:31
Message: Logged In: YES user_id=27104 Originator: NO
Which version of Pd? I hope it's not my bug ;) The version can be set in the "Group" pulldown menu in the bug report form.
----------------------------------------------------------------------
You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1738289...
SourceForge.net wrote:
Bugs item #1738289, was opened at 2007-06-16 12:06 File Added: array_viewlist.diff
i was just wondering: when a bug-report gets a fix (e.g. a patch-file), should it be moved from the "bugs" section to the "patches" section or should it stay within the "bugs".
the question is: which one get's accepted more easily? i can imagine that it is not so much fun for e.g. miller to look through all bug-reports to see whether there is already a fix for it (if the bug is minor enough, miller would probably not care to fix it himself, but if a fix was ready at hand, why not apply it?)
mga.sdr IOhannes
On Sep 17, 2007, at 8:34 AM, IOhannes m zmoelnig wrote:
SourceForge.net wrote:
Bugs item #1738289, was opened at 2007-06-16 12:06 File Added: array_viewlist.diff
i was just wondering: when a bug-report gets a fix (e.g. a patch- file), should it be moved from the "bugs" section to the "patches" section or should it stay within the "bugs".
the question is: which one get's accepted more easily? i can imagine that it is not so much fun for e.g. miller to look through all bug-reports to see whether there is already a fix for it (if the bug is minor enough, miller would probably not care to fix it himself, but if a fix was ready at hand, why not apply it?)
I think once it gets a patch attached, it should be moved to the patches section.
.hc
mga.sdr IOhannes
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
------------------------------------------------------------------------ ----
¡El pueblo unido jamás será vencido!