summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCedric BAIL <cedric@osg.samsung.com>2016-05-06 15:32:32 -0700
committerCedric BAIL <cedric@osg.samsung.com>2016-05-06 15:35:36 -0700
commit45d17f100e927ee90ea782a387893add0e7f3fbd (patch)
tree5c50fa87723cc5e1359413a7dd57031547c4191c
parent1460321b125bb3149bde9b1ad98e6eb9f49741df (diff)
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.
-rw-r--r--src/lib/ecore/efl_timer.eo10
1 files changed, 4 insertions, 6 deletions
diff --git a/src/lib/ecore/efl_timer.eo b/src/lib/ecore/efl_timer.eo
index f44052e..10bcbef 100644
--- a/src/lib/ecore/efl_timer.eo
+++ b/src/lib/ecore/efl_timer.eo
@@ -3,13 +3,11 @@ import ecore_types;
3class Efl.Timer (Efl.Loop_User) 3class Efl.Timer (Efl.Loop_User)
4{ 4{
5 [[Timers are objects that will call a given callback at some point 5 [[Timers are objects that will call a given callback at some point
6 in the future. 6 in the future and repeat that tick at a given interval.
7 7
8 They may also optionally repeat themselves if the timer callback returns 8 Timers require the ecore main loop to be running and functioning
9 true. If it does not they will be automatically deleted and never called 9 properly. They do not guarantee exact timing, but try to work on a
10 again. Timers require the ecore main loop to be running and functioning 10 "best effort" basis.
11 properly. They do not guarantee exact timing, but try to work on a "best
12 effort" basis.
13 ]] 11 ]]
14 legacy_prefix: ecore_timer; 12 legacy_prefix: ecore_timer;
15 methods { 13 methods {