• 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: Setting the clip, double buffering
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Setting the clip, double buffering


  • Subject: Re: Setting the clip, double buffering
  • From: Candide Kemmler <email@hidden>
  • Date: Thu, 5 Jul 2001 13:39:45 +0200

Le jeudi 5 juillet 2001, ` 12:34, Stiphane Sudre a icrit :


On jeudi, juillet 5, 2001, at 11:50 AM, Candide Kemmler wrote:

Hi !

I don't find any clip-setting function for graphics, i.e. functions that set a viewing rectangle outside of which all drawings are discarded.

In Cocoa, it's in the NSBezierPath or in the NSGraphicContext.

- addClip
- setClip
+ clipRect

Fine. Strange place to put that I think. I find the Java2D API much clearer and more coherent ! The [ NSColor set ] thing is strange too. In Java, you would tell a *graphic context* to set it's color, which is logical. What does it mean from a color's perspective to "set" ???

But that's about aesthetics, not really relevant, is it ?


As of double-buffering, until now, I just didn't care, but then now I get this very annoying bug where I see a path drawn a fraction of a second on the screen, then it disappears forever...

I don't know. I'm not using Java.

I'm not either ! anymore... That is on Mac OS X. The routine I'm talking about runs on the Java 2 Platform. I gave up developing in java-cocoa last week.

No, I was asking about double-buffering with Cocoa.


BTW, until now, there's no noticeable performance difference between the Java drawing routine and the Objective-C/C drawing routine under Cocoa...

I would be surprised since they stated that the Java drawing was not at all optimized

To be honest I didn't try out the code on my Mac box, but on a 700 Mhz K6. My G4 runs at 350 Mhz, and the C implementation is definitely not faster than the Java running on my Wintel (if not a bit slower).

Regards,

Candide

PS: Stiphane, c'est pas un nom frangais par hasard ? J'ai dij` posi la question, mais tu ne l'avais peut-jtre pas remarqui...


  • Prev by Date: [NEWBIE] NSAttributedString
  • Next by Date: [OT]Re: AppKit source available as reference?
  • Previous by thread: Setting the clip, double buffering
  • Next by thread: [NEWBIE] NSAttributedString
  • Index(es):
    • Date
    • Thread