On Apr 30, 2012, at 1:24 AM, Motti Shneor wrote: > In our client-server app we sometimes present modal sheets on our main > window. Following server notifications we sometimes have to dismiss these > sheets (user is expelled, or otherwise status-changed).
To me, dismissing a sheet without any user intervention sounds like a problematic UI design. It could be confusing if the user was about to do something with the sheet (or was halfway through) when it disappeared. In the worst case the user might be about to click an item in the sheet, and end up clicking through to whatever control was underneath it in the main window. I would suggest either making this UI modeless, or keeping the sheet up but adding a banner or something to it alerting the user that she’s been logged out. > However, If we do this while the user holds one of the sheet buttons pressed > --- within the mouse-tracking loop --- than endSheet happens, and then the > mouseUp event reaches a released object (the sheet) which then crashes the > application. Ouch. The best workaround to this that I can think of is to check the current runloop mode, and if it’s NSEventTrackingRunloopMode give up without messing with the sheet (or check again later.) —Jens
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Cocoa-dev mailing list ([email protected]) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
