Re^5: How a baisc debugging effort restored my sanity!

given that you have your own modules in perl/Tk, I am not surprised that you do not have interest in digging deeper

and that is perfectly o-kay,
you have your code that relies on something, and moving is not easy.

For me, moving to Tcl::Tk was just a necessary step, because at that time perl/Tk haven't supported Unicode.
Today, perl/Tk do have Unicode,
but it will be several steps behind - by design.

I do not know anything about pTk, I know Tcl::Tk and Tcl CPAN modules.

Of course your problem could easily be resolved, but given that you do not want it - let it be as it is :)

Comment on Re^5: How a baisc debugging effort restored my sanity!

Replies are listed 'Best First'.
Re^6: How a baisc debugging effort restored my sanity! by Tux (Canon) on Mar 03, 2011 at 09:02 UTC
But it sounds like you are interested enough. If I can help (you) to improve on these modules, maybe by testing or adding RT tickets to the module queues, I'm all ears. Enjoy, Have FUN! H.Merijn	[reply]
Re^7: How a baisc debugging effort restored my sanity! by vkon (Curate) on Mar 03, 2011 at 13:11 UTC
my interest is - with larger user base it would be better for me. I have code based on Tcl::Tk that I could share, and vice-versa - I could use someone else's code. you're right, I must start with providing easier setup, RT tickets, better CPAN reports, etc. I'll see what can I do in this area.	[reply]