On Sun, Mar 13, 2011 at 8:43 PM, Andreas Volz <li...@brachttal.net> wrote:
> Am Sun, 13 Mar 2011 20:23:01 -0300 schrieb Gustavo Sverzut Barbieri:
>
>> On Sun, Mar 13, 2011 at 7:36 PM, Andreas Volz <li...@brachttal.net>
>> wrote:
>> > Am Sun, 13 Mar 2011 19:09:30 +0100 schrieb Andreas Volz:
>> >
>> >> Am Sun, 13 Mar 2011 13:13:37 -0300 schrieb Gustavo Sverzut
>> >> Barbieri:
>> >>
>> >> > On Sun, Mar 13, 2011 at 12:54 PM, Andreas Volz
>> >> > <li...@brachttal.net> wrote:
>> >> > > Hello,
>> >> > >
>> >> > > does someone know how I could call a generic purpose signal
>> >> > > with editje after finish an animation signal? Like with edc
>> >> > > "after". I've to signal my application when an animation is
>> >> > > finished. I tried to write an edc by hand with after
>> >> > > transition. It seems editje doesn't show after. So how could I
>> >> > > do this?
>> >> >
>> >> > Take a look at the generated EDC, you'll see Editje ALWAYS create
>> >> > such "animation ended" signals for you. You just have to listen
>> >> > to them in your app.
>> >>
>> >> Ah, thanks. This is good, but maybe not sufficient for my use case.
>> >> I'll explain you with my hand written edc code what I need:
>> >>
>> >>       programs {
>> >>          program { name: "visible";
>> >>             signal: "visible";
>> >>             source: "stateval";
>> >>             action: STATE_SET "visible" 0.00;
>> >>             transition: LINEAR 0.50000;
>> >>             target: "border";
>> >>             target: "text";
>> >>             after: "visible_signal";
>> >>          }
>> >>          program { name: "invisible";
>> >>             signal: "invisible";
>> >>             source: "stateval";
>> >>             action: STATE_SET "default" 0.00;
>> >>             transition: LINEAR 0.50000;
>> >>             target: "border";
>> >>             target: "text";
>> >>             after: "invisible_signal";
>> >>          }
>> >>          program { name: "visible_signal";
>> >>             signal: "";
>> >>             source: "";
>> >>             action: SIGNAL_EMIT "visible_signal" "edje";
>> >>          }
>> >>          program { name: "invisible_signal";
>> >>             signal: "";
>> >>             source: "";
>> >>             action: SIGNAL_EMIT "invisible_signal" "edje";
>> >>          }
>> >>
>> >> My application logic is very generic and needs this spec for each
>> >> edje view:
>> >>
>> >> - visible (IN)
>> >>   - signal:visible
>> >>   - source:stateval
>> >>
>> >> - invisible (IN)
>> >>   - signal:invisible
>> >>   - source:stateval
>> >>
>> >> - visible_signal (OUT)
>> >>   - signal:visible
>> >>   - source:edje
>> >>
>> >> - invisible_signal (OUT)
>> >>   - signal:invisible
>> >>   - source:edje
>> >>
>> >> It just provides two IN signals to show and hide a view and edje
>> >> provides two OUT signals to tell my application when it's finished
>> >> shown or hidden. So I couldn't use your editje provided signals as
>> >> they have a name that is very dependant of the animation.
>> >>
>> >> Do you've some idea how I could map editje behaviour to my needs?
>> >>
>> >> BTW: What is that "api" export function? Is this maybe usable for
>> >> my needs? There's nothing written in the wiki about it.
>> >>
>> >> I'm also motivated to change my spec if needed or maybe provide
>> >> some patches to change editje to support my needs. Hand writing
>> >> all my animations isn't so funny all the time... :-(
>> >
>> > Hm, I got it somehow working if I name my animations visible and
>> > invisible and change my logic to register for:
>> >
>> > "animation,end", "invisible"
>> > "animation,end", "visible"
>> >
>> > Then it's generic for me. The editje created prototype was working.
>> > I'll create a bigger one for my application and see if it's ok.
>> >
>> > Thank you for providing this great editor! :-)
>>
>> Great you like it!
>
> Another question: Is it possible to create animations longer than 1 sec?

Not yet. It was a planned feature but the project was ended by the
client. There was some usability issues to solve and that required
changes to that timeline, but shouldn't be something impossible to do,
will just require some work.


-- 
Gustavo Sverzut Barbieri
http://profusion.mobi embedded systems
--------------------------------------
MSN: barbi...@gmail.com
Skype: gsbarbieri
Mobile: +55 (19) 9225-2202

------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to