Creating your own MainWindow is an odd workaround. $poe_main_window should be defined there, so your MainWindow->new() call should never happen.

If you do succeed in creating your own MainWindow, you may notice that clicking on the close button doesn't stop your program. You can re-enable this with POE::Kernel's signal_ui_destroy() method.

There's no good reason for JSON::XS to interfere with Tk, but perhaps there's something conflicting at the XS level. Have you tried a non-complied JSON library instead?

If it is a C-level issue, then also be sure that you're deploying the software on a compatible version of Windows and C's runtime libraries. I'm not sure whether perlapp bundles things that far down.


In reply to Re: POE, pTk, JSON Cause Lockup with perlapp by rcaputo
in thread POE, pTk, JSON Cause Lockup with perlapp by cmv

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.