Can anyone confirm please?
TIA, Niv.
package require Tk
early in the script.
ActiveTcl never made associations for .tk, so those must have been made
by yourself or another program. It makes associations for .tcl (and
optionally .tbc) to wish, as that is the most common expectation. You
can change this in the registry.
Jeff
I think it should, by default, add for .tsh to run tclsh, too. But maybe
that's because I write way more tcl scripts than wish scripts. :-)
--
Darren New / San Diego, CA, USA (PST)
I bet exercise equipment would be a lot more
expensive if we had evolved from starfish.
If people would like a tclsh-specific extension, please let us know. It
would have been nice if .tcl and .tk had stuck as separate extensions
earlier, but I otherwise don't want to co-opt .tcl for tclsh. While
using 'package require Tk' would work for most people, it has a slightly
different effect on Windows and OS X where they are tied to a console.
Jeff
I still seem to be having some minor problems, now that I'm re-
visiting some old scripts.
I have sme tcl scripts for manipulating data files, these work fine
now that the windows .tcl association is made to tclsh.
However, I also have some scripts that I want to open directly with
wish, but as they have .tcl extensions, they open a tclshell which
then opens teh wish window; killing the tclshell obviously kills the
wish as well.
I did have the wish files with a tk extension and a windows
association to wish. Should I return to that scenario to prevent the
tclshell opening before the wish window?