Hi,
I used cluttermm a few years back, and liked the API and integration
with Gtkmm. When I went back to it last year, however, there hadn't
been any work done on it for a while. Clutter has changed a significant
amount since then. I've been trying to rewrap it for a while, and now
I'm at t
fre 2011-10-07 klockan 15:34 +1300 skrev Ian Martin:
> Hi,
> Another question.
> I'm trying to wrap Clutter::State at present. It's got a struct within
> it called State. Will it be causing name clashes with the C++ generated
> class? I can't see how it won't, and I'm getting tied in verbal kn
Hi,
Another question.
I'm trying to wrap Clutter::State at present. It's got a struct within
it called State. Will it be causing name clashes with the C++ generated
class? I can't see how it won't, and I'm getting tied in verbal knots
trying to figure out how to wrap the State struct within
Hi,
I'm trying to wrap the animation classes in Cluttermm.
Clutter::Animation is the basic animation class. It's got a restricted
interface- for instance it only animates one object, and the start and
finish times are the only two points where an actor's location can be
defined.
In the C code
On So, 2011-09-04 at 04:32 -0700, Ian Martin wrote:
> The return value is a pointer to the object itself. In C I believe
> this helps chain the function; I'm struggling to see why I'd bother in
> C++. So can I change it to return void (or mabe bool?) or is that
> messing with the library too muc
Hi,
I'm having a crack at wrapping a bit of the Clutter library. The
Clutter::Animator::set_key function is keeping me entertained at present. The
C function is:
ClutterAnimator* clutter_animator_set_key (ClutterAnimator *animator, GObject
*object, const gchar *property_name, guint mode, g
