Re: AS Application
Re: AS Application
- Subject: Re: AS Application
- From: Philip Aker <email@hidden>
- Date: Sat, 26 Sep 2009 16:13:30 -0700
On 2009-09-26, at 14:44:36, Steffan A. Cline wrote: Why don't you just write the 'command" to a file to see what the cumulative lines look like. If it looks correct, then another possibility is the permissions of the files involved. Also, put your code in a 'try', 'on error', 'end try' block and log any caught errors to a file.
I found the error I was making and fixed it but am now playing with error trapping. I am trying to capture the result of the error so I can format it my way.
set theResult to (do shell script command)
This does not work. If it succeeds then it's ok. If there is an error, I can use the "on error" but the actual error is not contained within theResult. Is there a way around this?
Google is your friend.
on error errorMsg
do something with errorMsg
You can also get an error number for trapped errors. So:
try --doit() on error errs number errn display dialog errs & return & return & "Error code: " & (errn as text) default button "OK" with icon stop return -- the return value may be anything appropriate for your application end try
Is there a way to set a scrollable area for the output rather than a tall dialog?
You will have to move to AppleScript Objective-C and Interface Builder to customize dialogs. For 'display dialog' a cheap trick is to pad your string result with spaces and returns.
Philip Aker
echo email@hidden@nl | tr a-z@. p-za-o.@
Democracy: Two wolves and a sheep voting on lunch.
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden