• 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: QTKit: hum, is it a bug?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: QTKit: hum, is it a bug?


  • Subject: Re: QTKit: hum, is it a bug?
  • From: Tim Monroe <email@hidden>
  • Date: Mon, 14 Nov 2005 09:46:59 -0800


On Nov 14, 2005, at 7:58 AM, Stéphane Sudre wrote:

I've been playing a bit with the QTKit today updating a project which
was using NSMovieView till now.

While the API is better, I am seeing some things I would tend to
believe are bugs.

1. If you set the frame of the QTMovieView and then the movie for this
same view, the first frames of the animation are out of bounds.

Basically the code is:

[myMovieView setFrame:someFrame];
[myMovieView setMovie:myMovie];

Well when you call play:, the movie is drawn outside the bounds of the
QTMovieView. The fact is that the movie frame is bigger than the view
frame.

The only way I've found to fix this problem is to set the
QTMovieCurrentSizeAttribute attribute before adding the movie to the
movieView and calling play:.

Am I missing something or is this a bug?

It's probably a bug; I will file a bug report. Looks like you have a workaround until we sort this out, right?


2. It looks like the QTMovieDidEndNotification is not very bullet
proof. When you change the movie of the QTMovieView in the
QTMovieDidEndNotification callback, you just crash. I didn't see any
warning against this in the "documentation" so I tend to believe this
is a bug.

You raise a good point. Many of the QTMovie notifications are posted from within a QuickTime callback where it is unsafe to destroy the associated QuickTime Movie or MovieController. This means that in general you should not release a QTMovie object directly or indirectly in a notification callback (that is, by calling [QTMovie release] or [QTMovieView setMovie:] with a different QTMovie object).


I need to investigate this issue a bit more. Either QTKit should be able to work around the problem, or the documentation needs to include a warning. In the meantime, I think you need to defer calling setMovie: until you have exited the notification callback. Sorry for the hassle.

Tim Monroe
QuickTime Engineering _______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: QTKit: hum, is it a bug?
      • From: Stéphane Sudre <email@hidden>
  • Prev by Date: Re: NSTextViewCell
  • Next by Date: Re: Where do asynchronous API do their "work"?
  • Previous by thread: QTKit: hum, is it a bug?
  • Next by thread: Re: QTKit: hum, is it a bug?
  • Index(es):
    • Date
    • Thread