On Thu, 19 Feb 2004, Krzysztof Czaja wrote:
hi Ben (and Guenter?),
in a short-term project you will probably find yourself on a safer side, since toxy is still very immature.
Taking a longer-term view, however, I do not understand, why should anybody prefer writing and maintaining (esp. through Pd api changes) a few-hundred-or-more-line external, to a few lines of a simple Tcl code, which has to be embedded in that external, anyway.
Well, I can only reiterate that I am not really happy with the approach that I have taken in these externals.
I didn't know about toxy at that time, if I had known, or if toxy already existed, probably I would not have changed them to use native tcl/tk widgets.
Remember, most of the sliders, bangs, toggles etc that are in the iemgui came from my external collection, so the only options I had was making mine different or removing them completely. I made them different in order to test the embedding of standard widgets.
At least, there are no fundamental stability, nor performance gains I can think of...
Absolutely right.
Guenter
Krzysztof
B. Bogart wrote: ...
I'm almost finished [popup], with a couple bugs and the biggest issue being that I can't figure out how to pass data from the tk widget back to pd.. (telling it what menu item was selected!) in GGEE button.c seems to do the magic here, could someone explain whats really going on?
sprintf(buf,"button%p",x); x->x_sym = gensym(buf); pd_bind(&x->x_obj.ob_pd, x->x_sym);
sys_vgui("proc button_cb%x {} {\n pd [concat button%p b \;]\n }\n",x,x);
defines a procedure to be configured into a button's -command. The proc, when invoked, sends a 'b' message to the object.
PD-dev mailing list PD-dev@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-dev