Re: Quartz blitter/hardware support?
Re: Quartz blitter/hardware support?
- Subject: Re: Quartz blitter/hardware support?
- From: Jason Harris <email@hidden>
- Date: Thu, 27 Jun 2002 00:36:06 -0700
I wish I _could_ learn about Jaguar - I'm just an online ADC member.
Quartz debug shows the entire content flash yellow as I scroll. This occurs
even if I subclass every view so that isOpaque returns YES. I've commented
out code so that my drawRect routine just calls super's. My NSScrollViews
have drawsBackground set to YES and a white background set.
If I setCopiesOnScroll to NO, most of the view still flashes yellow while
scrolling, but a few areas remain clear.
I'm not being scientific at all about measuring frame rates. I've got an
NSTimer that scrolls the view when it fires. I set it to fire at some
frequency like 0.1 seconds and to stop after firing 10 times or after a set
time has elapsed. The frame rate is low enough that I can just count how
many frames have elapsed.
So, of course, I could be seeing NSTimer being a laggard instead of
Quartz...
Jason Harris
Shawn Erickson Tried to Tell Me:
>
You guys will like Jaguar then. I suggest learning what you can about it
>
so you don't end up optimizing yourself into a corner.
>
>
By the way... I have a feeling you content it fully repainting itself
>
during scrolling if you are seeing frame rates that low. Also how are
>
you measuring frame rate?
>
>
-Shawn
>
>
On Wednesday, June 26, 2002, at 08:40 PM, Jason Harris wrote:
>
>
> Allan Odgaard Tried to Tell Me:
>
>
>
> [snipped lots of stuff about slow scrolling in Quartz]
>
>
>
> It's interesting that this comes up. I just wrote some code that
>
> automatically scrolls an NSScrollView that contains a fairly complicated
>
> view hierarchy. I'm making extensive use of isOpaque in the views, and
>
> I've
>
> used Quartz Debug to verify that I'm not doing extra redraws.
>
>
>
> On a 500MHz iBook, I get about 2 frames per second. Absolutely
>
> horrible.
>
>
>
> I did notice, however, that using scrollToPoint made a big difference.
>
> When
>
> I first implemented it, I was using setBoundsOrigin on my NSClipView
>
> instead. I got about one update per two seconds. Really, really
>
> horrible.
>
>
>
> Anyway, I don't see how I could improve my code much beyond setting
>
> isOpaque
>
> and making sure it's not drawing extraneous stuff. Except maybe by
>
> using
>
> NSView's drawRect routine instead of subclassing it :)
>
>
>
> So, basically, not much to this post except to say, "Me too!"
>
>
>
> Jason Harris
_______________________________________________
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.