Okay, pretty sure I figured out the virtual macro issue.

I was trying to make a simple A/B image switcher with a multiplexer.
(Two things I was wondering about as I went along -- could it cause problems
using the forward slash -- "A/B" -- in the published port name, and/or using
a boolean input for the multiplexer index?)

When adding the macro to the library it would not show up right away so I
would then save the .qtz, then import the virtual macro .qtz. When I did it
this way the macro would show up in the library, but loading it to the
editor would crash QC consistently. This apparently caused the infinite
recursion?

Solution: if I only use Add To Library then close and reopen QC, it works as
expected.

Is this still a bug I should report?



On 2/20/10 10:52 PM, "Christopher Wright" <[email protected]> wrote:

>> The crash logs reflect the buggy behavior.
>> The "Preset Parameter" .qtz, when converted to a virtual macro and
>> added to
>> the library, will load to a comp but will not show up in a macro.
>> The "A-B Image" crashed QC trying to load it from the library. It's
>> the most
>> recent crash log.
> 
> 
> (ps) -- the crashes in question look like they happen due to infinite
> recursion (the address it segfaults on is 0xbf7ff__ is just past the
> end of the default 8MB stack, growing down from 0xC0000000) [this
> isn't intended to mean anything to normal humans, btw] -- I'm going to
> bet that your macros are referencing themselves through some weird
> loop, perhaps due to the Import Virtual Macros step (that shouldn't be
> necessary -- adding to library _should_ make stuff appear immediately
> in the patch library)?
> 
> --
> [ christopher wright ]
> [email protected]
> http://kineme.net/
> 
> 


 _______________________________________________
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