From: Cedric BAIL <cedric@osg.samsung.com>
Date: Fri, 6 May 2016 22:32:32 +0000 (-0700)
Subject: ecore: update documentation of Efl.Timer.
X-Git-Tag: upstream/1.20.0~6451
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=45d17f100e927ee90ea782a387893add0e7f3fbd;p=platform%2Fupstream%2Fefl.git

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.
---

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;
 class Efl.Timer (Efl.Loop_User)
 {
    [[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
-     true. If it does not they will be automatically deleted and never called
-     again. Timers require the ecore main loop to be running and functioning
-     properly. They do not guarantee exact timing, but try to work on a "best
-     effort" basis.
+     Timers require the ecore main loop to be running and functioning
+     properly. They do not guarantee exact timing, but try to work on a
+     "best effort" basis.
    ]]
    legacy_prefix: ecore_timer;
    methods {