Just as a developer and an end user, I really frown upon using view
controllers for custom QC patches. The reason is simple as this:
you cannot publish controls exposed in the view controller to the host
app since they have no outlets or inlets, nor can you publish the view
itself to the host app*
In short, if your patch has controls, please make them standard input
ports, so they can be used with 3rd party Quartz friendly apps by
other devs.
Just saying :). Why not make your controls parameters?
*(this is actually a pending feature request of mine, and i think
would be awesome. Being able to get an NSView object from a plugin and
being able to drop it into a nice designed UI would be really cool,
especially for patches like interpolate and timeline with interesting
parameters.).
On Oct 22, 2009, at 5:31 PM, Milton Aupperle wrote:
So we have a catch 22 situation here. The device doesn't get
accessed from the -createViewController until the -startExecution
method gets called because it hasn't been opened yet and -
createViewController is already allocated by the plugin so it's all
set to fail!. And if device is released in the -stopExecution call,
then it once again can not be accessed at all in -
createViewController. This is just a very poor user experience - I
expect Apple to be better than this kludge!
_______________________________________________
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]
