OmniOutliner and controlling user interaction in AppleScript

[Andrew Abernathy]

Any of the scripters out know much about / have opinions about 
controlling the user interaction level (which indicates whether or not 
the application should attempt any interaction with the user)? As best 
as I can tell, AppleScript still doesn't have standard support for 
changing the user interaction level, and I'm trying to confirm this, 
and see what support scripters think is important.

This is coming up at the moment because if a user asks OmniOutliner to 
open a document and it fails (permissions problem, corrupt file, etc) 
then an alert panel is displayed, but if the user double-clicks an 
outliner document or a script tells OO to open a document and it fails, 
no alert panel is displayed, leaving the user wondering what happened.

The difference between these cases is that both the double-click and 
scripting actions go through AppleEvents, but it's difficult (at best) 
to tell the difference between them programmatically in order to 
display an alert in the double-click case and be silent in the 
AppleScript case. I'd be fine with just checking the AppleEvent user 
interaction level, relying on the scripter to turn off user interaction 
if so desired (and turn it back on when done), but there doesn't appear 
to be standard support for scripters to adjust the user interaction 
level. I'm hoping I'm overlooking something, or someone has some 
insight that will help. Short of that, anyone have expectations for 
exactly what they would _want_ in terms of this functionality?

-andrew