On Thu, 25 Aug 2005 John C. Randolph From wrote:
>On Thu, 25 Aug 2005 John C. Randolph From wrote:
>> Window flushing isn't disabled in drawrect, it just doesn't happen until
>> your -drawRect: method exits, and the process gets back to the main event loop.
>There is an NSWindow function that asks if flushing is disabled
>(-isFlushWindowDisabled). When called in drawRect, it returns true.
>Under most other circumstances it returns false. I think flushing is
>actually temporarily turned off in drawRect, for whatever reason.
Umm... To be precise, it's turned off in the _recursiveDisplayRect... methods. That's
not necessarily the only way that your -drawRect: method will be invoked.
-jcr
Keith Wiley - 26 Aug 2005 16:06 GMT
On Fri, 26 Aug 2005 John C. Randolph From wrote:
>> On Thu, 25 Aug 2005 John C. Randolph From wrote:
>
[quoted text clipped - 8 lines]
> Umm... To be precise, it's turned off in the _recursiveDisplayRect... methods. That's
> not necessarily the only way that your -drawRect: method will be invoked.
Thanks. The whole buffered window thing, which I grant is fantastic as an
end-application feature, is annoying as a debugging feature. At least
Quartz degub is there, and on certain occasions flushing the window
works...but on others it doesn't and you have to turn on Quartz debug...as
stated in my original post to this thread.
Oh well, I think I get it. Thanks.
________________________________________________________________________
Keith Wiley kwiley@cs.unm.edu http://www.unm.edu/~keithw
"Yet mark his perfect self-contentment, and hence learn his lesson,
that to be self-contented is to be vile and ignorant, and that to
aspire is better than to be blindly and impotently happy."
-- Edwin A. Abbott, Flatland
________________________________________________________________________