Re: question about ActiveState's Tkx
- From: Jeff Hobbs <jeff.hobbs@xxxxxxxxx>
- Date: Mon, 3 Mar 2008 20:00:39 -0800 (PST)
On Mar 2, 2:20 pm, "~greg" <g...@xxxxxxxxxxxxxxxxxx> wrote:
In the Tcl.pm help, in the section
"Moving Tcl/Tk around with Tcl.pm",
it says:
In order to create Tcl/Tk application with this module, you need to make sure
that Tcl/Tk is available within visibility of this module. There are many ways
to achieve this, varying on ease of starting things up and providing flexible
moveable archived files.
Following list enumerates them, in order of increased possibility to change location.
First method
Install Tcl/Tk first, then install Perl module Tcl, so installed Tcl/Tk will be used.
This is most normal approach, and no care of Tcl/Tk distribution is taken
on Perl side (this is done on Tcl/Tk side)
....
This is the generic Tcl.pm docs, whereas is appears you are using
ActivePerl, which includes Tkx. We make some minor patches in order
to ensure there is a working and _reliable_ Tcl/Tk available. This is
because ActivePerl's ppm UI is written in Tkx.
which seems to mean that tkkit.dll is being used, not Tcl/Tk.
Yes, the tkkit.dll is a single-file dll that encompasses Tcl/Tk +
extensions. This is patched in as the "default" Tcl/Tk to be found.
So how can I get Tkx.pm (and Tcl.pm) to use Tcl/Tk instead of tkkit.dll?
This can be controlled with the PERL_TCL_DLL environment variable
(point to another tclXY.dll should generally work), or $Tcl::DL_PATH
in Perl.
Jeff
.
- Follow-Ups:
- Re: question about ActiveState's Tkx
- From: ~greg
- Re: question about ActiveState's Tkx
- From: ~greg
- Re: question about ActiveState's Tkx
- References:
- question about ActiveState's Tkx
- From: ~greg
- question about ActiveState's Tkx
- Prev by Date: Re: Knowing size of window/widget before it's displayed?
- Next by Date: Re: double buffering with perl/tk
- Previous by thread: question about ActiveState's Tkx
- Next by thread: Re: question about ActiveState's Tkx
- Index(es):
Relevant Pages
|