Been playing a little more and discovered a potentially related
problem that causes an immediate seg fault. If I create a class and
init is as below:
class MenuSelector(clutter.Texture):
def __init__ (self):
pixbuf = gtk.gdk.pixbuf_new_from_file("ui/active_bar.png")
self.set_pixbuf(pixbuf)
The app will segfault immediately if an instance of the class is
created. If I comment the final line from above then program runs, but
obviously texture is blank.
Like I said, not sure if this is a related problem, but thought it
might be useful feedback.
-Josh
On 7/11/07, Josh Stewart <[EMAIL PROTECTED]> wrote:
On 7/10/07, Emmanuele Bassi <[EMAIL PROTECTED]> wrote:
> On Tue, 2007-07-10 at 22:29 +1000, Josh Stewart wrote:
> > Hi all,
> >
> > I've been playing around with the Clutter python bindings and sinking
> > my teeth into it a little more, but have struck a bit of a problem. I
> > keep getting what appears to be an almost random error that reads:
> > Clutter-CRITICAL **: clutter_actor_get_id: assertion `CLUTTER_IS_ACTOR
> > (self)' failed
> > Clutter-CRITICAL **: clutter_actor_get_parent: assertion
> > `CLUTTER_IS_ACTOR (self)' failed
>
> what version of the C library have you compiled the python bindings
> with? the Python bindings are only tested against the current stable
> branch (clutter-0-2).
>
Yes definitely compiled against clutter-0.2. I removed 0.3 completely
and recompiled/installed to make sure.
I've attached the program if its any help (Please excuse the horribly
messy code :)
-Josh
--
To unsubscribe send a mail to [EMAIL PROTECTED]
