• 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: 1 pixel width NSBezierPath issue
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 1 pixel width NSBezierPath issue


  • Subject: Re: 1 pixel width NSBezierPath issue
  • From: Shawn Erickson <email@hidden>
  • Date: Tue, 18 Feb 2003 17:50:11 -0800

On Tuesday, February 18, 2003, at 10:06 AM, Sebastian Gomez Papiol wrote:

I think that NSBezierPath have a serious bug, since I have to rewrite a custom NSBezierPath to do what I want to do. I want make a question: a powerful class is a class that can do a lot of things, not only extraordinary things like paint precise curved lines with an excellent antialias algorithm but all the drawing possible. And NSBezierPath don't allow 1 pixel paths without antialias, for this reason I can't use it. The question is: is NSBezierPath a powerful class? the answer: No since Apple solve this issue. I'm a little indignant since I listen NSBezierPath draw 1 pixel lines well in OpenStep and also in the first release of Mac OS X Server...

For many it is not an issue and for a few others it could be...

If you think is has a bug file a bug report with Apple and attempt to outline as best you can what you think should happen when drawing such paths and anti-aliasing is off.

As I said earlier it is likely (but just my running theory) that NSBezierPath, now that is backed by Quartz 2D, is optimized to draw paths with anti-aliasing and hence they end up displaying more pixels when anti-aliasing is turn off then one would expect. In theory they could drop the pixels out that are less then full alpha instead of what looks to be fully painting them, not that this wouldn't cause many skips in paths and such... It may make sense for Quartz to switch its path rendering to better display paths when anti-aliasing is not being used but it isn't trivial.

I also don't think pre-quartzified NSBezierPath rendered paths always "1 pixel wide" in all orientations (not sure how it could with out skips showing in the paths), it most likely did draw them with less pixels (if I remember correctly... its been a while).

I also suggest that you look at using QuickDraw or OpenGL in the short term it may better render what you want if you don't want to roll your own.

-Shawn
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

References: 
 >1 pixel width NSBezierPath issue (From: Sebastian Gomez Papiol <email@hidden>)

  • Prev by Date: Re: 1 pixel width NSBezierPath issue
  • Next by Date: Re: drawing into NSBitmapImageRep
  • Previous by thread: Re: 1 pixel width NSBezierPath issue
  • Next by thread: Re: 1 pixel width NSBezierPath issue
  • Index(es):
    • Date
    • Thread