Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!bb3.andrew.cmu.edu!newsfeed.pitt.edu!scramble.lm.com!news.math.psu.edu!news.cse.psu.edu!uwm.edu!cs.utexas.edu!howland.reston.ans.net!newsfeed.internetmci.com!news.sprintlink.net!new-news.sprintlink.net!news.emi.net!news
From: joe@teknomad.com (Joe TekNomad)
Subject: Re: VW2.0: Problems with the radio-button widget
Content-Type: Text/Plain; charset=ISO-8859-1
X-Newsreader: WinVN 0.99.5
Sender: news@emi.net (EmiNet Domain News Admin)
Organization: EmiNet Domain Internet Services (407)731-0222
Message-ID: <Dq6FwG.MGM@emi.net>
References: <4l7ls2-giv@svstch.ubs.ch>
Mime-Version: 1.0
X-Nntp-Posting-Host: ttyc6.emi.net
Date: Sat, 20 Apr 1996 20:07:27 GMT
Lines: 43

In article <4l7ls2-giv@svstch.ubs.ch>, szhs79@svusnet.ubs.ch says...
>
>I noticed that in my application the radio-button widget didn't behave
>as expected. I arranged the 3 buttons in a horizontal way, slightly
>overlapping. When I selected the buttons from the left to the right
>they behaved as expected. When I tried to select them from the right
>to the left, finally all 3 buttons were ON!!
>
>I tried to figure out what was causing these problems. I run through the 
>application step by step and everything seemed to work ok, all instance
>variables held the correct values. I finally figured out, that it's (only)
>a redrawing-problem: if I moved another window over the three selected
>radio buttons and then moved it away again, only one button (the correct one)
>remained to be turned on.
>
>When I rearranged the radio buttons in a way, that the text-labels where
>not overlapping the problem disappeared. Maybe I also have to mention, that
>the problem only arised when the widgets were only slightly overlapping.
>When the were almost completely overlapping, there was/is no problem.
>
>Strange isn't it? Has anybody else made similar experiences?
>



Hi Daniel

I haven't actually investigated this but it 'sounds' like it is a problem 
related to widget damage repair. The components of a window will signal to 
there window that they have been damaged and require fixing as soon as 
possible. But this normally happens at the discretion of the window.

In overlapping cases, the widgets may be getting confused about who is actually 
visible. When you cover and uncover the entire area, they all shout about 
damage.

Sending the message #repairDamage to a widget will force it to be redrawn 
immediately. So you have some choices....either ensure no overlap or when a 
button is pressed run a method that targets just the troublesome buttons with 
#repairDamage.

Joe TekNomad

