Hi,
Thanx a lot CP.. You caught the problem and its working fine..
It was because of the pending events..
Now another problem i am facing is about this warning :
"Warning: XmForm form : attachment to contract_text which is not a child,
replaced with contract_textSW"
I am calling it like this :
wContractText =
XmCreateScrolledText(wForm, "contract_text", args, n);
#endif
XtAddCallback(wContractText, XmNactivateCallback,is_finished , NULL); */
What mistake am i making.. I want to get rid of this warning.
Thanx & Regards,
-sharad
-----Original Message-----
From: C Hennessy
To: Sharad Kumar Gupta (EHPT)
Sent: 5/9/00 12:22 AM
Subject: Re: problem with lesstif
Hi
Why are you doing :
while (!JaldaDone)
{
XtAppNextEvent(ctxApp, &event);
XtDispatchEvent(&event);
}
???
There are still X events left in the queue or on the way to/from the X
server!
It is better to use XtAppMainLoop and a callback for your exit.
But I still do not see your problem ( even when I compiled against Motif
2.0 )!!!
Please submit replies also to the address [EMAIL PROTECTED] as you
will
always get a faster response.
CP
"Sharad Kumar Gupta (EHPT)" wrote:
>
> Hi,
>
> I have writen the demo program
> which is malfunctioning. Please find attached
> the C program, makefile and the executable.
> I have added the printfs to exactly
> pinpoint the problem. Hope this will make
> the picture clear.
>
> One thing i am not able to understand id that while debugging if i
> print any
> Widget, it says "incomplete type".
> Secondly XtDestroyWindow which is not actually destroying the
> window is must be in libXt.a which is not part of
> Lesstif package. Then why its not doing its job, as it works fine with
>
> Motif 2.1
>
> I am thorougly confused. Kindly revert back at the earliest.
>
> Regards,
> -sharad
>
> -----Original Message-----
> From: C Hennessy
> To: Sharad Kumar Gupta (EHPT)
> Cc: '[EMAIL PROTECTED]'
> Sent: 5/4/00 8:32 PM
> Subject: Re: problem with lesstif
>
> Hi,
> Sorry, but it's not very clear from your email that your code already
> works
> with Motif. If it does work with Motif then we probably have a lesstif
>
> bug.
>
> Otherwise we may still have a lesstif bug, but without looking at the
> offending
> code and logic it is not possible to say where the problem is.
> So could you please make a small program which shows your problem and
> then
> email that to us.
>
> CP
>
> "Sharad Kumar Gupta (EHPT)" wrote:
> >
> > Hi,
> >
> > 1. version Number: lesstif-0.90.0-1.i386.rpm
> > 2. distribution : binary
> > 3. system :
> > Linux linux.ind.ehpt.com 2.2.12-20 #1 Mon Sep 27 10:40:35 EDT 1999
> > i686 unknown
> >
> > 4. Problem :
> > I am creating one simple dialog which has 2 text fields and
> > 3 labels with 2 buttons to say OK and Cancel. If i enter
> > some wrong info ( its password), the dialog should remain there
> > in ideal case, but what's happening is it pops up 2nd window while
> > the first is still there. So what's happening is that if the user
> > enters wrong password 5 times there are 5 windows displayed which
> > obviously is not desirable.
> >
> > The dialog i am created has his parent set to NULL and is not a
> > modal dialog.
> >
> > I am calling these 2 functions to destroy the dialog :
> >
> > XtUnmapWidget(JdaWMainTopLevel);
> > XtDestroyWidget(JdaWMainTopLevel);
> >
> > Thanx & Regards
> > -sharad
>
>
>
> Name: test.c
> test.c Type: unspecified type (application/octet-stream)
> Encoding: quoted-printable
>
> stdefs.hName: stdefs.h
> Type: unspecified type (application/octet-stream)
>
> Name: Makefile
> Makefile Type: unspecified type (application/octet-stream)
> Encoding: quoted-printable
>
> Name: a.out
> a.out Type: unspecified type (application/octet-stream)
> Encoding: base64
