hi Ben,
it is wonderful you have invested so much time, with trust and patience. I feel sorry for not having more time for toxy myself, lately, causing much confusion, as it seems. Using it in a current project is a challenge I would not dare to advertise -- my other remark came out of a general concern about duplicating code, keeping developers in sync, etc.
Now, what bothers me, is the ``bounding box'' phenomenon:
B. Bogart wrote: ...
- The objects's bounding box changing side willy-nilly and being
altogether wrong on load. (I suppose this is a bug, but I can imagine the code to draw the box around an arbitrary widget could be a little complicated.) Actually I would prefer the non-selected bounding box just not be there, the widgets's themselves have sufficient borders. Only the blue on select box should remain, and its size does not need to be perfect.
I have never seen anything like that... perhaps, there is some incompatibility with the cvs branch of Pd? Even stranger is this:
$3 $4 $5 ...]. Also this lead to object boxes many times wider than the widget itself, making it awkward in a gui. I decided to try an external
You mean the text object box is still visible behind the widget? I am lost...
Also, changing menubutton's width is as simple, as sending '-width <nchars>' to its [tow], or including it in the argument list, or declaring in a .wid file -- everything works here, in linux, using Miller's branch (this might be the case of some osx peculiarity I am not aware of, though).
Configuring the menu is simple too, e.g. changing item's text on the fly with "tot .-.pop entryconfig <itemno> -label <newtext>", same with menu subcommands: 'add', 'delete', ...
Krzysztof