From: Martin Weber <Ephaeton@...>
Date: 2001-11-10T21:34:45+09:00
Subject: [ruby-talk:24827] Re: Ruby-Tk; feature/bug/misunderstanding? mouse-location during  when a key is pressed in the presence of TkMenubutton

On Sat, Nov 10, 2001 at 09:26:13PM +0900, Kero van Gelder wrote:
> Ah, that's where I should look! Thanks.
> 
> >From OO perspective, that's not obvious, but heck, it can be worse, I
> guess :)
> 
> NB: Ruby/Tk seems to have all Tk features, so let's assume it is
> implemented.
> 
> PS: This might solve my double scrollbar problem for a canvas...

Take care, in tcl you need to call update to tell the tk system
to actually updat the widget information after you requested
a specific width/height. If you ask for a width and immediately
afterwards you call winfo (req)(height|width) for that widget
it is not guaranteed that neither requested h/w nor the 'real'
h/w in the widget information is updated. An update idletasks
equivalent call in ruby should take care of this.

(I've ran into some pits already because I forgot a call to
update, and suddenly I had windows with 0-w/h widgets ;))

Martin Weber