On Wed, 2008-10-15 at 05:48 -0700, ere wer wrote: > In general I think it is to be expected to get this sort of information from > the actor itself because this makes > the actor "self-contained" - it knows what alters its original definition > (width, height, x, y, color/texture)
it really doesn't know anything of sort: it knows its position, size, rotation and such - a ClutterActor cannot distinguish from a call to clutter_actor_set_size() from within your application and a behaviour. > We already have : > for geometry(is_scaled(), is_rotated(), etc), these are properties internal to the actor. > for appearance (get_clip(), get_shader(), etc), same as above. > for hierarchy(get_parent(), etc) this is needed for painting. a behaviour is a construct that shields you from updating the actor yourself on every frame; it's not part of the scenegraph: it manipulates one or more nodes on it. > ... and there should be > for behavior - does an actor plays a role? - (get/set_behavior(s)(), etc) as I said, this can be easily done outside ClutterActor from your application (you already have the behaviours you have instantiated, and you have access to the scenegraph) or your framework. I personally doubt how much useful would this be - unless you can present a use case where this information is impossible to retrieve with the current API. ciao, Emmanuele. -- Emmanuele Bassi, Intel Open Source Technology Center -- To unsubscribe send a mail to [EMAIL PROTECTED]
