On Fri, May 8, 2009 at 5:51 AM, Kiran Kumar S <kirankuma...@prithvisolutions.com> wrote: > according to documentation for > beginSheet:modalForWindow:modalDelegate:didEndSelector:contextInfo: it says > that While the application is in the run loop, it does not respond to any > other events (including mouse, keyboard, or window-close events) unless they > are associated with the sheet. It also does not perform any tasks (such as > firing timers) that are not associated with the modal run loop. > But in my app the timer i had created fires even my main window is in > running as Modal
The documentation is completely broken here. That's not how sheets work. Sheets only block events to the window they are associated with. Events to other windows work just fine. You can see this by bringing up the standard save sheet in, say, TextEdit, and observing how you can still create new documents, edit other open documents, etc. As such, the fact that timer still fire is completely expected. I recommend you file a bug against the documentation. It seems that they did a copy/paste job from the -runModalForWindow: method despite the fact that they work nothing alike. Mike _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
