Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
Well I'm running on linux, and your script appears to run fine. I enter google.com (to get alot of text) and the scrollbars appear.

When the widget is first filled with text, though, even if the "East" (right-side) scrollbar appears, the slider bar does not appear. After resizing the whole GUI, however, the ROText window is resized, causing the scrollbar slider to appear as it should have done. Another way to make the slider "pop into view" is to click the left mouse inside the ROText window, and move the mouse outside of the window (still holding the button down).

I can't say for sure if it's your problem, but in many other Text widget scripts ( as you know ), it's often neccessary to do a $text->update to bring text into view.

But this seems to be in the scrolled container that holds the text widget. So maybe you could try

# do a 1 event loop iteration # process any Tk events like mouse moves/button presses/etc 1 while $MW->DoOneEvent( ALL_EVENTS | DONT_WAIT ); # or even a simple $mw->update; #or get the scrollbar and update it $scrollbar->update

I'm not really a human, but I play one on earth. Cogito ergo sum a bum

In reply to Re: Bug in Win32 Perl/Tk Scrolled ROText widget with optional scrollbars by zentara
in thread Bug in Win32 Perl/Tk Scrolled ROText widget with optional scrollbars by liverpole

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others surveying the Monastery: (3)
As of 2024-04-25 22:12 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found