On Thu, Jul 9, 2009 at 6:09 PM, Scott Thompson<ea...@mac.com> wrote: > To empasize this point. Consider, for example, the method > performSelectorOnMainThread:. We use this API in several place to ensure > that functionality is performed on the same thread that is processing user > events. If code were able to change the thread responsible for handling > events willy-nilly, that kind of functionality would break badly.
... or two plugins both trying this hack, and claiming their thread as the main thread. I sympathize with what you're trying to do, Julien, but it's simply not going to work. Personally, I'd write a full fledged helper app in Cocoa, maybe marking it as a background app (so it doesn't appear in the Dock), and then communicate with it in my plugin. There are many ways to do this: unix sockets, mach ports, distributed objects, shared memory, etc, etc. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
