Hello,
when starting a Xt-Application you should use XtOpenApplication() or
XtAppInitialize()
they will call XOpenDisplay().
I read the paper but i am not sure is the programm without display of any use ?
or is
it a sample that simply shows the limitation of the model ?
I am not deeply in Xt an
when do application do not have a display ?
Xt is also a powerful general purpose environment for event-driven
programming. Input events, timers, now signals ... all handled pretty
well. Originally the big drawback was that XtAppMainLoop would *never*
return, but this ExitFlag stuff appears
this sounds reasonable,
but when do application do not have a display ?
re,
wh
Am 24.02.2011 00:09, schrieb Jordan Hayes:
> The manual page for XtAppMainLoop says that it's just a simple loop that
> calls
>
> XEvent event;
> XtAppNextEvent(app, &event);
> XtDispatchEvent(&event);
>
> ... unti
The manual page for XtAppMainLoop says that it's just a simple loop that
calls
XEvent event;
XtAppNextEvent(app, &event);
XtDispatchEvent(&event);
... until XtAppGetExitFlag() returns true.
And looking at the code in libXt-1.0.9/src/Event.c seems to show that to
be the case.
But: XtAppNextE
