Hi,
with Pd 0.47 in Debian dynamically deleting objects does not work anymore.
When I open my abstraction https://github.com/residuum/Puredata-abstractions/blob/master/glue/switch-ma..., I get an error in the console
(Tcl) INVALID COMMAND NAME: invalid command name ".find.entry" while executing ".find.entry get" (procedure "pdtk_showfindresult" line 10) invoked from within "pdtk_showfindresult .x90a2a58 1 1 35" ("uplevel" body line 483) invoked from within "uplevel #0 $docmds"
and a series of
error: consistency check failed: sys_decodedialog: inlet
followed by a series of
error: .x90a2a58: no such object
I boils down to the subpatch "delete-inlets", which is a series of
[$0 find inlet 1(
[$0 findagain(
[$0 cut(
[$0 dirty 0, menuclose 1(
Has there a change in the implementation of [; find( or [; findagain(?
Thanks, Thomas
I made some changes in the "find" dialog and its communications with Pd - sorry if this has (apparently) mixed things up. (I keep wanting to make some sort of "delete" message to canvases but can't figure out what would be a usable design).
Miller
On Sun, Jun 19, 2016 at 01:36:00AM +0200, Thomas Mayer wrote:
Hi,
with Pd 0.47 in Debian dynamically deleting objects does not work anymore.
When I open my abstraction https://github.com/residuum/Puredata-abstractions/blob/master/glue/switch-ma..., I get an error in the console
(Tcl) INVALID COMMAND NAME: invalid command name ".find.entry" while executing ".find.entry get" (procedure "pdtk_showfindresult" line 10) invoked from within "pdtk_showfindresult .x90a2a58 1 1 35" ("uplevel" body line 483) invoked from within "uplevel #0 $docmds"
and a series of
error: consistency check failed: sys_decodedialog: inlet
followed by a series of
error: .x90a2a58: no such object
I boils down to the subpatch "delete-inlets", which is a series of
[$0 find inlet 1(
[$0 findagain(
[$0 cut(
[$0 dirty 0, menuclose 1(
Has there a change in the implementation of [; find( or [; findagain(?
Thanks, Thomas -- "As long as people kept worrying that the machines were taking over, they wouldn't notice what was really happening. Which was that the programmers were taking over." (Robert Anton Wilson - The Homing Pidgeons) http://www.residuum.org/
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
On 2016-06-20 03:38, Miller Puckette wrote:
(I keep wanting to make some sort of "delete" message to canvases but can't figure out what would be a usable design).
what's wrong with the index that can be found everywhere else? e.g. iemguts adds a "delete" message (to the canvas) that takes a single number: https://git.iem.at/pd/iemguts/blob/master/src/canvasdelete.c
(actually it takes a list of numbers, but i've never used that).
so using "delete <index>" whould be:
fgamsdr IOhannes
Hi,
On 20.06.2016 09:29, IOhannes m zmoelnig wrote:
On 2016-06-20 03:38, Miller Puckette wrote:
(I keep wanting to make some sort of "delete" message to canvases but can't figure out what would be a usable design).
what's wrong with the index that can be found everywhere else? e.g. iemguts adds a "delete" message (to the canvas) that takes a single number: https://git.iem.at/pd/iemguts/blob/master/src/canvasdelete.c
(actually it takes a list of numbers, but i've never used that).
so using "delete <index>" whould be: - consistent with the current user-interface (e.g. "connect") - backward compatible with prior implementations
Thanks, [delete( from iemguts' [canvasdelete] is just what I needed, and makes it even clearer.
"Anything can be a tool - poverty, war. War is useful because it is effective in so many areas." (Bijaz to Hayt in: Frank Herbert - Dune Messiah) http://www.residuum.org/