• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Good ol' modal dialogs
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Good ol' modal dialogs


  • Subject: Re: Good ol' modal dialogs
  • From: Marco Binder <email@hidden>
  • Date: Wed, 6 Nov 2002 00:37:06 +0100

I dont see why it s neccessary to create a new nib-file for each dialog. If the dialogs are likely to be used, it should sufficient to just design them in you MainMenu nib or wathever nib you like best (that contains your app-controller). Then, upon receiving the action-message from the menu-command, you just orderFrontAndMakeKey your appropriate "dialog" or run it as a modal sheet, just as you desire. In your nib, you connect the controls to the controller object you like to handle that stuff.

I d say thats the easiest way to do it and it works nicely. Just if the "dialogs" are very complex and not likely to be shown everytime u run the app, you might be better off, speed- and memorywise, putting them into a seperate nib.

marco


Am Mittwoch, 06.11.02 um 00:14 Uhr schrieb Charles Srstka:

You need to make a .nib file containing the window and controls. It's not that hard.

BTW, are you sure these windows really need to be modal?

Charles

On Tuesday, November 5, 2002, at 10:46 AM, Steve Mills wrote:

One thing that seems to be lacking (or I just haven't seen it) in the AppKit examples is modal dialogs used to get information from the user. Most examples just put the controls right in the main window, or they use an NSPanel only to display info to the user.

The app I'm working on will have a bunch of menu items that the user can use to apply different changes to the data. Each menu item needs its own dialog with various controls (like edit text fields) or custom views that the user can perform graphical manipulations.

From what I've gathered so far, it looks like each dialog needs its own .nib that will load as a result of choosing the matching menu item, and a special subclass of NSObject to load the .nib, run the dialog, and handle actions in the controls.

Is this really the easiest way to display modal dialogs? Using a palette or drawer in this case is wrong. Would I be better off just using Carbon to display and handle all the modal dialogs?

Steve Mills
Drummer, Mac geek
http://sjmills5.home.mchsi.com/
_______________________________________________
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.
_______________________________________________
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.


--
|\ /| E-Mail: email@hidden WWW: www.marco-binder.de
| \/ | Telefon: 07531 / 94 19 94 Fax: 07531 / 94 19 92
| |ARCO Snail-Mail: Banater Str. 3 - 78467 Konstanz
BINDER _____________________________________________________
_______________________________________________
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.

References: 
 >Re: Good ol' modal dialogs (From: Charles Srstka <email@hidden>)

  • Prev by Date: NSTextField and Formatters
  • Next by Date: Re: redirect stderr
  • Previous by thread: Re: Good ol' modal dialogs
  • Next by thread: Syntax highlighting
  • Index(es):
    • Date
    • Thread