cursor ills
cursor ills
- Subject: cursor ills
- From: robert l clair <email@hidden>
- Date: Thu, 2 Oct 2003 15:21:34 -0400 (EDT)
I've solved things another way, but I'm still curious about some
problems I had with cursors and cursor rects. I was trying to
use a cursor rect the size of my entire view to set the cursor
according to the active tool when it entered the view. The problem
is this:
I have a transparent window over the view (same size) that is used for
temp graphics and animation. No problem. Everything works fine. Except
that when is something drawn in the overlay view I get a mouseExited event
for the regular view as soon as the mouse enters a region where the overlay is
no longer transparent. OK. No problem. I see why and I agree. But I cannot seem
to get a mouseEntered event for the overlay view. I've tried every combination I
can think of for the overlay view. It has its own cursor rect. With and without, in all
combination, acceptsMouseMovedEvents and ignoresMouseEvents for the overlay view's
window. I wasn't aware the mouseInHyperspace was part of the framework.
Another problem: if I have two different document windows open in the same
app and I move the cursor from over one that isn't the main window to the one in front
that is, the mouseEntered event for the front window is delivered _before_ the mouseExited
event for the back one. How annoying. Especially if you were using mouseExited to pop
the cursor stack.
On a slightly different note (and I know a lot of verbiage has been spent on this one) having
the window server control the wait cursor doesn't seem to be such a great idea on a purely
pragmatic basis. Since taking up the Mac I've become the sort of Mac/Unix help desk for
a number of non-technical friends using OS X. In my limited sample, 5 or so, they don't think of
it as the wait cursor - they think of it as the "spinning ball of death" cursor. If it disappears
and the app comes back it isn't like "Oh it finished doing what it was doing" it's more "A near
death experience miraculously averted." I think the problem is that (1) it doesn't appear immediately
when a potentially lengthly operation starts and (2) at least on a perceptual basis the delay before
it starts doesn't feel consistent. It think that a application controlled wait cursor, used consistently,
would make them happier.
.....Bob Clair
-------------------------------------------------------------
The Confusion is the gradient of the Potential for Confusion.
_______________________________________________
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.