> If you're seeing weirdness in one composition but not the same behaviour in > another that you freshly create then it sounds like a condition of the QTZ > being corrupt/saved in an inconsistent state. I've seen this happen > especially when the clipboard use/plugins are involved. > This is far from helpful but I've had a massive, complex composition go bad > after making a slight change. The only way I found to fix it was to go back > to an earlier version from backups and recreate the changes from scratch. > Second time round no problems. > Ps. Check out creativecommons.org/license
Awhile ago I was also dealing with a corrupt composition which consistently resulted in QC crashing every time I opened the project. I found that manually editing the XML fixed the issue. It was pretty tedious and took some trial and error, but I eventually pinpointed the offending code and massaged it until the project would open the in QC. (It was a divide-by-zero exception being thrown in QC in a JS patch, IIRC.) So yeah, haven't really been following this thread but perhaps that helps. David _______________________________________________ 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]
