It's not Perl...it's Tk mucking up, that's why I concentrate on Gtk2 now. :-) I was toying with it, using all the tricks I know, but no go. There is the -dynamicgeometry option for the NoteBook, and it seems to address the problem, but it has no effect. Usually with the Notebook, when it acts up from tab to tab, you need to set a -raisecmd option to adjust the geometry (like a $mw->update) when a tab is raised...but it dosn't work in this case.

I notice that you have alot of nested packing with anchors, and all the other packing options, that seem to be messing with the Scrolled Pane's scrollbars. To be honest, I would go back to the example I mentioned earlier, that dosn't crush the tabs, and try to work your data set into that model. Or switch to Gtk2. :-)

I'm not really a human, but I play one on earth Remember How Lucky You Are

In reply to Re^3: Tk gui bug by zentara
in thread Tk gui bug by honyok

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.