Quartz Composer not being cached somewhere?

• Subject: Quartz Composer not being cached somewhere?
• From: <email@hidden>
• Date: Mon, 11 Feb 2008 21:35:25 +0000
• Delivered-to: email@hidden
• Delivered-to: email@hidden
• User-agent: Plasq Webmail/0.1

(Resending this as I posted before confirmation from the list came through, sorry if it comes through twice!)

We're trying to tweak a Quartz composition to fix some drawing errors
it has. Back in tiger we could change the QC in the app resources to
incrementally change the QC, but now that doesn't work. Is the QC
being saved somewhere else? If so how can we force the app to reload
the QC each time?
Even with a clean builds of the app with the QC in the resources, we
have the same problem. What's going on?

- Mathieu Tozer
plasq

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/email@hidden

This email sent to email@hidden

• Follow-Ups:
  • Re: Quartz Composer not being cached somewhere?
    • From: Troy Koelling <email@hidden>

• Prev by Date: Re: Virtual ports in Quartz Composer plug-ins
• Next by Date: Re: Quartz Composer not being cached somewhere?
• Previous by thread: Re: Virtual ports in Quartz Composer plug-ins
• Next by thread: Re: Quartz Composer not being cached somewhere?
• Index(es):
  • Date
  • Thread