Re: [Pythonmac-SIG] NSMovieView question

2005-07-01 Thread Jared Barden
Is that framework accessible from PyObjc? I forgot to mention previously that was the language I was using. Thanks for the input. Jared On Jun 30, 2005, at 4:01 PM, Dethe Elza wrote: > You can't really do that using NSMovieView without dropping down to > the C-level Quicktime routines (mayb

Re: [Pythonmac-SIG] NSMovieView question

2005-07-01 Thread Bob Ippolito
Yes, if you're using the latest PyObjC for Mac OS X 10.4. -bob On Jul 1, 2005, at 3:06 AM, Jared Barden wrote: > Is that framework accessible from PyObjc? I forgot to mention > previously that was the language I was using. > > Thanks for the input. > > Jared > > On Jun 30, 2005, at 4:01 PM, Deth

Re: [Pythonmac-SIG] NSMovieView question

2005-07-01 Thread Jared Barden
I appreciate all the QTMovieView help. Hopefully this will be the last question on the subject. In my app, I create a QTMovie with the initWithURL_error_() call. When I try to do a setMovie_() with the QTMovieView, I receive the following error: ValueError: NSInvalidArgumentException - *** -

Re: [Pythonmac-SIG] NSMovieView question

2005-07-01 Thread Jared Barden
Disregard that last e-mail. I figured it out. Jared On Jul 1, 2005, at 3:14 PM, Jared Barden wrote: > I appreciate all the QTMovieView help. Hopefully this will be the > last question on the subject. In my app, I create a QTMovie with the > initWithURL_error_() call. When I try to do a setMovie_(

Re: [Pythonmac-SIG] NSMovieView question

2005-07-01 Thread Bob Ippolito
On Jul 1, 2005, at 9:14 AM, Jared Barden wrote: > I appreciate all the QTMovieView help. Hopefully this will be the > last question on the subject. In my app, I create a QTMovie with > the initWithURL_error_() call. When I try to do a setMovie_() with > the QTMovieView, I receive the follow

Re: [Pythonmac-SIG] NSMovieView question

2005-07-01 Thread Steve Spicklemire
Beware.. initWithURL_error_() returns a tuple.. the first element of the tuple is the QTMovie, the second is (presumably) the error. I think it's because python has no concept of a 'pointer to memory', so rather than pass in a pointer, you get a 'tuple' return value. -steve On Jul 1, 2005,