It's wrong to assume that Tk has evolved to Tkx. ActiveStatePerl's supported version of Tk, has evolved to Tkx, but plain old Tk will still run on ActiveStatePerl. The problem it seems, is that like the shifting wind blown sand dunes in the desert, the various binary builds for various Tk releases seem to move around, hide, and are not clearly identified. Maybe ActiveState wants it that way?
in reply to ptkdb module using Tkx?
I know the binary Tk build for your Windows architecture is out there, maybe someone can point you to it, unless you want to move to Tkx.
Doesn't Tkx have it's own debugger GUI?
Another far out option, is to run the Tkx and Tk eventloop simultaneously, by running one as master loop, and the other as a slave loop, which you pump frequently with a timer. It works surprisingly well, see Wx with Tk for example.