Re: FolderItem.launch monitoring

[Jann Gobble <janngobble@gmail.com>]

On May 29, 2009, at 2:33 PM, Anic wrote:

> Le 29 mai 09 à 00:39, Norman Palardy a écrit:
>
>
> > On 28-May-09, at 4:05 PM, Tim Jones wrote:
> >
> >
> >
> > > On May 28, 2009, at 2:35 PM, Norman Palardy wrote:
> > >
> > >
> > >
> > > > On 28-May-09, at 3:04 PM, Bastian Bense wrote:
> > > >
> > > >
> > > >
> > > > > I doubt you can do that using folderItem.launch(). The best way  
> > > > > to do that
> > > > > (depending on the application you are using) is to use a shell  
> > > > > command and
> > > > > wait until it finishes/terminates.
> > > > In an OS X shell you can use open -W and the shell wont complete  
> > > > til the application opened quits
> > > > Combine -W with -n and then when the user quits the copy of the  
> > > > application you launched you'll be 100% sure it's the right one
> > > One very important tip - make sure the shell is in asynchronous  
> > > mode (Mode = 2), or your app will appear frozen while the shelled  
> > > process runs.
> > ah right ... you may or may not want that but it's a good thing to  
> > remember :)
> The Apple Interface Guidelines mention that an application should  
> not appear frozen (with the coloured mouse cursor of the spinning  
> ball). I agree with them: when I see an unexpectedly frozen  
> application, I try to force quit it.
Something better may be to use asynchronous mode (like was said above)  
but launch it from a thread in the application, that way if there is  
an issue with the shell, the rest of your app is not locked up.


_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>