I bet the continuously available fileevents are taking higher priority than the idleevents which is where the actual repaint is done. As Tk::Widget says: 
       $widget->idletasks
           One of two methods which are used to bring the application 
+``up to
           date'' by entering the event loop repeated until all pendin
+g events
           (including idle callbacks) have been processed.

           If the idletasks method is specified, then no new events or
+ errors
           are processed; only idle callbacks are invoked. This causes
+ opera-
           tions that are normally deferred, such as display updates a
+nd win-
           dow layout calculations, to be performed immediately.

           The idletasks command is useful in scripts where changes ha
+ve been
           made to the application's state and you want those changes 
+to
           appear on the display immediately, rather than waiting for 
+the
           script to complete. Most display updates are performed as i
+dle
           callbacks, so idletasks will cause them to run. However, th
+ere are
           some kinds of updates that only happen in response to event
+s, such
           as those triggered by window size changes; these updates wi
+ll not
           occur in idletasks.

[download]

-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.

In reply to •Re: Re: Re: Perl::TK - fileevent and script execution theory by merlyn
in thread Perl::TK - fileevent and script execution theory by crabbdean

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.