• 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: Ways Apple COULD optimize -setNeedsDisplay
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Ways Apple COULD optimize -setNeedsDisplay


  • Subject: Re: Ways Apple COULD optimize -setNeedsDisplay
  • From: Norbert Heger <email@hidden>
  • Date: Tue, 18 Dec 2001 15:27:36 +0100

John C. Randolph <email@hidden> wrote:

> I don't have a NeXT machine put together at the moment to check,
> but did NeXTSTEP or OpenStep ever actually do the optimizations
> you're discussing?

NEXTSTEP (3.3) did
OPENSTEP (4.2) did not, same behavior as we have now in OSX

Remember, there have been huge AppKit API changes from NEXTSTEP to OPENSTEP:

NEXTSTEP: View - (id)drawSelf:(NXRect *)rects :(int)rectCount;
OPENSTEP: NSView - (void)drawRect:(NSRect)aRect;

Best Regards, Norbert

_____________________________________________
Norbert Heger, Objective Development
http://www.obdev.at/


  • Follow-Ups:
    • Re: Ways Apple COULD optimize -setNeedsDisplay
      • From: Marcel Weiher <email@hidden>
References: 
 >Re: Ways Apple COULD optimize -setNeedsDisplay (From: "John C. Randolph" <email@hidden>)

  • Prev by Date: Re: THANK YOU OSX GANG
  • Next by Date: Re: THANK YOU OSX GANG
  • Previous by thread: Re: Ways Apple COULD optimize -setNeedsDisplay
  • Next by thread: Re: Ways Apple COULD optimize -setNeedsDisplay
  • Index(es):
    • Date
    • Thread