Helmut,
I have the same problem. My solution is not great, but in general, it works.
Like you, I place the proc's in other packages, require them, then I make sure
they are not called by placing the following code around calls to the proc's:
if {![info exists ::vTcl]} {
call to proc
}
This will call the proc if you are running your code from wish or another
program.
It will not call the proc when you're in vTcl, so you can't use vTcl to edit
the widgets from the package. But it prevents the proc's from ending up in
your saved code.
I understand why vTcl includes the called proc's in it's saved code, but I wish
(no pun intended) that there was a better solution. Maybe vTcl could
distinguish between proc's defined in the main tcl file and those loaded from a
package.
Cheers,
Randy Reichenbach
"Helmut Schr�der" wrote:
> Hallo,
>
> there is a strange behavior with vtcl, maybe someone has a solution or
> work around:
> I made a GUI with vtcl and declared some procedures in external library
> files e.g. lib.tcl to do some other work. The library file is imported
> with the auto_path command. This is no problem.
> But when I load the GUI in vtcl , change something in the GUI and save
> the work, then all the externel procedures are stored in the vtcl file.
> Does any body know how to avoid this?
>
> Helmut
>
> ---------------------------------------------------------------------------
> To unsubscribe from the Visual Tcl mailing list, please send a message
> to [EMAIL PROTECTED] with "unsubscribe vtcl [EMAIL PROTECTED]" in the
> message body (where [EMAIL PROTECTED] is your e-mail address).
---------------------------------------------------------------------------
To unsubscribe from the Visual Tcl mailing list, please send a message
to [EMAIL PROTECTED] with "unsubscribe vtcl [EMAIL PROTECTED]" in the
message body (where [EMAIL PROTECTED] is your e-mail address).
