Thanks for the detailed response and apologies for not mentioning my external constraints upfront.
>As stated "share an NSView between processes" it's not possible. >Even on a more abstract level, it's generally not the way things are >done. Why do you think you need/want to do this? I have a 64 bit application which needs to access a framework that only provides 32 bit binaries (http://code.google.com/p/chromiumembedded/). I'm already using distributed objects to communicate between the processes. This framework renders HTML content and the user can interact with it. The framework only gives you access to the NSView which it renders into. Since the content is rendered in the subprocess, which is hidden, I'm trying to translate the inputs I get from the parent process into the child process. I have tried to call mouseDown directly (from the child process) with no affect. Since this is the framework's implementation, I would like to avoid changing it. >As Mikevann suggested, If you really want to let a subprocess be >responsible for the content of a view in a parent process, you should >design a custom communication protocol. Use any of various IPC >mechanisms to convey status, events (custom data structures, not >NSEvent), and requests between the two processes and have the parent >process carry out the actual rendering to the view on behalf of the >subprocess. I was not clear before. I was sending the NSEvent from the child process after receiving the IPC call from the parent. _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
