this allows you to specify the default color for any parts using color_classes in a given file.
this color will be overridden by edje_color_class_set()
which will in turn be overridden by edje_object_color_class_set()
note. if you specify a color (color: ...) in a part description that also has a color_class, the cc will be multiplied against the color -- generally not what you want.
also, as a tip, the gimp's 'multiply' blend mode is almost exactly the same as evas/edje's coloring.
example:
...
part {
name: "colored";
type: RECT;
description {
state: "default" 0.0;
color_class: "bg_color";
/* note: no color: set here */
}
}
...
color_classes {
color_class {
name: "bg_color";
color: 229 239 255 255;
}
}
SVN revision: 19708
this allows you to specify the default color for any parts using color_classes in a given file.
this color will be overridden by edje_color_class_set()
which will in turn be overridden by edje_object_color_class_set()
note. if you specify a color (color: ...) in a part description that also has a color_class, the cc will be multiplied against the color -- generally not what you want.
also, as a tip, the gimp's 'multiply' blend mode is almost exactly the same as evas/edje's coloring.
example:
...
part {
name: "colored";
type: RECT;
description {
state: "default" 0.0;
color_class: "bg_color";
/* note: no color: set here */
}
}
...
color_classes {
color_class {
name: "bg_color";
color: 229 239 255 255;
}
}
SVN revision: 19707
* both exe run functions now use the same code.
* don't allocate pipes that wan't be used. This made the code much cleaner.
* track and free the exe timers as needed.
E still reports a naughty null timer free at shutdown time, but I don't
think its in ecore_exe. I'll valgrind it later.
The error fd handler is curently an identical copy of the read fd handler,
with only the names changed. That's a big slab of code that is duplicated.
I'll merge the two into something generic next.
raster also mentioned that say the first ten lines or so of stderr should
be thrown into a dialog and shown to the user. I don't know if there is a
way to do that from ecore, or if the user of ecore_exe has to do that
themselves. The stderr support does line buffered mode just like the read
support, but has not been tested yet. I'll test properly after the merge.
SVN revision: 19700
Carsten Haitzler
David Walter Seikel
Dan Sinclair
rbdpngn
rephorm
handyande
doursse
Mike Frysinger
sebastid
Kim Woelders