| … | |
… | |
| 4 | <head> |
4 | <head> |
| 5 | <title>libev</title> |
5 | <title>libev</title> |
| 6 | <meta name="description" content="Pod documentation for libev" /> |
6 | <meta name="description" content="Pod documentation for libev" /> |
| 7 | <meta name="inputfile" content="<standard input>" /> |
7 | <meta name="inputfile" content="<standard input>" /> |
| 8 | <meta name="outputfile" content="<standard output>" /> |
8 | <meta name="outputfile" content="<standard output>" /> |
| 9 | <meta name="created" content="Mon Nov 12 10:01:12 2007" /> |
9 | <meta name="created" content="Mon Nov 12 10:02:16 2007" /> |
| 10 | <meta name="generator" content="Pod::Xhtml 1.57" /> |
10 | <meta name="generator" content="Pod::Xhtml 1.57" /> |
| 11 | <link rel="stylesheet" href="http://res.tst.eu/pod.css"/></head> |
11 | <link rel="stylesheet" href="http://res.tst.eu/pod.css"/></head> |
| 12 | <body> |
12 | <body> |
| 13 | <div class="pod"> |
13 | <div class="pod"> |
| 14 | <!-- INDEX START --> |
14 | <!-- INDEX START --> |
| … | |
… | |
| 586 | <p>It must return the next time to trigger, based on the passed time value |
586 | <p>It must return the next time to trigger, based on the passed time value |
| 587 | (that is, the lowest time value larger than to the second argument). It |
587 | (that is, the lowest time value larger than to the second argument). It |
| 588 | will usually be called just before the callback will be triggered, but |
588 | will usually be called just before the callback will be triggered, but |
| 589 | might be called at other times, too.</p> |
589 | might be called at other times, too.</p> |
| 590 | <p>NOTE: <i>This callback must always return a time that is later than the |
590 | <p>NOTE: <i>This callback must always return a time that is later than the |
| 591 | passed <code>now</code> value</i>. Not even <code>now</code> itself will do, it must be larger.</p> |
591 | passed <code>now</code> value</i>. Not even <code>now</code> itself will do, it <i>must</i> be larger.</p> |
| 592 | <p>This can be used to create very complex timers, such as a timer that |
592 | <p>This can be used to create very complex timers, such as a timer that |
| 593 | triggers on each midnight, local time. To do this, you would calculate the |
593 | triggers on each midnight, local time. To do this, you would calculate the |
| 594 | next midnight after <code>now</code> and return the timestamp value for this. How you do this |
594 | next midnight after <code>now</code> and return the timestamp value for this. How |
| 595 | is, again, up to you (but it is not trivial).</p> |
595 | you do this is, again, up to you (but it is not trivial, which is the main |
|
|
596 | reason I omitted it as an example).</p> |
| 596 | </dd> |
597 | </dd> |
| 597 | </dl> |
598 | </dl> |
| 598 | </p> |
599 | </p> |
| 599 | </dd> |
600 | </dd> |
| 600 | <dt>ev_periodic_again (loop, ev_periodic *)</dt> |
601 | <dt>ev_periodic_again (loop, ev_periodic *)</dt> |
