That was the trick. Now I have much of the program reworked. Thank you.
But several more questions...
The QCView does not have an image of interest. Is there an optimal
placement/setting for the view if I am not interested in the patch's
primary output?
The NSImageViews have to receive an explicit setNeedsDisplay to get
them to update on significant events. Is there a better way to get
the ImageViews updated?
The primary significant event is the motion of a slider (thank you
Roger for pointing out how to scrub a movie)? I have the slider both
bound to the patch and connected to a controller (sends the
setNeedsDisplay).
When I import an jpg for the movie, sometimes, the image is scanned
incorrectly (defining rectangle not correct). The particular image is
not altered by the patch's logic. What would be causing this?
When a user selects a QT compatible file, I set the QCView's input
port for the movie path. I have an option for the user to simply set
a channel to no-movie. [view setValue:@"" forInputKey:@"Movie_Path"]
does not purge the movie from the patch. How do I get the patch to
forget a movie?
If two channels point to the same movie, I am finding the same Patch
Time value is putting the instances on two different (although
nearby) frames. Why would a single patch time select different frames
on two instances of a single movie?
Cheers,
Dave
On Nov 29, 2005, at 3:47 PM, Pierre-Olivier Latour wrote:
Despite what I had typed, the full path is
Bind To: QCPatchController
Controller Key: patch
Model Key Path: Output.value
I am still not seeing an image. Here are the points that I know to
verify.
Loading the .qtz file in Composer yields an image in the tool-tip
over the correctly keyed published out port "Output". The
QCPatchController instance is loaded with the correct qtz file.
The NSImageView is enabled, visible, and frame==layout.
Alignment is fully centered with scaling to fit.
What should a check next?
You need to have a QCView connected to the controller and that is
rendering
