Archived QTMovieViews on 64-bit?

  • Short question: How do I get a 64-bit application to load an Interface
    Builder nib that has a QTMovieView object in it?

    Long question: I've been experimenting with QTKit and 64-bit. I have a
    nib that has a QTMovieView that loads correctly when the application
    is run as a 32-bit app, but when it is run as a 64-bit app, then while
    the nib is being decoded, the following exception is raised:

    *** -[NSKeyedUnarchiver decodeObjectForKey:]: cannot decode object of
    class (QTMovieContentView)

    I'm guessing QTMovieContentView is a 32-bit-only object, but I can't
    tell for sure since it appears to be private. How can I work around
    this and get the 64-bit application to just load the nib?

    Nick Zitzmann
    <http://www.chronosnet.com/>
  • On Nov 26, 2007, at 6:01 PM, Nick Zitzmann wrote:

    > Short question: How do I get a 64-bit application to load an
    > Interface Builder nib that has a QTMovieView object in it?
    >
    > Long question: I've been experimenting with QTKit and 64-bit. I have
    > a nib that has a QTMovieView that loads correctly when the
    > application is run as a 32-bit app, but when it is run as a 64-bit
    > app, then while the nib is being decoded, the following exception is
    > raised:
    >
    > *** -[NSKeyedUnarchiver decodeObjectForKey:]: cannot decode object
    > of class (QTMovieContentView)
    >
    > I'm guessing QTMovieContentView is a 32-bit-only object, but I can't
    > tell for sure since it appears to be private. How can I work around
    > this and get the 64-bit application to just load the nib?

    That sounds like a bug. I would file a bug report with Apple about.

    -Shawn
  • On Nov 26, 2007, at 10:08 PM, Nick Zitzmann wrote:

    > Long question: I've been experimenting with QTKit and 64-bit. I have a
    > nib that has a QTMovieView that loads correctly when the application
    > is run as a 32-bit app, but when it is run as a 64-bit app, then while
    > the nib is being decoded, the following exception is raised:
    >
    > *** -[NSKeyedUnarchiver decodeObjectForKey:]: cannot decode object of
    > class (QTMovieContentView)

    I think you can prevent this from happening by removing the
    QTMovieView object from your nib file and then adding it back in and
    restoring any connections it has to other objects in the nib. Your
    description leads me to believe that the nib file is fairly old.

    If this does *not* work, let us know.

    Tim Monroe
    QuickTime Engineering
  • On Nov 27, 2007, at 10:11 AM, Tim Monroe wrote:

    > I think you can prevent this from happening by removing the
    > QTMovieView object from your nib file and then adding it back in and
    > restoring any connections it has to other objects in the nib. Your
    > description leads me to believe that the nib file is fairly old.
    >
    > If this does *not* work, let us know.

    I'm installing Xcode 2.5 right now to test the hypothesis, which is
    the problem occurs with QTMovieView objects instantiated by the QTKit
    palette in IB 2. I tried it with a QTMovieView instantiated using IB
    3, and the problem did not occur (although I did run into one other
    problem; see bug #5616126).

    Nick Zitzmann
    <http://www.chronosnet.com/>
  • On Nov 27, 2007, at 3:48 PM, Nick Zitzmann wrote:

    > I'm installing Xcode 2.5 right now to test the hypothesis, which is
    > the problem occurs with QTMovieView objects instantiated by the
    > QTKit palette in IB 2.

    My hypothesis was wrong; it must have been instantiated with a really
    ancient QTKit palette. Anyway, now I know I have a workaround (just
    delete and re-create the instance), and I have bug #5616235 filed on
    the incident.

    Nick Zitzmann
    <http://www.chronosnet.com/>
  • On Nov 27, 2007, at 3:21 PM, Nick Zitzmann wrote:

    >
    > On Nov 27, 2007, at 3:48 PM, Nick Zitzmann wrote:
    >
    >> I'm installing Xcode 2.5 right now to test the hypothesis, which
    >> is the problem occurs with QTMovieView objects instantiated by the
    >> QTKit palette in IB 2.
    >
    >
    > My hypothesis was wrong; it must have been instantiated with a
    > really ancient QTKit palette. Anyway, now I know I have a
    > workaround (just delete and re-create the instance), and I have bug
    > #5616235 filed on the incident.

    The relevant vintage is that of the QTKit framework, which does
    archiving and unarchiving. We made some changes with respect to
    archiving the subviews of QTMovieView that were not in earlier QTKit
    frameworks. Glad to hear that the workaround was operative, which
    confirms my diagnosis.

    Tim Monroe
    QuickTime Engineering
previous month november 2007 next month
MTWTFSS
      1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30    
Go to today