• 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: Need help understanding first responder and multiple nibs
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Need help understanding first responder and multiple nibs


  • Subject: Re: Need help understanding first responder and multiple nibs
  • From: Quincey Morris <email@hidden>
  • Date: Wed, 4 Aug 2010 14:49:15 -0700

On Aug 4, 2010, at 11:02, Jason Bruce wrote:

> My app is a presentation app for presenting trial exhibits in a court room.  The
> main window of the app would consist of a tab view w/an NSTableView on one tab
> and an IKImageBrowserView on the second tab -- both bound to the same
> nsarraycontroller.  The filter window would be for each document only, and would
> be open just to create filters and then disappear.
>
> By clicking on a particular image in the image view or on a particular row in
> the table view, the user could then open a third window with a IKImageView or
> PDFView showing a particular image or pdf -- which could then be sent to an
> external display or projector.
>
> So, 1 main window per document holding an array of images, with 1 window which
> may stay open for a period of time to display an image, and another window which
> will only appear for purposes of creating filters and filter the table and then
> disappear.
>
> So, at this point, if I had two documents open, I want to see 6 windows  (3
> windows per document); not 1 filter window for all documents.

OK, that makes sense.

FWIW, I'd recommend that your image browser windows and your image display window should be document-linked windows, and that the other window should not.

Your document would initially open with its browser window in the normal way. There's actually no reason to disallow opening *multiple* image display windows for a single document, although your application may have independent reasons for limiting this to 1 image. (In that case, it's worth exploring the idea of making the image an extra pane of the browser window, rather than a separate window, but that's another discussion.) You would use 'addWindowController:' and 'removeWindowController:' to link the image window(s) to the document as discussed already.

The filter window, since it's short-lived and specific to a single document, is probably better off as a sheet rather than a separate window, for UI reasons. Aside from that, passing the document as a parameter when creating its window controller seems appropriate, and I *wouldn't* suggest linking this window controller to the document via 'addWindowController:'.


_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden

References: 
 >Need help understanding first responder and multiple nibs (From: Jason Bruce <email@hidden>)

  • Prev by Date: Re: Drag'n Drop Mail.app message to Cocoa app
  • Next by Date: Re: CoreData warning: File.children -- to-many relationship does not have an inverse:
  • Previous by thread: Need help understanding first responder and multiple nibs
  • Next by thread: Re: Need help understanding first responder and multiple nibs
  • Index(es):
    • Date
    • Thread