• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: NSShadow changes on 10.5.2?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSShadow changes on 10.5.2?


  • Subject: Re: NSShadow changes on 10.5.2?
  • From: Ricky Sharp <email@hidden>
  • Date: Fri, 15 Feb 2008 15:27:20 -0600


On Feb 15, 2008, at 7:43 AM, Jim Correia wrote:

On Feb 15, 2008, at 5:48 AM, Uli Kusterer wrote:

On 15.02.2008, at 11:36, João Pavão wrote:
I had the impression that there was an NSShadow bug only on 10.5.0 thru 10.5.1. My shadows looked great on 10.4.x, and I had to add a check to draw them with an extra 1pt offset on leopard to account for that bug. This made them look exactly the same both on tiger and on leopard.

Well, for what it's worth, Safari (and by extension WebKit) has had this bug since 10.4.x. I haven't changed anything on my web site's text shadows in ages, and I am still running 10.4.11 on one Mac that still shows them with the bug. It still looked fine up to 10.5.1 (which I have on another Mac), but in 10.5.2 it was fixed, so all shadows designed for the old behaviour were suddenly off by one pixel down and right.


So, I am actually able to see the matching 10.5.1 and 10.4 behaviour side-by-side. Not sure about NSShadow.

This is the behavior I am seeing as well. The shadows only look bad on 10.5.2 (which now actually draws them at the offset you pass in.)


I'd still like to derive the function

	f(actual offset) = 10.5.1/10.4.x offset

so that I don't have to hand tweak every shadow offset in my app so that they look the same on both OS releases.


And this is why I'm really hoping they address the bug I filed (to revert drawing behavior to what it was, yet add an API that developers can choose to set if they want to in order to get new behavior). Nobody should have to attempt to fudge offsets based upon an OS release.

Also, for those customers with older versions of your app that choose to remain on those versions (e.g. maybe they don't want to go with a paid upgrade), they'll end up getting different output when moving to 10.5.2 and beyond. That's unacceptable IMO.

___________________________________________________________
Ricky A. Sharp         mailto:email@hidden
Instant Interactive(tm)   http://www.instantinteractive.com

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: [Workaround] NSShadow changes on 10.5.2?
      • From: Ricky Sharp <email@hidden>
References: 
 >NSShadow changes on 10.5.2? (From: Jim Correia <email@hidden>)
 >Re: NSShadow changes on 10.5.2? (From: João Pavão <email@hidden>)
 >Re: NSShadow changes on 10.5.2? (From: Uli Kusterer <email@hidden>)
 >Re: NSShadow changes on 10.5.2? (From: Jim Correia <email@hidden>)

  • Prev by Date: Re: Proper use of #define to aid in compile-time checking of strings (was KVC and KVO for arrays)
  • Next by Date: Re: [Foo new] vs [[Foo alloc] init]:
  • Previous by thread: Re: NSShadow changes on 10.5.2?
  • Next by thread: Re: [Workaround] NSShadow changes on 10.5.2?
  • Index(es):
    • Date
    • Thread