Again thanks for your reply Tom.
Said to say: they are recognized. I don't know why. The regions are commented 
out. Yet the error.

I'll run some small compiler test on friday.

BR,

Leif

ERR:EDJE_CC edje_cc_out.c:1252 data_process_lookups() /opt/e17/bin/edje_cc: 
Error. Unable to find part name "increase_button".
make[4]: *** [default.edj] Error 255
make[3]: *** [all-recursive] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

Am 07.03.2010 um 13:44 schrieb Tom Haste:

> Heres the actual code for all those apparently uncommented parts. The
> /* comment */ section shouldnt be recognized at all. Having said that,
> could this been some sort fo Mac weirdness? What happens if you delete
> this whole section?
> 
> /*
>        program {
>           name: "next_governor";
>           signal: "mouse,down,1";
>           source: "cpu";
>           action: SIGNAL_EMIT "e,action,governor,next" "";
>        }
>        program {
>           name: "next_governor2";
>           signal: "mouse,down,1";
>           source: "cpu";
>           action: STATE_SET "clicked" 0.0;
>           target: "cpu";
>        }
>        program {
>           name: "next_governor3";
>           signal: "mouse,up,1";
>           source: "cpu";
>           action: STATE_SET "default" 0.0;
>           target: "cpu";
>        }
>        program {
>           name: "increase_frequency";
>           signal: "mouse,down,1";
>           source: "increase";
>           action: SIGNAL_EMIT "e,action,frequency,increase" "";
>        }
>        program {
>           name: "increase_frequency2";
>           signal: "mouse,down,1";
>           source: "increase";
>           action: STATE_SET "clicked" 0.0;
>           target: "increase_button";
>        }
>        program {
>           name: "increase_frequency3";
>           signal: "mouse,up,1";
>           source: "increase";
>           action: STATE_SET "default" 0.0;
>           target: "increase_button";
>        }
>        program {
>           name: "decrease_frequency";
>           signal: "mouse,down,1";
>           source: "decrease";
>           action: SIGNAL_EMIT "e,action,frequency,decrease" "";
>        }
>        program {
>           name: "decrease_frequency2";
>           signal: "mouse,down,1";
>           source: "decrease";
>           action: STATE_SET "clicked" 0.0;
>           target: "decrease_button";
>        }
>        program {
>           name: "decrease_frequency3";
>           signal: "mouse,up,1";
>           source: "decrease";
>           action: STATE_SET "default" 0.0;
>           target: "decrease_button";
>        }
> */
> 
> 
> 
> 
> On 7 March 2010 20:00, Leif Middelschulte <leif.middelschu...@gmail.com> 
> wrote:
>> Thanks for reply Toma,
>> 
>> Am 07.03.2010 um 04:23 schrieb Tom Haste:
>> 
>>> The only mention of those parts are in in the CPU freq code, and
>>> theyre all commented out.
>> I just removed my entire checkout and got me a fresh one.
>> 
>> $ cd e/data/themes/
>> 
>> $ grep -R increase *
>> default.edc://          set_state(PART:"increase_button", "inactive", 0.0);
>> default.edc://          set_state(PART:"increase", "inactive", 0.0);
>> default.edc://          set_state(PART:"increase_button", "default", 0.0);
>> default.edc://          set_state(PART:"increase", "default", 0.0);
>> default.edc:        name: "increase_frequency";
>> default.edc:        source: "increase";
>> default.edc:        action: SIGNAL_EMIT "e,action,frequency,increase" "";
>> default.edc:        name: "increase_frequency2";
>> default.edc:        source: "increase";
>> default.edc:        target: "increase_button";
>> default.edc:        name: "increase_frequency3";
>> default.edc:        source: "increase";
>> default.edc:        target: "increase_button";
>> 
>> $ grep -R decrease *
>> default.edc://          set_state(PART:"decrease_button", "inactive", 0.0);
>> default.edc://          set_state(PART:"decrease", "inactive", 0.0);
>> default.edc://          set_state(PART:"decrease_button", "default", 0.0);
>> default.edc://          set_state(PART:"decrease", "default", 0.0);
>> default.edc:        name: "decrease_frequency";
>> default.edc:        source: "decrease";
>> default.edc:        action: SIGNAL_EMIT "e,action,frequency,decrease" "";
>> default.edc:        name: "decrease_frequency2";
>> default.edc:        source: "decrease";
>> default.edc:        target: "decrease_button";
>> default.edc:        name: "decrease_frequency3";
>> default.edc:        source: "decrease";
>> default.edc:        target: "decrease_button";
>> 
>> so as I see the state sets are commented out, but the targets are not. So 
>> the compiler (edje_cc) has to fail right?
>> 
>>> Are you using the most recent SVN checkout?
>>> It looks fine with SVN revision 46921.
>> see above.
>> $ svnversion .
>> 46936
>> 
>> BR,
>> 
>> Leif
>> 
>>> 
>>> Toma
>>> 
>>> 
>>> On 7 March 2010 01:39, Leif Middelschulte <leif.middelschu...@gmail.com> 
>>> wrote:
>>>> Hello,
>>>> 
>>>> I noticed that the parts "increase", "increase_button", "decrease", and 
>>>> "decrease_button" are missing but targeted in e's default.edc which leads 
>>>> to a failure during build.
>>>> 
>>>> Another bug appears on OSX during 'msgmerge --update' command due to acl 
>>>> reasons apparently.
>>>> A workaround is extending the command with '--backup=off'.
>>>> 
>>>> BR,
>>>> 
>>>> Leif Middelschulte
>>>> ------------------------------------------------------------------------------
>>>> Download Intel&#174; Parallel Studio Eval
>>>> Try the new software tools for yourself. Speed compiling, find bugs
>>>> proactively, and fine-tune applications for parallel performance.
>>>> See why Intel Parallel Studio got high marks during beta.
>>>> http://p.sf.net/sfu/intel-sw-dev
>>>> _______________________________________________
>>>> enlightenment-devel mailing list
>>>> enlightenment-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
>>>> 
>> 
>> 


------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to