Can someone point out to me whether there's a way to solve the following problem?
Until recently the way I used all "base" classes like Clutter::Texture was by deriving from them and overriding the create() method to return a RefPtr to the new object. (and then adding my own handlers, member variables and methods while preserving the main behaviour) The specific problem is when I do: Glib::RefPtr<MyClass> my_object = MyClass::create(); [....] my_object.reset(); to force the destructor to be called, it isn't. The destructor isn't even called when the program is cleanly closed (when even hidden reference counts should be decremented). Is this to be expected because the destructor of Clutter::Texture has not been wrapped (the source claims technical difficulties) or is this a bug in Clutter::Texture? I would much prefer to avoid using the texture as a member of my custom class because the code is cleaner. (I currently do that as a workaround to the above problem) Thanks in advance! -Bartek -- To unsubscribe send a mail to [email protected]
