Robert,
First-off, thanks for that great reply.
Your assumption was correct — I am using the
xxx.set_property('pick-with-alpha',True) and then cloning xxx.
My use-case is mainly centered around CairoTexture actors. I get RSVG to
do the drawing which has the side-effect of leaving me sans a path to
use in a manual do_pick function. (Unless I am missing something in
rsvg, but even-so I'd have to translate the path over to cogl drawing
commands.)
Using something automatic to achieve picking is just what the doc
ordered, and pick-with-alpha is it.
If that doesn't work for you then it's a bug.
For the original Actor, it's working just fine.
something like:
A "pick-with-source-shape" boolean property (default FALSE to match
current semantics)
From your further descriptions, I think that would do nicely.
One thing to note is that presumably if the source was a
composite/container actor then we would still traverse all its children
to paint their picking geometry, and I think you'd expect all of those
children to also pick with the overridden ID of the clone.
You make me wonder. I had assumed a clone of a container would clone all
the children too.
I don't know enough about clutter really, but I'd assume the
aggregate-pick belongs to the clone. Identifying as the original actor
could be a manual task of sending a signal to the original once the
clone has received the event.
2) being able to use the pick-with-source-shape method with the clone's
ID (as above) but possibly not draw picking geometry for children of
composite/container actors.
I suppose this depends on whether the original even has a shape, it may
be a pure container. Some kind of 'go X levels up the container tree'
thing comes to mind, but sounds too complex.
Perhaps the clone could simply have a function in the original
registered with it that it should use for getting the pick-shape. Some
kind of ('pick-with-source-function', source.use_this_func) affair, but
I am out of my depth here.
It could be good to file a feature request for the above ClutterClone
property so we can keep track of this and potentially - since it sounds
like it wouldn't be too tricky to implement - we might be able to get
this done for 1.4.
S'magic. I shall hit the site and make it so.
Thanks,
\d
_______________________________________________
clutter-app-devel-list mailing list
[email protected]
http://lists.clutter-project.org/listinfo/clutter-app-devel-list
