Re: Writing application without Interface Builder
Re: Writing application without Interface Builder
- Subject: Re: Writing application without Interface Builder
- From: Murat Konar <email@hidden>
- Date: Mon, 17 Jul 2006 20:26:13 -0700
On Jul 17, 2006, at 7:52 PM, Patrick Hartling wrote:
[C++ based library makes it difficult to write Cocoa using
Interface builder]
I tracked down an earlier post of yours which sheds a bit more light
on what you're doing
<http://www.cocoabuilder.com/archive/message/cocoa/2006/2/6/156127>
and in which you note that
(The application object derives from a base C++ class, the
interface methods of which are invoked by the microkernel in a
spawned thread.)
and
Then, I would see what it would take
to get that to work in a spawned NSThread with no event processing
happening
in the primordial thread.
If I'm reading this right, you're hoping to run UI code (including
receiving events) in threads other than the main thread. You should
know that this unfortunately isn't supported.
It sounds like your microkernal wants to be in charge, and that what
you're trying to do is plug Cocoa into an already existing app
framework, yes? I wonder if splitting this up so that you have your C+
+ based "app" (with no visible manifestation) running in one process,
communicating with a Cocoa part that runs in another process is worth
investigating?
_murat
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden