[comp.windows.interviews] Controlling the Event Loop...

linton@marktwain.rad.sgi.com (Mark Linton) (06/18/91)

In article <4881@meaddata.meaddata.com>, curt@meaddata.com (Curt Kohler) writes:
|> Is there a method or way way to either tell the application to eat all
|> these extraneous events or to flush out the input buffer like the
|> WorldView::ClearInput() method which could be called immediately following
|> a return from one of these long duration database calls?

It should work to call World::read with zero timeout until it returns false, e.g.,

    while (world->read(0, 0, event));

This will ensure that any expose or resize events that occurred while accessing the database
will be processed, while queued user events will be ignored.