Hello all.
I've been thinking about playing with clutter lately, so I started
working on some C++ bindings. I've got a couple of questions about
the ClutterColor API. There are several functions which take a src and
a dest color argument. For this email, I'll just focus on
hi Jonathon;
On Mon, 2007-10-29 at 08:25 -0500, Jonathon Jongsma wrote:
So I guess my question is, which version most closely satisfies the
intent of the API? Is modifying a color directly (e.g.
clutter_color_darken(foo, foo)) an expected and common use case? (i
looked at the implementation
Jonathon Jongsma wrote:
Hello all.
I've been thinking about playing with clutter lately, so I started
working on some C++ bindings. I've got a couple of questions about
the ClutterColor API. There are several functions which take a src and
a dest color argument. For this email, I'll just
On Mon, 2007-10-29 at 13:56 +, Neil Roberts wrote:
On an sort of related note, I think there is a slight issue with
clutter_color_darken that I worked around in the Ruby bindings which
is that the alpha value of the destination is not copied over from the
source and is left
Maybe the C API is more useful in C because you more often have direct
access to color instance. For instance, maybe you would do something
like this:
clutter_color_darken(default_color, thing-color);
redraw_thing(thing);
But in C++ we will tend to do copy-by-value instead of allowing that
direct
(no need to Cc: me in :-))
On Mon, 2007-10-29 at 15:44 +0100, Murray Cumming wrote:
By the way, this particular function is rather strange to me. It
Darkens src by a fixed amount, and saves the changed color in dest,
but I wonder when I would ever want to darken by some unknown
unspecified
