Re: rendering-cleanup-next

[Matthias Clasen <matthias clasen gmail com>]

On Sat, Sep 11, 2010 at 4:23 PM, Havoc Pennington <hp pobox com> wrote:

>
> Does GDK have enough information to know when to set background to None?
> The patch
> d3802ca Remove calls that try to set GDK_NO_BG
>
> basically removes hints to GDK that the background should not be
> repainted by the OS. I don't know how GDK would know this.
>
> I don't know exactly what the API should be. Maybe set_hint_no_clear()
> or set_autopaint() or whatever it is. The main thing is, I think pre-
> this patch, things probably did not flicker as much, and post- this
> patch, they are probably flickery and uglier. So that's a user-visible
> regression. It just doesn't seem like a good idea to me to regress
> that.
>
> The API for this may be something that's a no-op on Windows and/or
> Mac, I don't know.

Could also  make it a gdk_x11 api.
But maybe a hint that is a no-op on other backends is better.

> I would say, expose-event should be defined to be exactly what comes
> from GdkWindow, no pre-processing or special handling _at all_, and it
> only happens on window widgets. In the GTK of the future, this
> expose-event thing would be like the other obscure list of events that
> only window widgets ever get (destroy-notify, visibility-notify, blah
> blah). These events should all be lifted up out of GtkWidget somehow
> and only be present on windowed widgets; maybe via an interface, I
> don't know.

This makes sense to me, as a general direction.

Also, the idea to separate the translation and the size in
size_allocate is intriguing.