Hi Paul,
K.. can you tell me what exactly the changes are ? I wanted to try the same
in my libgnomecanvas too.
As to what i can understand from our previous conversations ;changes were
made in
*gnome-canvas.c* in function *static void paint (GnomeCanvas *canvas)
*and commented out the line *gt
On Wed, 2008-06-11 at 20:26 +0530, svalbard colaco wrote:
> Hi Paul,
> k.
> So the "fix" you spoke about was in your application code and not in
> your GTK-quartz backend?
its in my own modified version of libgnomecanvas, which is distributed
on OS X as part of the app bundle.
_
On Wed, 2008-06-11 at 19:55 +0530, svalbard colaco wrote:
> HI all;
>
> Further debugging has shown that antialiased canvases formed using
> gnome_canvas_new_aa() appear correctly on GTK-DFB backend
> whereas canvases formed using gnome_canvas_new() fail to render on
> GTK-DirectFB ;rather they
Hi Paul,
k.
So the "fix" you spoke about was in your application code and not in your
GTK-quartz backend?
CMIIMW.
On Wed, Jun 11, 2008 at 8:04 PM, Paul Davis <[EMAIL PROTECTED]>
wrote:
>
> On Wed, 2008-06-11 at 19:55 +0530, svalbard colaco wrote:
> > HI all;
> >
> > Further debugging has show
HI all;
Further debugging has shown that *antialiased canvases* formed using
*gnome_canvas_new_aa()
*appear correctly on GTK-DFB backend
whereas canvases formed using *gnome_canvas_new()* fail to render on
GTK-DirectFB ;rather they appear black instead of white.
Hoping this will give a clearer i
