Thanks, George, I thought it was related to that but you turned my ³I think
this might be happening² to ³this is happening². And the patent stuff -- I
wouldn¹t have thought to go dig up that info. Very good, I¹ll have a peek.

Jerry


On 11/6/10 2:44 PM, "George Toledo" <[email protected]> wrote:

> 
> 
> On Sat, Nov 6, 2010 at 5:19 PM, Jerry Smith <[email protected]> wrote:
>> Maybe this is an issue I don't get re: pulling / pushing the processing
>> chain, but in this test comp why does the first multiplexer index not switch
>> after first mouse click whereas the second one works as I would expect? And
>> how can i get the first to behave like the second?
>> 
> 
> I'm not 100% sure how to answer your question, but I can describe what is
> happening in your composition.
> 
> When the composition first open, all input values are 0. When you hit Left
> Button, you're changing index values on both multiplexers simultaneously. 
> 
> After you hit Left Button once, you will see that the Number Multiplexer that
> outputs to the secondary Number Multiplexer still has an Index Value of 1.
> This is because when you released the Left Button, the Source Index on the
> Number Multiplexer that is directly connected to the Clear shifts to 0. This
> effectively stops evaluation for that portion of the chain, since the Clear
> isn't making any calls upstream to make that update, because Index is now 0 on
> the Number Multiplexer directly attached. So, no calls can be made to it
> anymore to update the ports to 0.
> 
> If you want to force evaluation on that part of the chain, you can connect it
> to a Renderer directly, as in the attachment, so that whether or not the Left
> Button is up or down, there's a Consumer/Render patch that "needs" it's value
> to "do something".
> 
> Hope that makes sense. You know, you can actually do a search for the patents
> on QC, and it's pretty informative on how it works as far as really
> conceptualizing what's going on, if you're the type that doesn't mind reading
> those things.
> 
> -GT
> 
> 
>> 
>>  _______________________________________________
>> 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/gtoledo3%40gmail.co>>
m
>> 
>> This email sent to [email protected]
> 
> 

 _______________________________________________
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]

Reply via email to