WWW-www.enlightenment.org pushed a commit to branch master.
http://git.enlightenment.org/website/www-content.git/commit/?id=aee1bab093d4c8ae28618c460f2dcff90a6f478a
commit aee1bab093d4c8ae28618c460f2dcff90a6f478a
Author: Raster <ras...@rasterman.com>
Date: Mon Apr 27 23:35:55 2015 -0700
Wiki page mainloop changed with summary [] by Raster
---
pages/docs/efl/mainloop.txt | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/pages/docs/efl/mainloop.txt b/pages/docs/efl/mainloop.txt
index e7009cf..8c64e75 100644
--- a/pages/docs/efl/mainloop.txt
+++ b/pages/docs/efl/mainloop.txt
@@ -16,9 +16,9 @@ The mainloop will sit and iterate forever until something
flags it to stop. This
|**[[#Wake Up]]** | This is a special timepoint and it is stored and can be
retrieved with ecore_loop_time_get() | |
|**[[#Idle Exit]]** |Coming out of the idle state due to a timeout or I/O
event |[[ecore_idle_exiters]] all called here, if registered|
|**[[#FD Event handling]]** |File Descriptors (fd's) are processed here (read
from or written to) and events queued |[[ecore_fd_handlers]] callbacks called
here (read, write, buffer) |
-|**[[#Event filtering]]** |Filter out events we don't want now that we have
gathered all pending I/O | [[ecore_event_filters]] callbacks called here |
-|**[[#Event handling]]** |Regular event handling (in order) and events may
still be generated and added to the queue as a result of event handling via
ecore_event_add() or ecore_job_add() for example |[[ecore_event_handlers]]
callbacks called here as well as [[ecore_timers]] callbacks,
[[ecore_animators]] callbacks for animation, [[ecore_jobs]] callbacks, and
almost all the UI callbacks (such as mouse click events, enter/leave, key
events, other widget changes etc.) |
-|**[[#Entering idle]]** |The mainloop is about to go idle again now that
everything has been processed | [[ecore_idle_enterers]] are called here (the
first of which may be the [[evas_rendering]] related callbacks which will
calculate widget and object changes, actually trigger rendering etc., depending
on the order of idlers added via ecore_idle_enterer_add() to the end of the
idle enterer queue or ecore_idle_enterer_before_add() which adds to the start
of the idle enterer queue |
+|**[[#Event Filtering]]** |Filter out events we don't want now that we have
gathered all pending I/O | [[ecore_event_filters]] callbacks called here |
+|**[[#Event Handling]]** |Regular event handling (in order) and events may
still be generated and added to the queue as a result of event handling via
ecore_event_add() or ecore_job_add() for example |[[ecore_event_handlers]]
callbacks called here as well as [[ecore_timers]] callbacks,
[[ecore_animators]] callbacks for animation, [[ecore_jobs]] callbacks, and
almost all the UI callbacks (such as mouse click events, enter/leave, key
events, other widget changes etc.) |
+|**[[#Entering Idle]]** |The mainloop is about to go idle again now that
everything has been processed | [[ecore_idle_enterers]] are called here (the
first of which may be the [[evas_rendering]] related callbacks which will
calculate widget and object changes, actually trigger rendering etc., depending
on the order of idlers added via ecore_idle_enterer_add() to the end of the
idle enterer queue or ecore_idle_enterer_before_add() which adds to the start
of the idle enterer queue |
|REPEAT |Go back to the top of this table and repeat | |
== Idle ==
--
