Tristan Van Berkom wrote:
> On Thu, 2007-10-04 at 00:12 +0200, Christian Buennig wrote:
> [...]
>> However, that does not matter any more. As suggested by you and jcupitt
>> I'll avoid to autonomously run a main loop within the library.
>
> Note that in some con
Donny Viszneki wrote:
> Oh, I forgot this part:
>
> On 10/3/07, Christian Buennig <[EMAIL PROTECTED]> wrote:
>> Of course they could tell the
>> library somehow if there already is a running main loop in the default
>> context, but it would be nice if the
context) or to let the library do this. Of course they could tell the
library somehow if there already is a running main loop in the default
context, but it would be nice if the library could detect this itself.
[EMAIL PROTECTED] wrote:
> On 10/2/07, Christian Buennig <[EMAIL PROTECTED]&
Hi,
thanks for the hints, however, some more questions below..
Donny Viszneki wrote:
> I'm a bit of a newb to this, so others should feel free to correct me.
>
> On 10/2/07, Christian Buennig <[EMAIL PROTECTED]> wrote:
>> Hi,
>>
>> I have a general question
Hi,
I have a general question about the concepts of GLib main loops.
I've read the GLib reference several times but still I don't get how
main loops internally work. To be precisely, the following questions occur:
* Do main loops exist per process or per thread?
If I start a main loop in one t
