Menu vs. Window nib files
Menu vs. Window nib files
- Subject: Menu vs. Window nib files
- From: "James G. Pengra" <email@hidden>
- Date: Thu, 31 Oct 2002 16:22:54 -0800 (PST)
In document based applications the menu and window resources are put in different nib files. My Controller has Actions methods which respond to commands from both the Menus and Outlets to the window which contains an NSScrollView. What's the cleanest and most efficient way to arrange things so I can connect up these Actions and Outlets, since I can only instantiate the Controller in one nib file? Things that I've thought of, but not tried, are: 1) make 2 Controllers, 2) make a delegate controller, or 3) put all my custom resources in the Menu.nib. This must be a common situation, but I've not seen it in any sample code.
While I'm at it, is there any way to add a custom menu without dragging in one of the already-populated ones like "Application" or "Font" and deleting everything before building the new menu?
Thanks, Jim
-------------------------------------------------
This mail sent through IMP: webmail.whitman.edu
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.