> From: Jeff Hobbs [mailto:[EMAIL PROTECTED] > Konovalov, Vadim (Vadim)** CTR ** wrote: > >> From: Sylvain Thibault [mailto:[EMAIL PROTECTED] > >> I had to move tkkit.dll to a writable directory and then > it worked. It > >> generates a tkkit.dll slightly bigger than the original one. > > > > tkkit.dll is updated and gets bigger? How so? > > This is a side-effect of the virtual file system in > particular that is > used with the stardll (STand-Alone Runtime DLL). It is a metakit > database. If you do random inserts, it can go up in size. > There is a > vacuum operation that can be done, but it isn't necessary.
That's cool! :) Thanks for letting know. > >> You can find out where your Activetcl is mapped by: > >> "puts [join $::auto_path \n]" in the tcl shell > >> > >> In my case this is accomplished by adding these 2 lines to > my script: > >> > >> Tkx::lappend('::auto_path', > >> 'C:/Tcl/lib/teapot/package/win32-ix86/lib'); > >> Tkx::lappend('::auto_path', 'C:/Tcl/lib/teapot/package/tcl/lib'); > > > > these 2 lines should not belong to your script: next time > tkkit.dll will > > be packaged differently, and you'll be lost and frustrated, > yet direct paths > > also a problem > > These 2 lines are independent of the tkkit, rather they are > tied to the > Tcl install. The problem is that Sylvain inserts these lines into the script, which is wrong direction of resolving th eproblem, IMO. BR, Vadim.