A couple of people have reported that the Windows NT build of
scotty that I did the tkined didn't work properly. First, you
had to rename it to tkined.tcl to get the windows association to
work (probably should change the install to do this). It would
then run, but there was no Tools menu.
In tracking this down, the problem appears to be in TnmInitPath
in tnmWinInit.c. It's trying to find where the tclsh83.exe and
wish83.exe are installed at, so it can use them to execute the
various sub-scripts used by tkined.
The code in there looks in the registry for the root of the Scriptics
or Sun TCL installs, and uses that to find the binaries. If I hack
up the registry to put the right values in, I get a Tools menu
(which I haven't tested at all, but that's a seperate issue).
However, for other Tcl installs (such as the ActiveState one I
built against), this fails. I could add yet more custom code for
ActiveState (and TclPro and other Tcl packages), but that seems
like the wrong way to go.
I'm not much of a Windows programmer, but is there a better way to
do this? Is there a way to do a "which tclsh83.exe" in windows?
Programatically? After all, the tclsh83.exe (or wish83.exe) is
the thing *running* right now, correct? Is there a way to find
the full path of the currently executing binary? Would that be
the right way to go?
Pete
-- !! This message is brought to you via the `tkined & scotty' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>. !! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.
This archive was generated by hypermail 2b29 : Thu Jan 03 2002 - 14:56:28 MET