Believe it or not, there are some things that are kind of ambiguous about your scenario and what could be causing the problem from your post/screen shot. The comment about lazy evaluation and that if your renderer/consumer patch is off, that it will stop things from updating is totally spot on. If your composition needs to keep evaluating and your main renderer is turning off, you can consider tying one of the number outputs to a 3D transform, or a billboard with no image input.
Backing off a bit... why is there conversion going on after the first conversion? (note attachment). Notice how in the example, if you keep a multiplexer on virtual it converts the boolean input works fine, and is converted to numeric on the output of the multiplexer. So even though there is conversion going on in the second "chain", it still works fine. Without seeing your exact scenario it's a bit hard to say what the problem is. On a side note, I strongly disagree that connections severing when changing type is a bug. I think that's extremely functional (... it can be irritating, but I think it's the "right" thing to have happen). -George Toledo On Fri, Jun 26, 2009 at 1:42 AM, Alastair Leith <[email protected]>wrote: > I've got issues with a patch where Boolean values can be processed thru a > chain of patches okay but when the value *type is changed to* *any other > type (say number) and then back to Boolean it will not work.* > > I have the strange result of a True value on one side of an Input Splitter > Patch and a False value on the output node. I've noticed this can occur at > various points down the line of patches where it is true in on a splitter > and false out. > > I'm working on a macro that can process any kind of value (virtual) like > image, number, QCstrucutre and so on. The values pass through the macro to > output un-changed but can be recorded sent or substituted in various ways. > All the values types work fine except Boolean. > > I remember cwright posting @Kineme there is an issue in QC with the way > Boolean are treated re: something else entirely, just wondering if there is > a know issue causing this mal-functioning and if there's a known ways around > it. > > _______________________________________________ > 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.com > > This email sent to [email protected] >
conversion.qtz
Description: Binary data
_______________________________________________ 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]
