On 5 Aug 2011, at 16:04, douglas welton wrote:
Julius,
QTMovieLayer is your friend. If you haven't already, check out the Core
Animation QuickTime Layer sample code. I think you'll find it very helpful.
regards,
douglas
Douglas hi,
thanks for the suggestion.
I'll study the code
On 06/08/2011, at 9:00 PM, julius wrote:
The need for the child window to have a minimum alpha of 0.05 in order for it
to receive mouse events has an acceptably small effect on the movie's colour.
Hey Julian, this should allow you to get rid of that 0.05 of darkness:
setIgnoresMouseEvents:
On 6 Aug 2011, at 13:23, Ron Fleckner wrote:
On 06/08/2011, at 9:00 PM, julius wrote:
The need for the child window to have a minimum alpha of 0.05 in order for
it to receive mouse events has an acceptably small effect on the movie's
colour.
Hey Julian, this should allow you to get
the convertion and memory use are
unacceptable.
The most promising suggestion I've found so far is the (undocumented)
delegate method in QTMovieView.h
- (CIImage *)view:(QTMovieView *)view willDisplayImage:(CIImage *)image
Some discussions on various forums circa 2008, suggest the method had
the movie into an image
sequence but the time required to perform the convertion and memory use are
unacceptable.
The most promising suggestion I've found so far is the (undocumented) delegate
method in QTMovieView.h
- (CIImage *)view:(QTMovieView *)view willDisplayImage:(CIImage *)image
Some
a smoother result by first converting the movie into an image
sequence but the time required to perform the convertion and memory use are
unacceptable.
The most promising suggestion I've found so far is the (undocumented)
delegate method in QTMovieView.h
- (CIImage *)view:(QTMovieView *)view
On 4 Aug 2011, at 20:25, Mike Abdullah wrote:
Have you tried putting both the movie view, and a custom overlay inside of a
layer-backed view?
The more traditional route I think is to add a child window for the overlay,
keeping its size/placement in sync with the parent window
Hi Mike
