After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 694197 - clutter_matrix_progress works unexpectedly
clutter_matrix_progress works unexpectedly
Status: RESOLVED INCOMPLETE
Product: clutter
Classification: Platform
Component: general
1.12.x
Other Linux
: Normal normal
: ---
Assigned To: clutter-maint
clutter-maint
Depends on:
Blocks:
 
 
Reported: 2013-02-19 18:20 UTC by ChangSeok Oh
Modified: 2013-06-04 12:20 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description ChangSeok Oh 2013-02-19 18:20:53 UTC
Hi. I'm a WebKit developer. So I don't believe I have deep understanding about clutter.
Now a day, I'm doing some work related with css animation with clutter in WebKitGtk.
You can see what I'm doing in here. https://bugs.webkit.org/show_bug.cgi?id=109848

The problem is that I can see nothing when using clutter 'transform' property transition. yeah.. the clutter matrix animation is not working properly.
I'm suspecting the way of interpolating two matrices in clutter. Because it's fine when I use the webkit provided decomposing & interpolating api. 
http://trac.webkit.org/browser/trunk/Source/WebCore/platform/graphics/transforms/TransformationMatrix.cpp#L1375

As my investigation, clutter private api, clutter_matrix_progress seems doing same work, but I don't know what is the major difference between them.
Comment 1 Emmanuele Bassi (:ebassi) 2013-02-20 22:29:54 UTC
there should not be any difference at all: the matrix decomposition code is the same outlined (and used) by the CSS3 transformation specification.

what does "not working properly" means? do you have a (self-contained) test case that demonstrates that interpolating between two matrices does not produce the intended result?
Comment 2 Tobias Mueller 2013-06-04 12:20:42 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!