I am playing with a small app that pulls info from a database into a Win32::GUI::Grid . A GUI event triggers the SQL query, which may take several seconds to complete on large table/slow link.

Unfortunately, if I make another GUI event in the mean time, triggering another SQL query, the two get confused; The share a single DBI handle, create their own statement handles which execute in paralell. So far so good. Unfortunately, they both populate the same Win32::GUI::Grid and thus stomp all over each other.

I have tried using a global variable to "signal" the first event handler to abort when a second is called, but the first handler does not see the variable change. Perhaps they run as separate threads, I don't really know...

I imagine this is a fairly common pitfall when it comes to GUI programming, so what's the proper way to solve this?

In reply to Win32::GUI, tell an event handler to stop by FloydATC

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.