Re: Bug in -[NSWindow invalidateCursorRectsForView:] not forcing resetCursorRects?
Re: Bug in -[NSWindow invalidateCursorRectsForView:] not forcing resetCursorRects?
- Subject: Re: Bug in -[NSWindow invalidateCursorRectsForView:] not forcing resetCursorRects?
- From: "Ben Kennedy" <email@hidden>
- Date: Tue, 22 Oct 2002 00:59:35 -0400
- Organization: Zygoat Creative Technical Services
On 21,10,02 at 11:13 pm -0400, Ben Kennedy wrote:
>
My custom view's resetCursorRects: method never gets called following an
>
explicit [[self window] invalidateCursorRectsForView:self]. The method
>
only appears to be called after the view is redrawn, either after
>
scrolling or by an explicit [self setNeedsDisplay:YES] or equivalent.
Hiall again,
I'd like to offer an amendment to my earlier posting, and retract a
portion of my frustrated griping.
Upon further investigation, it appears that following a call to
invalidateCursorRectsForView:, the window's subviews' resetCursorRects:
methods *are* called, but *only* if they had previously instantiated
cursor rects by calling addCursorRect:cursor:.
If there were previously no cursor rects defined, then resetCursorRects:
is not given a new opportunity to define any following a call to
invalidateCursorRectsForView:. (Nonetheless, it seems it *is* still
called when the view is scrolled or expressly re-displayed.)
I suppose by some stretch this makes sense, since one might expect that
if there are no rects to invalidate then there should be no expectation
to refresh them. However, the behaviour is still inconsistent, and the
descriptions misleading.
Is there a bug here, or just poor reasoning behind the implementation?
-ben
--
Ben Kennedy, chief magician
zygoat creative technical services
613-228-3392 | 1-866-466-4628
http://www.zygoat.ca
_______________________________________________
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.