02.04.2013 Views

QuickTime Kit Programming Guide - filibeto.org

QuickTime Kit Programming Guide - filibeto.org

QuickTime Kit Programming Guide - filibeto.org

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

C H A P T E R 3<br />

Extending the QT<strong>Kit</strong>Player Application<br />

9. Enter mMovieView and QTMovieView, and mMovieWindow and NSWindow in their respective fields<br />

of the Connections pane, as shown in Figure 3-9. The illustration shows the Export view object<br />

in the MovieDocument.nib window, as well as the outlet mExportAccessoryView and its<br />

destination as NSView, and the outlet mExportTypePopUpButton and its destination as<br />

NSPopUpButton. You’ll enter these in a later step.<br />

Figure 3-9 The File’s Owner connections to various outlets, with actions specified<br />

10. Select the File’s Owner icon and press the Control key. A wire appears with a small square at one<br />

end. Make sure the square lands on the File Owner’s icon. You want to hook up the File’s Owner<br />

to the QTMovieView object. Select the outlet mMovieView and click Connect to wire up the File’s<br />

Owner with the QTMovieView object, as shown in Figure 3-9.<br />

11. Repeat the same step to connect the File’s Owner icon to the NSWindow object. Choose the outlet<br />

mMovieWindow and click Connect to wire up the File’s Owner with the NSWindow object.<br />

Creating the Export View Object<br />

In this sequence of steps, you want to create an Export view object in Interface Builder, as shown in<br />

Figure 3-10. This will enable your application to display a dialog and pop-up menu when you want<br />

to export a <strong>QuickTime</strong> movie to another file type.<br />

Creating the Extended QT<strong>Kit</strong>Player Project 37<br />

2005-11-09 | © 2004, 2005 Apple Computer, Inc. All Rights Reserved.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!