Hi all,

I just installed Clutter 0.3.1 with the new python bindings and fired
up my little app which seemed to run well with the exception of some
actor positioning. From what I can see the actor.get_abs_position()
function is returning very different values in 0.3.1 than 0.2 did. I
couldn't see any comments indicating that the intent of this function
had changed.

In my case, I have an actor group that is placed in the absolute
center of the stage. Calling get_abs_position on the actors within
this group gives strange results under 0.3.1 when 0.2 was fine.
The output below shows the results of calling this function on all the
actors in the group in both versions. Note that this is exactly the
same program on both occasions, with the exception of the diagnosis
text, and the actors themselves have not changed positions on screen:
************************************************************
Clutter 0.3.1 (x, y): (208, 84)
Original Group size: 106
Starting at : 459:168
Clutter 0.3.1 (x, y): (248, 153)
Clutter 0.3.1 (x, y): (248, 207)
Clutter 0.3.1 (x, y): (248, 261)
Clutter 0.3.1 (x, y): (248, 315)
Clutter 0.3.1 (x, y): (248, 369)

and 0.2

Clutter 0.2 (x, y): (415, 161)
Original Group size: 106
Starting at : 459:161
Clutter 0.2 (x, y): (415, 215)
Clutter 0.2 (x, y): (415, 269)
Clutter 0.2 (x, y): (415, 323)
Clutter 0.2 (x, y): (415, 377)
Clutter 0.2 (x, y): (415, 431)
************************************************************

The results given from 0.3.1 seem to be the incorrect ones. This is
shown by the fact that the location of the last actor is definitely in
the bottom half of my 1024x768 screen and so its y coord should be
greater than 384.
I took a look through this function in clutter-actor.c and noticed
that the logic behind it has changed between the two versions
(Switching to using get_abs_position_units() and then converting to
pixels) but I think there's a problem with the new method.

I tried registering an account with your Bugzilla instance to check
whether this was a known issue but never received the temporary
password?

-Josh
-- 
To unsubscribe send a mail to [EMAIL PROTECTED]

Reply via email to