I started to apply the technique from the now withdrawn QA1061 and
it appears that it's grabbing the same events. Just like in the
example I'd want to start and stop the event loop but instead of
Carbon RAEL, maybe the methods 'run', and 'stop' from
NSApplication. Do you think that would be viable? Or am I barking
up the wrong tree? I'm willing to do a lot so I can take advantage
of the much more elegant Carbon implementation.
MattD sent me a copy of this Q&A and I see it's referring to using
cooperative threads with RAEL. Unfortunately I'm not sure I can
comment with any authority about using this technique with Cocoa,
since I'm not really familiar with the details of how NSApplication
runs its event loop or whether the run and stop messages would give
the right results. Just offhand, I think you'd need to translate
the ReceiveNextEvent call into a call to [NSApplication
I'll read up on nextEventMatchingMask. What I want to do is have the
master controller be in Carbon and then parcel out the events as I
see fit. So of course my analogy is from Carbon thinking and the
NSApplication run and stop methods might not be applicable.
If I'm not mistaken, the 'cgs ' events from ReceiveNextEvent() are
the lowest normally seen at this level and bounced back into higher
calls when not handled, and they should be translatable into an NSEvent.
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden