Re: Include GdkRegion in expose events - bug 51288 [PATCH]

[Owen Taylor <otaylor redhat com>]

Tim Janik <timj gtk org> writes:

> On 28 Feb 2001, Owen Taylor wrote:
> 
> > Alexander Larsson <alla lysator liu se> writes:
> > 
> > > Here is a patch that implements a GdkExposeEvent.region field, in addition
> > > to the old area field. This lets app authors make more intelligent expose
> > > handlers in case they draw something that takes a lot of time.
> > > 
> > > I think this is a great idea.
> 
> > I think if we are going to break synthetic exposes, then we
> > should break them in a clear, reliable way and tell people
> > need to 
> > 
> > So, I'd propose make calling gtk_widget_event() with an 
> > event of type GDK_EXPOSE illegal and if that is done
> 
> at best, you can make it "invalid" but never "illegal".

"Illegal" - not allowed. I don't mean the police are going
to come knocking on your door.
 
> > print out a informative message like:
> > 
> >  "Events of type GDK_EXPOSE cannot be synthesized. To get
> >   the same effect, call gdk_window_invalidate_rect/region(),
> >   followed by gdk_window_process_updates()."
> 
> gtk_widget_event() is what gtkmain uses as well, unless you have
> some cruel hack to it in mind that you didn't mention here, i don't
> see how will avoid future gtk versions always spewing that warning
> upon expose events.

I don't see having a separate, non-public function to send expose
events to widgets counts as being a "cruel hack".

                                        Owen