summaryrefslogtreecommitdiff
path: root/Mac/Demo/applescript.html
diff options
context:
space:
mode:
authorJack Jansen <jack.jansen@cwi.nl>1996-11-20 15:13:24 +0000
committerJack Jansen <jack.jansen@cwi.nl>1996-11-20 15:13:24 +0000
commit0fb1d826987189005b3bedaf7660e93594950c85 (patch)
treedb13786859e0a55f8460faec4a7dfca76523b944 /Mac/Demo/applescript.html
parente1d8c9badea479837a7507118075f84c36fc957e (diff)
downloadcpython-git-0fb1d826987189005b3bedaf7660e93594950c85.tar.gz
Added reference to pdf documentation and bbpy, correctly explained
difference between aetools.Error and MacOS.Error for appletscript programs.
Diffstat (limited to 'Mac/Demo/applescript.html')
-rw-r--r--Mac/Demo/applescript.html7
1 files changed, 3 insertions, 4 deletions
diff --git a/Mac/Demo/applescript.html b/Mac/Demo/applescript.html
index 6d8688e5c4..379ac60ca0 100644
--- a/Mac/Demo/applescript.html
+++ b/Mac/Demo/applescript.html
@@ -157,10 +157,9 @@ AppleScript is basically a connectionless RPC protocol nothing happens
when we create to talker object. Hence, if the destination application
is not running we will not notice until we send our first
command. There is another thing to note about errors returned by
-AppleScript calls: even though <CODE>MacOS.Error</CODE> is raised not
-all of the errors are actually <CODE>OSErr</CODE>-type errors, some
-are error codes returned by the server application. In that case, the
-error message will be incorrect. <p>
+AppleScript calls: <CODE>MacOS.Error</CODE> is raised for
+all of the errors that are known to be <CODE>OSErr</CODE>-type errors,
+server generated errors raise <CODE>aetools.Error</CODE>. <p>
That concludes our simple example. Again, let me emphasize that
scripting support in Python is not very complete at the moment, and