On Mon, May 18, 2009 at 17:10, Mikael Liljeroth
wrote:
> Thanks for your help. I think the clip thing should solve my problem very
> well, defines would also solve my problem but I really would like to limit
> the number of Edje programs and signals sent. I also have an other issue
> where I want
Thanks for your help. I think the clip thing should solve my problem very
well, defines would also solve my problem but I really would like to limit
the number of Edje programs and signals sent. I also have an other issue
where I want to hide and show edje parts from c? Is this possible without
edj
Hello,
I have tackled this myself, and at one point used some macros as
defined in the cookbook here :
http://wiki.enlightenment.org/index.php/Creating_Edje_User_Interfaces#Edje_Code
I did have to do some re-organization of course, but in the end was able
to generate 12 icons that would pulse,
On Mon, 18 May 2009 07:33:32 -0700 Mikael Liljeroth
said:
> Hi, I have a question regarding Edje. In very large user interfaces almost
> every part has an invisible state and one visible state. Each of these parts
> also has a corresponding program to show or hide the part. This makes the
> edc f
You could use a define...
eg. see the ICONS section in E17s default theme. Just create the
define at the top of the file and call the show/hide program.
#define SHOW(blah) \
program { name: blah"1"; \
action: STATE_SET "active" 0.0; \
target: blah; \
} \
progr
Hi, I have a question regarding Edje. In very large user interfaces almost
every part has an invisible state and one visible state. Each of these parts
also has a corresponding program to show or hide the part. This makes the
edc file very big and hard to read. Is there some way to generalize the
p
