ur
> hardware is much slower, and of course, this app is not doing anything else
> in between frames except going to sleep. A real audio processing app would
> have much more work to do, but in theory it should have plenty of time to do
> it.
>
> Well, it might give you some sta
perceived as fluent.
All the best
Wolfgang
2011/6/15 Graham Cox
>
> On 15/06/2011, at 10:30 PM, Wolfgang Kundrus wrote:
>
> > We have to update a lot of small onscreen objects and performance is way
> better, when we travers them outside the Cocoa view tree. If we would use
> i
We have to update a lot of small onscreen objects and performance is way
better, when we travers them outside the Cocoa view tree. If we would use
invalidating, we would have to go thru our complete view tree and check for
overlaps with the update rect.
Wolfgang
This did not influence it in a pos
This did not influence it in a positive way. [NSWindow display] makes it
worth and takes down the performance of the whole application.
> > Is there anyway, I can inform the window that graphics need to be flushed
> ?
>
> Have you tried [NSWindow displayIfNeeded] (or just [... display])?
>
>
___
Hi,
I have a problem with the rate at which coalesced updates refresh the
window. We draw some animations outside the drawRect method, using
lockFocus/unlockFocus, but these drawing operations are only flushed about
ones a second. The do get flushed on mouse moves though. Is there anyway, I
can in
