how can i include tk commands into my tcl 8.0 script, if i want to use them, but the shell doesn't know them?
source tk.tcl? it doesnt work..b'cos i should use absolute pathname..
i make a script, what a CAD/CAM software will use to generate documentation,(as i said in the 'beginners guiding' topic) and it supports only 8.0, but as i see, not all tcl/tk commands are supported..
so i need a solution, to include the commands like toplevel, pack, wish, or any others, what i may need
I'm not sure about "toplevel", but "pack" and "wish" are OT (original Tcl) commands. It seems to me your problem is you're running the Tcl shell (tclsh) rather than the Tk shell (Tk). What is your platform? How are you invoking the script?
<i>I'm not sure about "toplevel", but "pack" and "wish" are OT (original Tcl) commands. It seems to me your problem is you're running the Tcl shell (tclsh) rather than the Tk shell (Tk).</i>
how can i switch to tk shell?
<i>What is your platform?</i>
im under win2k
<i>How are you invoking the script?</i>
i dont understand your question... :lama:
there is a command in the software: 'make doc', what launches the script, but i dont know any other... but i use
info tclversion , what tell me, that he is 8.1..
the documentation of the software is very poor in the usage of TCL
The Tcl shell is "tclsh.exe". The Tk shell is "wish.exe". Check in your Windows Explorer folder options and see if the .tcl file extension is associated with tclsh instead of wish. It should be "wish" if you are using Tk stuff. That is, wish includes Tcl as well as Tk. Tclsh only includes Tcl.
i found a dll, what the software loads, when starts, with the name:ugtcl.dll
and i found in this file:
O r i g i n a l F i l e n a m e t c l 8 1 . d l l L C o m p a n y N a m e S c r i p t i c s C o r p o r a t i o n , F i l e V e r s i o n 8 . 1 . 0 | , L e g a l C o p y r i g h t C o p y r i g h t ( c ) 1 9 9 9 b y S c r i p t i c s C o r p o r a t i o n H P r o d u c t N a m e T c l 8 . 1 f o r W i n d o w s 0 P r o d u c t V e r s i o n 8 . 1
i hope its not illegal to copy this text.. ;-)
It looks like the dll is being loaded, not the shell, per se. I don't know what that dll has but from your experience, it would appear that it is Tcl only, not Tk.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.