vtorri
/
efl
forked from enlightenment/efl
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

ecore: update documentation of Efl.Timer. 

I am wondering how this is going to affect our legacy API documentation
which has indeed a different lifecycle.
This commit is contained in:
Cedric BAIL 2016-05-06 15:32:32 -07:00
parent 1460321b12
commit 45d17f100e
1 changed files with 4 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
src/lib/ecore/efl_timer.eo
View File

@ -3,13 +3,11 @@ import ecore_types;
class Efl.Timer (Efl.Loop_User) class Efl.Timer (Efl.Loop_User)
{ {
[[Timers are objects that will call a given callback at some point [[Timers are objects that will call a given callback at some point
in the future. in the future and repeat that tick at a given interval.
They may also optionally repeat themselves if the timer callback returns Timers require the ecore main loop to be running and functioning
true. If it does not they will be automatically deleted and never called properly. They do not guarantee exact timing, but try to work on a
again. Timers require the ecore main loop to be running and functioning "best effort" basis.
properly. They do not guarantee exact timing, but try to work on a "best
effort" basis.
]] ]]
legacy_prefix: ecore_timer; legacy_prefix: ecore_timer;
methods { methods {