• 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: Designing for multitudinous objects
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Designing for multitudinous objects


  • Subject: Re: Designing for multitudinous objects
  • From: Allan Odgaard <email@hidden>
  • Date: Fri, 30 Jan 2004 16:23:11 +0100

On 29. Jan 2004, at 17:42, Erez Anzel wrote:

In a nutshell, I could have around 100,000 objects which the user imports/selects/edits/whatever, all in one command. Currently each object broadcasts a notification when it is changed, and each window controller is an observer. [...]

What can the receiver do with this notification? I mean, if n points change, is there anything besides simply redrawing everything in the bounding box of these n points?

If not, then each point can simply extend the containers bounding box (marking "changes") and before returning to the event loop, the container can send a notification (if the bounding box is != 0).

I would think that this also remove some logic from the various views, cause rather than recieve info that a polygon was moved, a line changed colour and a point was added, it will simply be told to redraw a box containing these changes (applying whatever transformations to map this box to view coordinates).
--
http://www.top-house.dk/~aae0030/
_______________________________________________
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.
  • Follow-Ups:
    • Re: Designing for multitudinous objects
      • From: Erez Anzel <email@hidden>
References: 
 >Designing for multitudinous objects (From: Erez Anzel <email@hidden>)

  • Prev by Date: Re: OK to use setCharactersToBeSkipped:nil ?
  • Next by Date: Re: OK to use setCharactersToBeSkipped:nil ?
  • Previous by thread: Re: Designing for multitudinous objects
  • Next by thread: Re: Designing for multitudinous objects
  • Index(es):
    • Date
    • Thread