First off, I don't expect support on this because it's private API stuff, but I'm posting it to list because someone out there may know. Multiple questions/points:
1- Where is it that the Boolean for "QCEditCompositions" is stored? When I update it in QC, I can see that the com.Apple.QuartzComposer.editor.plist gets updated, but for the life of me, I do not see any entry labelled with that. Basically none of the "system" options seem to be available in that plist. I've gone hunting around for where the plist that control this is, with not much luck. Manipulating the plist inside of the QC app doesn't do anything (can't remember if there's an entry for QCEditCompositions anywhere in that plist though. So.... 2- I basically want my app to shut that the heck off if it's running. I either want to do that by having my app turn QCEditCompositions off via an actual method, or targeting the plist and programmatically altering it. I already have the plist "change an entry" worked out, I just can't find the plist, or entry item that refers to this. I also cannot find a darn line that refers to this anywhere in the SkankySDK or in my own decompilation. I obviously have not combed through every single header, and definitely haven't started looking at the assembly code yet to suss this out. 3- What is QC "calling" this object? Is it the GFGraphEditorView or GFGraphView, whereas the QC Editor itself is QCCompositionEditor? Or are they entangled? The reason I ask is because I've made a QCPatch that QC will not load to wrap some compositions with, and that works fine, albeit with more effort than I think should be necessary (referring to the bundle identifier of QC and banning it, does nothing - you have to make your app load in your app environment and nowhere else at all). But that darn "convenient" QCEditCompositions will totally load the QCPatch even then.... which isn't awesome. If someone cut and pastes that patches that are blocked from QC (of my making), it will lead to incomplete state restoration (yay), or I can do fun stuff like swizzle the patch mode when it's in QC, so that a bunch of noodles break, but I don't want that view to be able to load *at all*. I want my program to turn that view off or block it altogether. I realize that even w/ the QCPatch trick I'm doing, it's somewhat trivial to hack what I'm doing back into a working composition, but I'd still like to block QCEditCompositions or turn it off while my app is running, if possible. Is the only way to prevent a viewable entry in that list *really* to load the composition as NSData? "QCEditCompositions, what don't you get about 'else return NO'"? :-) -gt
_______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to [email protected]
