Here comes a dose of wisdom for you Limbic~Region, :-)

If you destroy the entry, and try to redisplay it with the checkbutton click, you will gain memory. Tk will not clean up it's refcounts totally. So packForget the entry instead, then repack it it when the checkbutton is checked.

BUT, it usually is better for screen appearance to leave the entry widget in place, and just change it's state. 

#!/usr/bin/perl
use warnings;
use strict;

use Tk;

my ( $entry, $cbvalue );

my $mw = tkinit;

$mw->Checkbutton(
    -text     => 'Use Entry widget below?',
    -variable => \$cbvalue,
    -command  => \&SetState,
)->pack;

$entry = $mw->Entry->pack;
SetState();
MainLoop;

sub SetState {
    $entry->configure( -state => $cbvalue ? 'normal' : 'disabled' );
}

[download]
I'm not really a human, but I play one on earth CandyGram for Mongo

In reply to Re: Perl-tk Entry by zentara
in thread Perl-tk Entry by erez_ez

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.