Okay, I see it now.
This is probably a good time to repeat that when reporting a behaviour problem
the smallest of details matter. This particular problem only shows with the
following sequence....
<Btn1Down> in cb
<Btn1Up> in cb
<Btn1Down> in gpb2
<Btn1Up> in gpb2
<Btn1Down> in one of the dialog buttons
<Btn1Up>
It does not occur with the following....
<Btn1Down> in cb
<Btn1Up> in gpb2
<Btn1Down> in one of the dialog buttons
<Btn1Up>
Now the 2 should produce the same result, but the path taken to that outcome
are not the least bit similar. In short, details matter.
Thanks for the follow up info.
On 07-May-00 at 18:57, Kazuyuki Funada ([EMAIL PROTECTED]) wrote:
> Hi,
>
> Thanks for trying to reproduce..
>
> > I see no warnings when running your sample code.
> >
> >
> > On 02-May-00 at 05:18, Kazuyuki Funada ([EMAIL PROTECTED]) wrote:
> > > Hi,
> > >
> > > I found a problem related to "Gadget" and attached source code
> > > is a simple example to reproduce it.
>
> To reproduce the problem, the following steps are necessary.
> (Sorry, poor description in my previous e-mail..)
>
> 1. run binary
> 2. press "cb"
> 3. select "gpb2" (not "gpb1" that works fine.)
> 4. then press any button on the dialog-BOX
>
> If you did not do so, could you try again?
>
> I tested my sample code on lesstif-0.90.0 that I build from
> original source RPM. And I could see the problem on both of
> libXm.so.1 and libXm.so.2.
>
> If nobody can not reproduce, perhaps, there are any problem
> in my Linux-box, I guess.
>
> Thanks.
> --
> Kazuyuki Funada
>
>
