Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!oitnews.harvard.edu!purdue!haven.umd.edu!news.umbc.edu!eff!news.duke.edu!news.mathworks.com!newsfeed.internetmci.com!tank.news.pipex.net!pipex!dispatch.news.demon.net!demon!sunsite.doc.ic.ac.uk!susx.ac.uk!news.bton.ac.uk!Simon.Shurville
From: sjs16@itri.bton.ac.uk (Simon John Shurville)
Subject: More about radio buttons and labels in VW
X-Nntp-Posting-Host: tomcat.itri.bton.ac.uk
Message-ID: <DGL7ru.6Iy@bton.ac.uk>
X-Posted-From: InterNews 1.0@diamond.bton.ac.uk.
Lines: 46
Sender: -Not-Authenticated-[3206]
Organization: The Composer Project
Date: Tue, 17 Oct 1995 09:59:54 GMT
Xdisclaimer: No attempt was made to authenticate the sender's name.

I recieved the following very informative response from Jeff Rensch,
once again I have to thank this group for being so forthcoming with
help for us beginers. I would add that in my case the problem seemed to
be that the notional boxes around a pair of passive labels overlapped
the notional boxes around the radio buttons. A subtle variation on the
problem which might be worth looking out for!

Date:     Mon, 16 Oct 95 16:43:12 PDT
From: "Jeff Rensch"     <JRensch@EDU.Stanford.Forsythe>
To: sjs16@uk.ac.bton.itri
Subject:  Re: Solution to problem with radio buttons and labels in VW

Simon - Sigh.... your response reminded me that this had
indeed crossed the net previously.  Sorry I didn't think
of it earlier.  Here is what the ParcPlace guy said
last May.  Congrats that you solved it.

 Jeff Rensch, Stanford ITSS


Item: comp.lang.smalltalk 24073,  24 May 1995,  31 lines.    (164 items
left)
From: gojomo@soda.CSUA.Berkeley.EDU (Gordon Mohr)
Subject: Re: Radio Buttons Problem (VW2.0)

In article <n1410804017.71248@smtpgwprod.ny.jpmorgan.com>,
Dombiak, G. <dombiak_g@jpmorgan.com> wrote:

>I've got the following problem with some of my RadioButtons.  Sometimes,
>under circumstances which I still don't know, a pair of radio button don't
>behave as they should.  When I click on one of them he refuses to turn on and
>his companion refuses to turn off.  If I inspect my model,  the objects
>aspect they are working on, accepted the change *always*, even though
>visually the buttons don't show any change.  Moreover, they eventually will
>get so messed up that they  are both on or both off or whatever. The most
>curious thing is that if I hide the window with another and then unhide it,
>they will redisplay themselfs correctly.

Make sure the buttons don't overlap at all. Radio buttons mistakenly
believe they've completely redisplayed themself even if they've really
only redisplayed just a tiny corner of themself.

Thus, if common-model radio buttons overlap, when the first refreshes
itself it may damage the other slightly. Fixing that damage -- which
may
not be visible at all, if at the edges -- causes the second radio
button
to think it has already displayed its new state. Thus, when it is later
told, "you've changed state, redisplay", it thinks it's already done
that,
and does not change the on/off indicator.
