WWW-www.enlightenment.org pushed a commit to branch master.

http://git.enlightenment.org/website/www-content.git/commit/?id=d791fce23ad34ce21394953abae431c483009f75

commit d791fce23ad34ce21394953abae431c483009f75
Author: Lauro Moura <lauromo...@expertisesolutions.com.br>
Date:   Thu Dec 10 18:20:45 2015 -0800

    Wiki page timer changed with summary [] by Lauro Moura
---
 pages/api/javascript/ecore/timer.txt | 46 +++++++++++++++++++++---------------
 1 file changed, 27 insertions(+), 19 deletions(-)

diff --git a/pages/api/javascript/ecore/timer.txt 
b/pages/api/javascript/ecore/timer.txt
index 85ad4bf..c106525 100644
--- a/pages/api/javascript/ecore/timer.txt
+++ b/pages/api/javascript/ecore/timer.txt
@@ -52,52 +52,60 @@ Works like ''efl.Ecore.Timer.add'', but the reference "now" 
time is the time tha
 
 === timerObj.del() ===
 
+Syntax
+
+<code javascript>
+timerObj.del();
+</code>
 
+Deletes the callee timer object from the list of active timers.
 
-=== dump(args) ===
+=== dump() ===
 
 Syntax
 
 <code javascript>
-    code
+var log = efl.Ecore.Timer.dump();
 </code>
 
-Parameters
-
-   * parameters
-
 Return value
 
-   * return
+   * string - The human-readable log.
+
+This function returns a human-readable text-based log for Ecore Timer events.
 
-=== getPrecision(args) ===
+=== getPrecision() ===
 
 Syntax
 
 <code javascript>
-    code
+var precision = efl.Ecore.Timer.getPrecision();
 </code>
 
-Parameters
-
-   * parameters
-
 Return value
 
-   * return
+   * number - The current precision for all timers.
+
+Retrieves the current precision used by timer infrastructure.
 
-=== setPrecision(args) ===
+=== setPrecision(precision) ===
 
 Syntax
 
 <code javascript>
-    code
+    efl.Ecore.Timer.setPrecision(precision);
 </code>
 
 Parameters
 
-   * parameters
+   * precision - A number with the allowed introduced timeout delay, in 
seconds.
 
-Return value
+This sets the precision for **all** timers. The precision determines how much 
of a difference from the requested interval is acceptable. One common reason to 
use this function is to **increase** the allowed timeout and thus, **decrease** 
the precision of the timers, this is because less precise the timers result in 
the system waking up less often and thus consuming fewer resources.
+
+Be aware that kernel may delay delivery even further, these delays are always 
possible due other tasks having higher priorities or other scheduler policies.
+
+Example: We have 2 timers, one that expires in a 2.0s and another that expires 
in 2.1s, if precision is 0.1s, then the Ecore will request for the next expire 
to happen in 2.1s and not 2.0s and another one of 0.1 as it would before.
 
-   * return
\ No newline at end of file
+<note important>
+Ecore is smart enough to see if there are timers in the precision range, if it 
does not, in our example if no second timer in (T + precision) existed, then it 
would use the minimum timeout.
+</note>
\ No newline at end of file

-- 


Reply via email to