On Jun 6, 2010, at 22:59:08, Christopher Wright wrote: > (multi-email address smokescreen! ;) > >> Ah, pity. Bug #8066531 (I wrote it as a bug, and went back to change it to >> enhancement request, but couldn't) > > This is unlikely to work as well as you'd like -- if your patch is inside a > macro, it'll just publish ports to the macro's level, and a host application > will not see them. You might be better off with a structure input, if > possible -- that will allow arbitrary arrays/dictionaries of data to get > piped in without needing individual ports (that won't work so well with the > parameters controllers, sadly, but you could isolate the port you're > interested in, and make a custom control for it on the application's side -- > tedious, but better than nothing).
That's probably better, anyway. I'm realizing that ideally, my patch would simply have multiple outputs, one for each data channel, but then there'd be no way to dynamically make all the rendering patches in the encompassing composition. > I know your user/use-case is rather technical and special, so the need for > generic "works in all kinds of bizarre ways" reasons sound lame and useless. > However, designing new parts must take such things into consideration (for > better or worse), otherwise it just gets confusing for everyone. I fully understand. It seems, at first blush, that it should be doable in a generic way. Perhaps not. > Don't worry about the classification, we'll be able to re-class it as > necessary. Thanks much for filing the bug/feature request! I've been slowly coming to the realization that I don't think QC is going to be much help here, and that I'd be better off just rendering the overlay directly, and foregoing using QC to do it. Alternatively, I can create lots of little compositions, for various types of elements being displayed, and go that route. Complicates things, though. -- RIck _______________________________________________ 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]
