Achim, Thanks. That¹s kind of what I expected. If you want accumulated trails to fade off, you have to find a way to keep dinging it, or else the accumulator feedback loop terminates. I still don¹t understand why there is a difference between views (all layer hosted) with stationary images. I¹ve introduced some ³dingers² to make sure they show up.
BTW, I think you guys have an excellent product with a well designed, attractive interface. One more question do you or any one else know how to embed a QT movie in a qtz file? It appears that the standard movie importer requires a separate file, which is not useful in the way we intend to incorporate it. - Gordon Apple Ed4U Little Rock, AR On 3/11/13 3:05 AM, "Achim Breidenbach" <[email protected]> wrote: > I don't know much about using QC in views, but in my experience you encounter > a performance optimization problem: The Composition is only rendered, if > anything is changed which drives the output: QC is starting at the rendering > patches (Billboard / Sprite) and check their inputs, if anything has changed. > This is done by asking the connected patches which feeding the inputs of the > rendering patches. if their inputs didn't change either, they don't get > processed. This runs recursively upwards until your published inputs "mouse x" > "mouse y", what have you. If you don't change "mouse x" or "mouse y" the > composition don't get rendered again. You see this effectt with JavaScript > patches dramatically, because they only get processed if their inputs changes. > Which makes it necessary to connect a dummy "Patch Time" patch to any input of > them if they are depending on timing. Also "Patch Time" is not the best choice > sometimes, because its time output value is driven by the enclosing view. > AFAIK you can set the rendering time to any value you want and so you can run > the timing backwards for example. You should use the "System Time" patch if > you want to make sure, that everything is rendered all the time. > > Another thing is your "first frame missing" problem: QC is performing a first > test run on the complete composition in order patches can setup things before > the actually rendering happens. This is expressed by the variable "_testMode" > in Javascript. You should test against this variable if your are running in > this first test cycle or not in JavaScript. I don't know if this happens > outside QuartzComposer Editor too, thought. Maybe you have to render the > composition twice upon first start. > > best, > > Achim Breidenbach > Boinx Software -
_______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to [email protected]
