The other way is to use after(). after() will only be triggered once, thus the event handler will only be called once. Inside the event handler, based on the situation, you can decide whether to reschedule itself again. If yes, simply call after() to reschedule itself. For example:

use Tk; use Tk::MListbox; my $mw = MainWindow->new(); my $count_v = 0; my $stop_v = 0; my $stop = $mw->Checkbutton(-text => "stop", -variable => \$stop_v, -c +ommand => \&schedule)->pack(); my $count = $mw->Label(-text => $count_v)->pack(); $count->after(1000, \&inc); MainLoop; sub inc { $count->configure(-text => $count->cget("-text") + 1); if (!$stop_v) { $count->after(1000, \&inc); } } sub schedule { if (!$stop_v) { $count->after(1000, \&inc); } }

In reply to Re: Interrupting Tk repeat() method by pg
in thread Interrupting Tk repeat() method by aplonis

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.