On Wed, 2009-09-09 at 15:16 +0200, Danny Haak wrote:
> On Wed, 2009-09-09 at 12:14 +0100, Emmanuele Bassi wrote:
> > I'm referring to the C API, but I think the C# API will probably look
> > similar.
>
> Yes, true. But, the main problem is that the documentation and examples
> are not quite on par with the code sometimes, which is confusing. Which
> is also the main reason for me to try to update the examples for
> clutter-sharp - to make it easier for people to start :).
yeah, I guess the example code needs to be ported to the 1.0 API.
> > ClutterAlpha's constructor does not take a function any more: it uses
> > easing modes (an enumeration value).
>
> Clear now. The main problem is that the Alpha function accepts an ulong,
> and not the enum; which is confusing. I will try to fix that (not that
> experience in invoking c libraries in C#) and make a patch.
>
> Another issue arose: while BehaviourOpacity is working, BehaviourPath is
> not: GLib-GObject-WARNING **: IA__g_object_new_valist: invalid unclassed
> object pointer for value type `ClutterPath'. I will look into that as
> well.
ClutterBehaviourPath uses the ClutterPath object, which encapsulates all
the functionality that concerned describing paths from BehaviourPath and
BehaviourBspline. you'll need to create a new Path object and pass it to
the BehaviourPath behaviour -- something like:
# define a path as a set of nodes
my $behaviour = Clutter::BehaviourPath->new(
Clutter::Alpha->new($timeline, 'ease-out-cubic'),
Clutter::Path->new(
[ 'move-to', [ [ 100, 100 ] ] ],
[ 'line-to', [ [ 200, 100 ] ] ],
[ 'line-to', [ [ 200, 200 ] ] ],
[ 'curve-to', [ [ 100, 200 ], [ 100, 200 ], [ 100, 100 ] ] ],
),
);
or
# define a path using a SVG-like description
my $behaviour = Clutter::BehaviourPath->new(
Clutter::Alpha->new($timeline, 'ease-out-cubic'),
Clutter::Path->new("M 100,100 L 200,100 L 200,200 C 100,200 100,200
100,100"),
);
in Perl.
I actually need to add this example to the migration guide. :-)
> > since I receive the Bugzilla email for each Clutter bug, I'd like to
> > point out something that you did and that is always a pet peeve of mine:
> > do *not* set the target milestone -- it's not something for you to set:
> > it's for the maintainers and/or QA. the same applies to severity and
> > priority.
>
> Excuse me, not my intention - will refrain from it next time. Maybe
> remove that field in the bug-enter form anyway?
it has its uses, if a maintainer and/or a QA engineer files a bug. the
bug filing form, though, needs some love anyway, maybe taking some of
the lessons learned from the GNOME Bugzilla.
ciao,
Emmanuele.
--
Emmanuele Bassi, Senior Engineer | [email protected]
Intel Open Source Technology Center | http://oss.intel.com
--
To unsubscribe send a mail to [email protected]
