Re: [clutter] python cluttercairo segfault

On Wed, Apr 23, 2008 at 10:50 AM, Dirk Meyer <dischi_at_freevo.org> wrote:
> Looking at the cairo bindings code, I'm kind of confused. The
> auto-generated cluttercairo.c has a function _wrap_clutter_cairo_new
> that does NOT call clutter_cairo_new new at all and the size is all
> wrong. Example:
>
> | texture = clutter.cluttercairo.CairoTexture(100, 100)
> | print texture.get_size() # returns 0,0 ????
> | context = texture.cairo_create() # segfault

>>> import clutter
>>> from clutter import cluttercairo
>>> texture = clutter.cluttercairo.CairoTexture(100, 100)
>>> texture.get_size()
(0, 0)

Yup, get_size isn't useful in this context. So let's see if we can find it.

>>> texture.get_property("surface-width")
100

There he is.

>>> (control+D typed)

(:24481): GLib-GObject-CRITICAL **: g_type_instance_get_private:
assertion `instance != NULL && instance->g_class != NULL' failed
Segmentation fault (core dumped)

Yep. Note clue given. I mean, it don't mean nuthin' to me, but it
might mean something to someone else. But that instance sure is NULL.
Or his class is I guess.

Blake

-- 
Blake Ramsdell | http://www.blakeramsdell.com
-- 
To unsubscribe send a mail to clutter+unsubscribe_at_o-hand.com