Re: beginSheetModalForWindow: and Distributed Objects

FROM : Andrew Kimpton
DATE : Thu May 01 22:14:04 2008

On May 1, 2008, at 1:52 AM, Michael Vannorsdel wrote:

> I'm fairly certain this method keeps the loop in default mode; the 
> docs are probably copy and pasted or contain archaic info.
>
> Just to recap, how do you know messages are not being processed? 
> And where are these originating, another process, a secondary 
> thread?  When you end the sheet does a burst of messages suddenly go 
> through?


I'm not quite sure what was going on before - but everything is now 
working fine in the manner you and I (and Mike) would entirely expect 
it to. No need to worry about adding a different run loop mode, just 
set up the connection and call beginSheetModalForWindow:

It's possible some other sending side error was causing me to think 
that messages were not being delivered, then the documentation did 
nothing to reassure me that I didn't need special handling or somesuch.

Andrew 8-)

> On Apr 30, 2008, at 3:29 PM, Andrew Kimpton wrote:
>

>> I'm simply calling beginSheetModalForWindow: on  a 'regular' window 
>> (this isn't a document based app - but the window in question isn't 
>> modal either).
>>
>> So from Mike Ash's comments it seems like something else must be 
>> going on. What set me down this path is the comment in the docs for 
>> [NSApplcation beginSheet: modalForWindow: ...] (which I assume 
>> [NSAlert beginSheetModalForWindow: calls ?)
>>
>> Use this method in cases where you do not need to do any additional 
>> background processing while your sheet runs. This method consumes 
>> only enough CPU time to process events and dispatch them to the 
>> action methods associated with the sheet. If you want to perform 
>> additional background processing, use runModalSession:together with 
>> an NSModalSession object instead.
>>
>> The comment about additional background processing is confusing to 
>> me. Does handling messages on an NSConnection count as background 
>> processing ? Do I have to go to the expense of using 
>> runModalSession: (Mike Ash's comments seem to suggest not, it 
>> should 'just work')
>>
>> Bottom line - it sounds like beginSheetModalForWindow shouldn't 
>> block connection handling but it seems to in my case - where should 
>> I look begin to look for the cause of this ?

>
> _______________________________________________
>
> Cocoa-dev mailing list (<email_removed>)
>
> 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/<email_removed>
>
> This email sent to <email_removed>