RE: pTk Scrolled Text problem

"Konovalov, Vadim" <[email protected]>
Newsgroups gmane.comp.lang.perl.tk
Message-ID <[email protected]>
> >this problem is in perl/Tk and does not appear to be in Tcl/Tk.
> >Because if I replace many "use Tk; use Tk::something" with single
> >
> >  use Tcl::Tk qw(:perlTk);
> >
> >, the problem does not appear.

...

> The problen certainly used to occur with Tcl/Tk.

I only meant that same code within Tcl/Tk, as opposed to perl/Tk, behaves
differently.
I.e. if I instead write same program in Tcl/Tk language (this is what
Tcl::Tk perl module essentially do internally), then behaviour is different.

However, according to Slaven, same problem appears to be in Tcl::Tk also (I
can't reproduce, but I beleive this could be)


> What happens is: a line at the bottom of in the window is too 
> wide to be 
> rendered so a horizontal scrollbar is mapped. But now line 
> isn't in the window
> (covered by scrollbar) so scrollbar is unmapped.

Within this logic, a flaw may be caused by window redraw strategy.
So may be I need to try window manager same with Slaven to reproduce.


> 
> A proper "fix" is for Text widget to know the "width" of text 
> as a whole
> not just that which fits in the window. But that is a lot of 
> computation 
> for a large document. Caching longest line seen might suffice. 
> 
> What I personally would like to see is scrollbar's 
> mapped-ness be determined 
> by whether ANY line of whole text is wider than window, but 
> slider expand to 
> full size if current window contents fit.

me too.
BTW scrolled bar behaviour changed in Tcl/Tk recently,  see for example
http://www.tcl.tk/cgi-bin/tct/tip/155.html
Vadim.
-++**==--++**==--++**==--++**==--++**==--++**==--++**==
This message was posted through the Stanford campus mailing list
server.  If you wish to unsubscribe from this mailing list, send the
message body of "unsubscribe ptk" to [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.