Why don't you try going into each Graphics folder (system, library, and user... whichever/do or do not exist), and systematically erase any copies of your plugin (you indicate attempting this already, but check each of these three locations again, as they are the only locations QC will load plugins from).
Do this until the patch from your plugin doesn't restore in the qtz that it reads like you are attempting to open up *at all.* Another aspect of this is that if you have QC running and you are "switching" out plugins from your builds, automatically, it *doesn't change the plugin that loaded when you opened QC.* QC will run with whatever patch the plugin you made was when you opened up QC. In order to get the patcherator/patch creator/patch library/whatever they are calling it, to load your new version, you have to manually close and restart QC. It reads as if that may be happening to you. Unless I'm unaware of something, you should be able to use Debug builds with no problem. Try debug build and manual placement of the plugin (?), making sure to restart QC each time. Best, George Toledo On Tue, Apr 27, 2010 at 12:12 AM, Rick Mann <[email protected]> wrote: > > On Apr 26, 2010, at 20:44:37, vade wrote: > > > Are you making sure your plugin is compiling in both 32 and 64 bit? I've > seen XCode launch QC with a different architecture than what is selected in > the XCode get pulldown, vs what is selected in the get info pane on QCs app. > > > > Also, are you using any frameworks in your QCPlugin that use @rpath > linker? I've also seen instances where XCode will load libraries that may > not load when you launch the app, do you get any other errors in the log > window, or in Console.app (Applications/Utilities/Console.app). > > Good suggestions, but I don't think that's it. Both Debug and Release > configs are 64/32-bit universal, and in any case, I'm running the Debug > build for both. > > I don't have any private frameworks. > > > > > > > > > On Apr 26, 2010, at 11:26 PM, Rick Mann wrote: > > > >> I'm trying to verify that my QC custom patch runs correctly when > launching QC directly, rather than as a result of "Debug" from within my > patch's Xcode project. When I Debug, everything is fine. When I simply > launch QC, it complains about not being able to restore the document, and > you can see that the output I just added to my plugin isn't there, implying > that an older version of the plugin is being fetched. > >> > >> But I've deleted every copy of my plugin that I can find, and it's still > not working. I can see that the plugin in ~/Library/Graphics/Quartz Composer > Plug-Ins gets replaced when I build, but I don't see any way to verify which > plugin QC thinks it's using. > >> > >> Any suggestions? > >> > >> TIA, > >> Rick > >> > >> _______________________________________________ > >> 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/doktorp%40mac.com > >> > >> This email sent to [email protected] > > > > _______________________________________________ > 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] >
_______________________________________________ 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]
