Thomas Mittelstaedt <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] writes:
>
> > The X target should also send expose events, as is suggested by
> >
> > bash-2.03$ grep evExpose */*.c
> > xwin/input.c: giiev.any.type = evExpose;
> >
>
> Yep found that code. Its in GII_xwin_evenpoll.
>
> > See my other post on this. Please tell us, if expose doesn't work on X,
> > as it actually is the target for which exposes are interesting ...
>
> No, I never receive such an event. Is GII_xwin_evenpoll called at all?
The X-target is special. What you draw on is a block of RAM, an
XImage in X terminology, which is blitted to the GGI-on-X window
by the X server when you call ggiFlush(). The XImage belongs to
the X client, and is never overwritten by the server.
The X-target knows this, so when it receives an X expose event from
the X server it doesn't send a GGI expose event to the application.
Instead it simply blits the exposed part of the X-image to the
window, without telling the application that there ever was an expose
event.
This means that as long as you call ggiEventPoll() (which is necessary
for LibGGI to receive events from the X server) the window will be
automaticly updated, but the application won't receive expose events
from LibGGI.
//Marcus
--
-------------------------------+------------------------------------
Marcus Sundberg | http://www.stacken.kth.se/~mackan
Royal Institute of Technology | Phone: +46 707 295404
Stockholm, Sweden | E-Mail: [EMAIL PROTECTED]
