Re: Understanding glib events
- From: Siddu <siddu sjce gmail com>
- To: R K <cheesemilli gmail com>
- Cc: gtk-list gnome org
- Subject: Re: Understanding glib events
- Date: Sun, 18 Apr 2010 20:17:45 +0530
On Sun, Apr 18, 2010 at 7:48 PM, R K <cheesemilli gmail com>
I am trying to understand the way glib uses events when using g_main_loop_run(loop).
This is how I understand it:
g_main_loop_run() function checks regulary if there are events that
needs to be processed. The signal of an event is then executed by
executing the callback function. What I don't understand is when a new
event/callback function is executed. Is this when the first callback
function is completed and then a next event is handled? Or is this when
a event is dispatched by calling the callback function. Even when the
callback function is not completed yet, another event can already be
I expect that multiple callback functions can be handled at the same time but that only one event at at time will be dispatched.
its like the occurence of event will be followed by a look up in the table as to which all functions have been registered as callback .... all those functions will be dispatched ... and if any event occurs during the execution of these callbacks they will be queued and handled in the next turn !
Hopefully someone can clear this up for me a bit.
gtk-list mailing list
gtk-list gnome org
A little bird which escaped the nest had to fall before it learnt to fly !
] [Thread Prev