• 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: "Erik M. Buck" <email@hidden>
  • Date: Tue, 18 Dec 2001 10:34:11 -0600
  • Organization: EMB & Assocites Inc.

The window display logic could just call each view's displayInRect: the
correct number of times for the number of invalid rects that must be
re-displayed. The real key is that views that do not need to be
re-displayed at all should not be displayed at all. Right now, the entire
content of a window must be redrawn just because two small views on opposite
corners of the window need re-display. This was definitely NOT necessary in
Openstep 4.2 for Windows. We sell a high end animation application that
does not exhibit this ridiculous behavior.


----- Original Message -----

  • Follow-Ups:
    • Re: Ways Apple COULD optimize -setNeedsDisplay
      • From: Marcel Weiher <email@hidden>
References: 
 >Re: Ways Apple COULD optimize -setNeedsDisplay (From: Ian Clark <email@hidden>)

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