There are lots of solutions here, but none of them are built into TK, nor can they be. If you want your program to interface with an environment other than the one TK is running ni, it's up to you to make the links.
I believe you are asserting here that, PerlTK can not (or should not) concern itself with individual platform issues to which it is ported. I respectfully do not agree. Additionally I notice the developers of PerlTK do not agree. For example, they appear to have made many accommodations for Microsoft Windows. I draw your attention to the Tk-804.027 source files in the directory "Tk-804.027/pTk/mTK/win". Take a look at the tkWinPort.h header file in that directory.
The PerlTK developers make calls to Windows DLL's, they might want to make a call to OSX libs to make all PerlTK's features work more seamlessly with the native GUI. The developers seem to have lumped OSX into the same category as Unix/X. This is perhaps not the correct thing to do. While OSX runs X, it's primary GUI is not X.
Making sure all function calls work well in each target environment make PerlTK a more attractive development tool. Standing back and taking the "not my responsibility" attitude doesn't help the cause. Solving the problem by adding code to each PerlTK program written is not efficient.
Regards,
