Re: Heads-up: Potentially breaking changes to the GDK drawing model pushed

Yes, that should work. Make sure to test it, though, as begin_paint_rect / begin_paint_region currently clears the specified rect/region to the background set on the GdkWindow. If passing a more exact region is too much of an annoyance, I should be able to also change this without breaking too much so that the clear to background only happens on expose events.

It's difficult to balance the requirements of everybody.

On Sat, Jun 21, 2014 at 9:44 AM, Jean Brefort <jean brefort normalesup org> wrote:
Both abiword and gnumeric do something like:

cr = gdk_cairo_create(win); some drawing
then relase the cairo.

Will this still work if we use

gdk_window_begin_paint_rect (win, rect);
cr = gdk_cairo_create (win); some drawing
gdk_window_end_paint (win);


Le samedi 21 juin 2014 à 09:33 -0400, Jasper St. Pierre a écrit :
> Can you two explain exactly what Abiword and Gnumeric are doing, what
> APIs they're using and why and so on? We're trying to come up with a
> solution that will work well under both X11 and Wayland.
> As I said, if it's a really bad break and would require intensive
> changes to apps, I'll revert the patches. This is exactly why I sent
> out the mail.
> On Sat, Jun 21, 2014 at 9:18 AM, Jean Brefort
> <jean brefort normalesup org> wrote:
>         This will break abiword as well.
>         Jean
>         Le samedi 21 juin 2014 à 08:02 -0400, Morten Welinder a
>         écrit :
>         > Argh!
>         >
>         > Will the stream of ABI changes never end?
>         >
>         > Gnumeric uses this to provide a walking-ant cursor large
>         selected areas -- areas
>         > too big for processing in the normal paint loop.
>         >
>         > Morten
> --
>   Jasper


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]