Re: UI blocking
Re: UI blocking
- Subject: Re: UI blocking
- From: Kyle Sluder <email@hidden>
- Date: Mon, 17 May 2010 10:02:26 -0700
On Mon, May 17, 2010 at 9:21 AM, Uli Kusterer
<email@hidden> wrote:
> Can't you just not not ask for mouseDown events in your event mask while running your event loop? My guess would be that that would keep any menus from opening.
Gah! That would be a bad idea. The HIG says menus should always be
openable, even if they're entirely disabled.
Also, the menu manager runs a Carbon tracking loop. I don't know if
overriding -mouseDown: would actually work, or if mouse events to the
menu bar are siphoned off before being dispatched to Cocoa land.
> Anyway, this sounds like a very weird use case. Why do you want to disable everything during an animation? Usually animations should be short enough that this shouldn't be a problem, and if the user wants to do something, why keep them from multi-tasking? Animations are intended as indicators, and if a user doesn't want to watch an indicator, that should be their choice to make.
It sounds like Tobias is mistaking the symptoms of the OS animations'
implementation for their intended effect. Shift-click the minimize
button on a window and try to use the menu bar; it's apparent that the
framework (probably CoreGraphics) is running a tight loop while
animating.
--Kyle Sluder
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden