Optimizing NSView Performance

FROM : Dietrich Epp
DATE : Fri Nov 29 12:09:09 2002

I'm using OS X 10.1.

I have an NSView with a hand tool that scrolls it around.  It is very
slow.  I've optimized much of it using some slick buffering, but I know
the real problem is that the entire thing is redrawn if it scrolls in
both X and Y at the same time.  Scrolling in one direction is just fine.

It seems that there must be some solution to this problem, but I'm
baffled.  I can't figure out what methods are being called to invalidate
the view (the methods are undoubtedly undocumented methods).  I recall
discussion on the list much in the past on this subject, but I couldn't
find any real answers.

I don't care if I have to reverse-engineer undocumented methods.  What
will help me is:

- a list of the undocumented NSView methods
- a method for logging all messages sent to an object, using an NSProxy
perhaps (just a guess, I don't know if it would work in a view
hierarchy, though it should)
- an information on how the NSView class keeps track of invalidated
regions
- information on the differences between 10.1 and Jaguar, if any
- any experiences with this in the past
_______________________________________________
cocoa-dev mailing list | <email_removed>
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.