On Dec 17, 2008, at 7:21 PM, Deivy Marck Petrescu wrote: Chris go ahead and pick on me, but before reread my message and see if that answers your questions...
My point was that I am not picking on you, and I won't. :-) Should it be surprising that we would like more control over the display dialog? It is our way of communicating with the end user or ourselves. Why shouldn't we be able to control all aspects display dialog?
You shouldn't be able to force arbitrary applications to display a dialog if they aren't even scriptable. Apparently you did not like the answers and suggestions you got.
Let me be clear: That is not the case at all.
Now, as the reason for using SystemServerUI instead of System Events (used in the preceding example) is because the available tool (SE) does not do the job. So, as others have already suggested, if it works temporarily, it works!
Sending ‘display dialog’ to SystemUIServer or any other application within /System/ as a workaround is as completely arbitrary and incorrect as sending it to, say, “Dock”, or “SecurityAgent”. It may work today, but those applications aren't designed to do that, and your script is likely to break in the future. (And, yes, I tried it, you can tell “Dock” to display an alert. Whee!)
-- Chris Page
The other, other AppleScript Chris
|