Lines Matching refs:start

52      // initialise an io watcher, then start it
57      // initialise a timer watcher, then start it
689 the name, you can call it anytime you are allowed to start or stop
808 after you have initialised all your watchers and you want to start
927 third-party libraries. Just remember to I<unref after start> and I<ref
1133 To make the watcher actually watch out for events, you have to start it
1134 with a watcher-specific start function (C<< ev_TYPE_start (loop, watcher
1195 Callbacks of both watcher types can start and stop as many watchers as
1197 C<ev_prepare> watcher might start an idle watcher to keep C<ev_run> from
1508 the normal watcher callback, you just start the idle watcher. The real
1534      // start the idle watcher to handle the actual event.
1546      // have to start the I/O watcher again, as
1556 In the "real" world, it might also be beneficial to start a timer, so that
1814 =item 1. Use a timer and stop, reinitialise and start it on activity.
1817 start the watcher:
1823 and start it again:
1834 =item 2. Use a timer and re-start it with C<ev_timer_again> inactivity.
1840 of C<60> and then call C<ev_timer_again> at start and each time you
1849 At start:
1917 and simply start the timer with this timeout value.
1927 To start the machinery, simply initialise the watcher and set
1929 now), then call the callback, which will "do the right thing" and start
2147 and start the timer, if necessary.
2199    ev_timer_again (&mytimer); /* start timer */
2203    // reset the timeout to start ticking again at 10 seconds
2891 Example: Dynamically allocate an C<ev_idle> watcher, start it, and in the
3110        // create/start io watcher that sets the relevant bits in fds[n] and increment got_events
3113        // create/start timer
3159 C<ev_embed_sweep> function directly, it could also start an idle watcher
3289 process typically wants to start fresh, i.e. without any active watchers.
3299 other reasons, then in the process that wants to start "fresh", call
3527 or timeout without having to allocate/configure/start/stop/free one or
3655 The intent is to start some "lengthy" operation. The C<request> could be
3843 Whenever you want to start/stop a watcher or do other modifications to an
3991 you to use some convenience methods to start/stop watchers and also change
4055 method to set a callback before you can start the watcher.
4137 with the same arguments. Either this method or a suitable start method
4145 =item w->start ()
4150 =item w->start ([arguments])
4152 Instead of calling C<set> and C<start> methods separately, it is often
4177 Example: Define a class with two I/O and idle watchers, start the I/O
4193        io.start ();            // start it whenever convenient
4195        io2.start (fd, ev::READ); // set + start in one call
5005 exists, but it is always a good start.