Hi Krzysztof,
At this point I have been able to get closer to what I need with an external in two days than I have been able to in weeks of toxy tinkering. This is a short term solution at this point, as a deadline is drawing near.
I will continue working with Toxy though, and I reallt think it has great potencial. I do find it a little chalanging to work with toxy, especially lower-level things like the width of the popup widget, the size and shape of the bounding box etc.. Are you working on a language reference for toxy? I found the biggest stumbling having to be always asking you personally what things mean and how to deal with them.
If you end up making a text widget example, that returns a list of text items in the examples I'll be very likely to use that in my project, but I may just be able to make an external with the same functionality in less time.
I really do appreciate your efforts in the development of toxy, and taking the time to answer my questions. Your work is highly appreciated.
Thanks Ben
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.
At least, there are no fundamental stability, nor performance gains I can think of...
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.