I'm known to have pointed the finger at QCs JS patch a few times on this list and said it has gone whacko on me while editing code in the Editor. It's very hard to actually demonstrate this reliably but this time I've managed to save a composition with the JS patch playing up. Even after a QC restart which often fixes glitches. In this code I assigned a default value of 99 to output variable called Item and JS refused to output the default. I tried changing the output variable name and various other desperate maddening ploys. Finally I created a second output variable Out — this time of a number type not Index and patched it to display on screen. That seemed to have the illogical effect of making the initial variable Item finally output it's default value Anyhow here's the composition. Proof until unproven that JS in QC is unreliable at live code editing at least. I've experienced all sorts of these kinds of subtle bugs in QC JS patch and certain list members have called user error, hopefully they can see it for themselves with this comp — shivers, I hope it's not user error in this case… Comp is very simple but is Syphon Plugin dependant, sorry for that I wasn't planning a one hours debug session and posting to list when I started it. |
Syphon Client copy.qtz
Description: application/quartzcomposer
While JS related crashes are often reported on this list for QC based video production applications, I'm not aware of having any so far, although I have a the scars to indicate a gallizion JS related crashes in QC Editor. What are the tell tale signs of a JS caused Crash in the stack trace, JS patch up high on list?
|
_______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list (Quartzcomposer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
