Re: NSScrollView problems in Tiger
Re: NSScrollView problems in Tiger
- Subject: Re: NSScrollView problems in Tiger
- From: Cameron Hayne <email@hidden>
- Date: Fri, 27 May 2005 13:16:29 -0400
On 27-May-05, at 12:57 PM, Troy Stephens wrote:
Another possible workaround might be to leave the document view's
bounds unscaled, and instead apply the transforms you need to map
from your data space to view space at the top of the document
view's -drawRect: method, using an NSAffineTransform.
I've been wondering how that compares in efficiency - or are the two
techniques equally efficient (in terms of drawing speed or CPU
usage)? Does the answer depend on what type of GPU is present?
I find it conceptually easier to keep the bounds fixed at the
coordinates of my model (and not have any explicit transform in
drawRect) but that means that I have to be careful to reset the
bounds each time the view gets resized. But I also had been doing it
this way since I thought it might be (slightly?) more efficient than
having an explicit transform in drawRect. (My app updates many
millions of pixels per second so efficiency is a concern.)
--
Cameron Hayne
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden