Hi,
I am in a case where I have no access to the main thread since I am making a
plugin which consists of a dynamic library loaded by a third party program.
This third party program has nothing to deal with Cocoa and only uses
standard C API. And it has it's own main loop.
In the plugin I create
>
> On Jul 8, 2009, at 4:34 AM, Julien Isorce wrote:
>
> Any kind of comment or suggestion would be appreciated.
>>
>
> I can see you are just beginning to discover multi-threading.
>
> You need to break in gdb and backtrace all of the thread stacks. That will
> t
well ok,
In GNUstep it's possible to decide which pthread is the "main thread".
I mean the first pthread which call GSRegisterCurrentThread, is the main
thread.
And then the NSApp must be init and run in this main thread, as it's
required on MacOSX.
Is it possible to change the "main thread" as f
Hi,
First, thx for your reply.
2009/7/10 Scott Thompson
>
> On Jul 10, 2009, at 3:40 PM, Julien Isorce wrote:
>
> In GNUstep it's possible to decide which pthread is the "main thread".
>> I mean the first pthread which call GSRegisterCurrentThread, is the m
2009/7/11 Mike Abdullah
>
> On 11 Jul 2009, at 00:33, Julien Isorce wrote:
>
> Hi,
>>
>> First, thx for your reply.
>>
>> 2009/7/10 Scott Thompson
>>
>>
>>> On Jul 10, 2009, at 3:40 PM, Julien Isorce wrote:
>>>
>&g
that the NSRunLoop could/should
get the ability to perform/handle the events that the NSApp is the only one
able to do.
Anyway, thx for all your answers/advises
Julien
2009/7/11 Stephen J. Butler
> On Fri, Jul 10, 2009 at 6:50 PM, Julien Isorce
> wrote:
> > you are enterely righ
