Hi I have not been able to find out the fix that u mentioned in quartz backend; in gtk+-2.10.14; could u elaborate on that please?
It will be very helpful; Thanks & Regards sv. On Mon, Jun 9, 2008 at 6:07 PM, svalbard colaco <[EMAIL PROTECTED]> wrote: > Hi Paul Davis , > > Thanks for your prompt reply ; > > Can u tell me where exactly the changes have to be done? > > As u mentioned there is a fix in quartz ; can u elaborate on that ? where > in the source code i can find it ? > Could i provide a similar fix on DirectFB stack or should i use that the > mentioned function in the appllication code itself ? > > Awaiting for your inputs... > > Thanks & Regards > sv. > > On Mon, Jun 9, 2008 at 5:14 PM, Paul Davis <[EMAIL PROTECTED]> > wrote: > >> >> On Mon, 2008-06-09 at 16:00 +0530, svalbard colaco wrote: >> > Hi all, >> > >> > I have an application running on GTK-DirectFB and its observed >> > that , a part of the window, >> > which is a gnome canvas item is not rendered properly rather that >> > entire vbox appears black, >> > But when i click on , on a click_to_ add canvas item within that vbox >> > it appears white as expected. >> >> this happens on the quartz backend too, and is caused by the >> non-standard update model used by the canvas. there is a relatively >> simply fix on quartz. in the paint() function, the canvas should not be >> delivery expose events to itself, but instead should call >> gdk_window_invalidate_region(). >> >> >> >> >> > _______________________________________________ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
