Re: Who Owns An Application?
Re: Who Owns An Application?
- Subject: Re: Who Owns An Application?
- From: Luther Fuller <email@hidden>
- Date: Fri, 23 Jun 2006 09:07:14 -0500
I've done some experimenting and found some documentation since
yesterday. I found that:
Dialogs - will block user access to an application, but will also
block access by any other application, so this just does not work.
Hiding Mail - the scripted application will simply un-hide Mail, so
this won't work.
with transaction - Right idea, but protects the data not the
application, and not supported by Mail, so this is out.
Floating Palettes - haven't tried this yet.
I've confirmed that my problem is totally cosmetic and no data is
lost. User interference simply causes Mail not to delete messages
properly. I'll just have to explain this carefully in the
documentation. (I did find and remove the -609 error.)
Being able to block user interaction with an application while a
scripted transaction is in progress seems like a good idea, but I
haven't the slightest idea how it should best be implemented. A
'transaction' block probably isn't the way to do it. My script does
not have a single 'tell application "Mail"' block, but accesses Mail
in many 'tell' blocks in various handlers. Perhaps a command such as
tell application "someAppl" to start protected access
would be appropriate. 'protected access' would end automatically when
the scripted application quits. Send your ideas to Apple.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden