WAYRTTD? Interaction through dialog boxes, modal or otherwise, is typically counter to most of the goals that automation is typically trying to achieve. But if you can describe what you're really trying to do, perhaps an appropriate solution will become evident.
Thanks for the response, Rich!, but I really am just trying to do what I described: activate or quit BBEdit with a script when a dBox is open. I have no interest in controlling the dBox itself; I would be content if it had to be closed first, but I have not found any way to get BBEdit to respond to any scripting if a dBox is open. It won’t even acknowledge IF a dBox is open, it just freezes the app calling the script. To pontificate my intentions further:
If I have a dBox open in BBEdit and go off to work in another app and BBEdit gets buried in other windows, I just want to activate BBEdit again, preferably via a script called with a key combination. (I use control-cmd-b to call the script with iKey)
If BBedit has a dBox open, all hell breaks loose, and I either have to open Activity Monitor and force-quit iKey or go to a menu of apps and activate BBEdit that way.
?? Thanks! -- ------------------------------------------------------------------------ Have a feature request? Not sure the software's working correctly? If so, please send mail to <[EMAIL PROTECTED]>, not to the list. List FAQ: <http://www.barebones.com/support/lists/bbedit_script.shtml> List archives: <http://www.listsearch.com/bbeditscripting.lasso> To unsubscribe, send mail to: <[EMAIL PROTECTED]>
