On Thu, 2005-08-25 at 19:02 -0400, Chris Spencer wrote: > Chris Spencer wrote: > > > Is there a way to make the canvas use anti-alaising? Neither of those > > examples seem to make use of it. The C docs mention > > gnome_canvas_new_aa(), but I can find no similar function or attribute > > in the gnomecanvas module. The doc string for the Canvas class lists > > an 'aa' attribute, but when I try to access it I get an exception. > > > > http://developer.gnome.org/doc/tutorials/gnome-libs/gnomecanvas-widget.html > > > > Chris > > After reading through > http://cvs.gnome.org/viewcvs/gnome-python/gnome-python/gnomecanvas/canvas.override?rev=1.25&view=markup > it would appear the python binding of gnomecanvas has all the advanced > anti-aliasing functionality disabled. Namely the line "ignore > gnome_canvas_new_aa" and the following definition of _wrap_gnome_canvas_new. > > Is there a reason for this? I was attracted to GTK because of its > current and upcoming support for vector graphics. I can't understand why > the python bindings would simply throw away such rare and useful > functionality.
*sigh* You are reading the code wrong. gnome_canvas_new_aa is ignored because the Canvas constructor accepts an 'aa' optional parameter. To enable aa, create your canvas with gnomecanvas.Canvas(aa=True). To avoid future confusion I added aa=True to one of the canvas examples in gnome-python. Regards. > > Sincerely, > Chris > _______________________________________________ > pygtk mailing list [email protected] > http://www.daa.com.au/mailman/listinfo/pygtk > Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/ -- Gustavo J. A. M. Carneiro <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> The universe is always one step beyond logic _______________________________________________ pygtk mailing list [email protected] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
