Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CILinearGradient and 10.5 mess


On Mar 20, 2008, at 4:07 PM, Chris Meyer wrote: 
> I don't know exactly what they assumed or how this was implemented,
> but I do think that the behavior you're describing sounds like a bug
> in CoreImage.

At this point, fixing it is only going break any code that I write to work around it. Not a great situation. Maybe I'll just write code that makes a gradient, samples it, and chooses based on empirical evidence. Ugh!

FWIW, we noticed that the documented behavior was broken when 10.5 came out and worked around it using

if (floor(NSAppKitVersionNumber) > NSAppKitVersionNumber10_4) {
// assume gradients are in sensible order
}
else {
// assume gradients are in 10.4 order
}

If Apple fixes this to work as documented, it will probably break numerous apps.

> Most apps don't need to know what SDK they were built against; they
> need to know what the current OS version is. That's what
> NSAppKitVersionNumber is meant to provide - what version of AppKit are
> you currently running against. It has _never_ been meant to indicate
> what version of the SDK you linked against.

OK. No reason to bang my head against a wall even though this behavior seems to be of limited usefulness. But it is what it is.

It's useful for cases like this, where functionality changes based on framework version instead of linkage (as it was apparently supposed to).

--
adam



On Thu, Mar 20, 2008 at 3:48 PM, Eric Schlegel <email@hidden> wrote:

On Mar 20, 2008, at 3:45 PM, Chris Meyer wrote:
> How would an application ever tell which SDK it was built against?

Most apps don't need to know what SDK they were built against; they
need to know what the current OS version is. That's what
NSAppKitVersionNumber is meant to provide - what version of AppKit are
you currently running against. It has _never_ been meant to indicate
what version of the SDK you linked against.

> Before you dismiss this message (Eric), I think the case in point is
> how CILinearGradient works. It is NOT backwards compatible. The Core
> Image guys probably (correctly) assumed that NSAppKitVersionNumber
> would return the version of AppKit _linked_ against rather than
> _available on the system_.

I don't know exactly what they assumed or how this was implemented,
but I do think that the behavior you're describing sounds like a bug
in CoreImage.

-eric


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

This email sent to email@hidden 

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

This email sent to email@hidden
References: 
 >CILinearGradient and 10.5 mess (From: "Chris Meyer" <email@hidden>)
 >Re: CILinearGradient and 10.5 mess (From: Jack Small <email@hidden>)
 >Re: CILinearGradient and 10.5 mess (From: "Chris Meyer" <email@hidden>)
 >Re: CILinearGradient and 10.5 mess (From: Eric Schlegel <email@hidden>)
 >Re: CILinearGradient and 10.5 mess (From: "Chris Meyer" <email@hidden>)
 >Re: CILinearGradient and 10.5 mess (From: Eric Schlegel <email@hidden>)
 >Re: CILinearGradient and 10.5 mess (From: "Chris Meyer" <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.