On a slightly different note, looking at that build, and the Lion QC editor:
Is it me, or is it weird that QCPlugin are now described as "macro patches" in the editor? How in the flip is it a macro? Nowhere in the class reference or patch programming guide are QCPlugins referred to as macros, that I know of. I can see how it arguably makes sense, yet it's a weird time to start calling them that, and there's no kind of release note that describes this shift. It just seems willy nilly. It's also unclear why/what is tagging them as "macro patch". What's making this little grey text? It's not reflecting the "real name", nor the key? Why is it even there? The only other patch I see this with offhand are the pre-loaded composition importer based patches that identify themselves as composition importers. Macro patches (actual macro patches) don't even get this identifier. It's interesting that something fundamental like the Categories column was nixed from the Patch Creator on the Leopard to SL shift, and now extra category/name stuff is getting pushed onto the patches on the Editor, to help clarify what the heck you just picked from the Patch Creator. Good stuff. (Maybe this grey text would have been appropriate for the LFO "wave generator" change). On Tue, Jul 26, 2011 at 8:00 PM, George Toledo <gtole...@gmail.com> wrote: > > > On Tue, Jul 26, 2011 at 7:39 PM, vade <dokt...@mac.com> wrote: > >> Is this consistent across 32 and 64 bit QC Editor environments on 10.7 ? >> >> What about older runtimes, like 10.6? >> >> > I'm checking the project, and found another level of detail. > > If I flip the order of one item in my attributesForPropertyPortWithKey, > stuff becomes unpredictable, and it no longer lists "last = top", but first > = bottom stayed consistent. > > With some more fiddling, it seems that if > the attributesForPropertyPortWithKey, AND that the @dynamic properties are > listed in the same order, my plugin restores with ports in the expected > order in 10.6 and 10.7, 32 and 64 bit. I did compile in SL, not Lion. This > test also had the interface listed in the same order. > > I didn't test to see if the interface order matters (as in, I didn't fiddle > and make one in a different order to see what would happen), I just went > ahead and made it match the @ dynamic and attributesForPropertyPortWithKey > orders, so it may not have to match, for whatever that's worth. I don't > know. > > On Jul 26, 2011, at 7:36 PM, George Toledo wrote: >> >> >> >> On Tue, Jul 26, 2011 at 7:23 PM, vade <dokt...@mac.com> wrote: >> >>> Im fairly certain this is a known issue, but it appears 10.7 has 3rd >>> party input port ordering issues when running in 64 bit mode, not respecting >>> the output of >>> >>> + (NSArray*) sortedPropertyPortKeys; >>> >>> However running in 32 bit mode seems fine. >>> >>> Is this fixable via some preference or cache cleansing I have not found, >>> or a re-compile? >>> >>> Filed as bug: 9845407 >>> >>> Thanks. >>> >> >> I don't really think you want to hear this, and am guessing you probably >> already know this, but for the sake of other readers, and out of curiosity >> to see if you get the same results: >> >> Upon Lion, when building QCPlugins, I've abandoned the sortedPropertyKeys >> and when I setup: >> >> + (NSDictionary*) attributesForPropertyPortWithKey:(NSString*)key >> >> I list everything so that the port I want to be at the top is listed last, >> to the port at the bottom being listed first. I've only tested this with >> *one plugin build, *but results seemed consistent, and correct, as >> opposed to using the sortedPropertPortKeys method. So, that *may* work. >> >> >> -- >> George Toledo >> gtole...@gmail.com >> www.georgetoledo.com >> >> >> >> > > > -- > George Toledo > gtole...@gmail.com > www.georgetoledo.com > > > -- George Toledo gtole...@gmail.com www.georgetoledo.com
_______________________________________________ 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: http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
