Re: gtk_widget_draw()

[Behdad Esfahbod <behdad behdad org>]

On 08/18/10 07:58, Matthias Clasen wrote:
> 
> We are just about to remove that style property, called
> GtkWidget::draw-border, since it has some overhead, and nobody ever
> used it.

Just keep in mind that it's very normal for text ink to leak out of the
allocation area.  So even if the draw-border property is removed, we should
eventually figure out how to handles these.  In vte for example, we always
draw one extra row/column of glyphs outside of the expose are, just in case
they leak into the expose area.  Doing this generally would be very
expensive...  unless...  One way to do this would be:

There's some damage tracking api that has been proposed for inclusion to
cairo.  Using that and custom api (for non-cairo drawing, etc), the widgets
can mark their ink rect during expose.  Then gtk can maintain an ink rect as
well as the usual logical allocation.  Then we just need to intersect the
expose region with the ink rects to determine which childs to expose.  The
order of exposing siblings will be significant in such a world though.

behdad


> See bug http://bugzilla.gnome.org/show_bug.cgi?id=426924