Re: Custom DrawingArea doesn't show

[Herwig Hochleitner <hhochleitner gmail com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

| a simple minimal example showing the wrong behavior will be appreciated :)

As stated, everything works as documented (somewhere)

|> the C documentation for gdk_cairo_create() has a note:
|>
|>   Note that due to double-buffering, Cairo contexts created in a GTK+
|>   expose event handler cannot be cached and reused between different
|>   expose events.
|>
|> you need to create and destroy the cairo context for each expose event.

The issue arose because I wouldn't expect anything like double buffering
in gtk. That's the reason 'expose-event' exist anyway, isn't it?
Also the pygtk documentation for gtk.gdk.Drawable.cairo_create doesn't
state it.

I sugest the pygtk doc for cairo_create and probably DrawingArea (cairo
is the prefered API anyways, is it?) be extended.
Maybe there should also be some warning or the like when drawing to an
outdated, gdk.Drawable originated cairo context.

regards
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIpb/w2yN0WRIYfpERAswOAJ94RymteaMtjpttdmAdIhgTkukjCACggNBy
lASOrXMZzDUcxCDqJKIotxM=
=6lYQ
-----END PGP SIGNATURE-----