Message: 6
Date: Mon, 25 Jul 2005 10:25:58 +0000
From: "Roger Bolton" <email@hidden>
Subject: feature requests re bindings and multiple views
To: Pierre-Olivier Latour <email@hidden>, Roger Bolton
<email@hidden>, quartzcomposer-dev
<email@hidden>
Message-ID: <email@hidden>
Content-Type: text/plain; charset=iso-8859-1
nope - only proper way to render a composition into multiple screens
at once is to render it in an OpenGL pBuffer, then create a texture
from that pBuffer, and draw it whereever you want - here's a starting
point:
http://developer.apple.com/samplecode/QuartzComposerTexture/
QuartzComposerTexture.html
Apologies, I realised that you had answered this already when I looked
back through the list.
There are many things "almost but not quite possible" for those of
us a
bit lacking in objective c / cocoa coding skills.
These feature requests would make many more things possible with just
Quartz Composer and interface builder.
a) a QCImageView viewing area in interface builder that works like an
NSImageView but draws the texture from the graphics cards and can be
bound to a published image output from a QCView or QCPatchController.
b) multiple quartz compositions talking to each other.Eg publish an
input from one comp and have it bound in Interface Builder to a
published input in a second comp. To keep it simple at first you could
restrict it so that there is a "one way street" QC comps that accept
data from other QC comps could be restricted from publishing outputs.
so we could have one "master composition" that sends images and
data to
slave comps.
c) two way binding of controls. updates whenever the last one
changes.
so an NSSlider can be bound to midi inside a QC comp and the slider
moves with the mouse or midi, should jump to last changed position if
the two are different.
d) binding one interface builder control to send to multiple QC comps.
I can't see at the moment a way of having one text box send a path to
two QCPatch controllers. eg a text box goes to the path for an "image
with movie" in two QC comps that are running independently.
I call these the "idiot VJ doesn't have time to learn objective c /
cocoa" features.
Roger
Eskatonia Visuals
