Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!oberon!polyslo!bwarkent
From: bwarkent@polyslo.CalPoly.EDU (Brian Warkentine)
Newsgroups: comp.windows.x
Subject: Re: Command button remaining highlighted (was: Re: Menu Widgets)
Keywords: highlighting, events
Message-ID: <8883@polyslo.CalPoly.EDU>
Date: 4 Mar 89 18:41:01 GMT
References: <6146@medusa.cs.purdue.edu> <1309@husc6.harvard.edu>
Reply-To: bwarkent@polyslo.CalPoly.EDU (Brian Warkentine)
Organization: Cal Poly State University -- San Luis Obispo
Lines: 23

In article <1309@husc6.harvard.edu> kochhar@endor.UUCP (Sandeep Kochhar) writes:
>
> [...]  I have
>had the problem mentioned above (i.e. the item remains highlighted,
>until you move the cursor in and out again); 
> [...]  I am not sure, but it seems to be related to
>the time it takes for the callback routine to return.
>
>Anyone have any observations/suggestions?
>
>sandeep kochhar            email: kochhar@harvard.harvard.edu

I have noticed this behavior in several programs, including my own (eeekkk!).
In my case, it had nothing to do with the callback routine, it has to 
do with a popup widget grabbing all input.  As a result, the command 
widget never gets the leave window event that tells it to restore the
border to it's non-highlighted state.  If your situation is similar, the
solution is to code around it.

----
Brian "Give me a job" Warkentine                 Cal Poly, San Luis Obispo, CA
   bwarkent@Polyslo.CalPoly.EDU
   ...!ucbvax!voder!polyslo!bwarkent