Hello
After playing with these two objects showing a friend some QC stuff, I
see they are kind of lacking in certain ways. If you want the ease of
use (drag and drop in IB), but want to do a bit more advanced stuff,
they really get in your way.
I suggest they :
QCView:
Have an accessor for the running QCRenderer, because, it seems like
if you are using a QCPatchController, and you bind the QCViews patch
(patch!? is this Max/MSP?), it renders the 'loadedCompositon' accessor
null. Not helpful!
Have a notification for when it will begin to render a frame.
Have a notification for when its finished rendering a frame.
QCPatchController
Why on earth is it called that? (actually I know why but its a really
odd name and binding path)
The object is completely opaque, open it up a bit so we can get to
its internals.
I am aware that one should be using KVO via the QCPatchController to
make it useful, but it would be nice to be able to directly query it
for the patches state, or what not, at least with QCView, that would
be immensely helpful to get notification and a QCRenderer*
No idea if things change in 10.6, but, I hope they do. Any thoughts on
this from the list before I submit a feature request (which is late
int he game since 10.6 is around the corner but..... )?
Thanks!
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com
This email sent to [email protected]
