I have made some changes to tkined that when the tkined.defaults file is
opened, instead of only allowing interpreter[1-n] in the file, I allow
interpreter0 also, which 'source's the corresponding tcl file into the
existing interpreter. This allows more complicated GUI to be presented
then can be done via ined since I now have access to tk.
This is working well and I am able to bring up Tix widgets from within
module-based code loaded via tkined.defaults.
What I am running into now is that I would like to be able to get the
best of both worlds, specifically use of the ined log windows, but can't
since ined seems to be tcl functionality that only lives in the scotty
interpreter context(s).
I have been staring at objects.c for a while and fathomed that I could
call 'LOG create' from within the tkined context, but soon realized
there is a lot of object post-processing that happens in the call
through ined() and that I wasn't doing that with my simple test of it.
Just try it. I think it can work but I am not sure. Earlier versions
had problems with this but there is a chance that it works right now.
The ugly code in the ined command is needed because the internal
command structure in tkined is a bit different. (I wanted to keep the
external API stable so I hacked this ugly work-around.)
Juergen