Hal, The controller instance is created by the IB. All I wanted to do is to be able to call accessor methods on the controller (from other classes) to manipulate the GUI (encapsulate the GUI stuff). I thought that this would be a normal thing to do, but I guess not. I kinda think wiring sockets all over the place is messy at best. I am new to Cocoa, and I am trying to start out on the right paths with my projects. Matt
Make sure you understand nil-targeted actions/File's Owner/responder chain. That idiom might or might not be useful in this case. I can picture sending various messages to nil that only the POSSocket class will respond to, and have the POSSocket instance be the delegate of your controller. How is the controller being created? Right after creation might be the time to tell it about objects it needs to know about. Hal _______________________________________________ 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 [EMAIL PROTECTED]
