Re: Folder Actions
Re: Folder Actions
- Subject: Re: Folder Actions
- From: Mr Tea <email@hidden>
- Date: Fri, 08 Jun 2001 14:52:18 +0100
This from Simon Forster - dateline 08-06-01 11.13 AM:
>
1) What is error -1728?
Something referred to in the script isn't where it's expected to be. I've
appended a full list of error numbers to the end of this message (for the
masochistically inclined only).
>
2) What methodology can one use to debug Folder Actions? How can I mimic a
>
Folder Actions event?
One way to debug is to wrap your script (or the part of it that is causing
the problem) in a 'try' block.
try
--do stuff
on error errMsg
display dialog errMsg
end try
If the folder action runs into trouble, this will give you a standard dialog
with OK & cancel buttons, displaying the error message generated by the
script. This message may even contain useful information about the event
that is causing the problem, and will certainly be more welcome than the
wilfully arcane error numbers displayed in those horrid, pus-yellow
notification boxes.
>
3) Occasionally I see errors from the Folder Actions Server. What is the
>
Folder Actions Server?
Just a fancy name for the functionality provided by the Folder Actions
extension, I suspect.
>
4) In what form does the Folder Actions pass on the file path reference? Is
>
it file "file name" of folder "folder name" of application "Finder"?
That's the 'user-friendly', 'english-like' form of path reference that you
get when recording a script or using the Script Editor's 'paste reference'
menu item.
The real deal works the other way around, starting with the name of the disk
that the item is on and working down through any nested folder structure.
The whole thing is wrapped in speech marks, and each item along the way is
separated from the next by a colon. If the final item in the list (the
target of your reference) is a folder, then its name is also followed by a
colon. (This is why colons are forbidden in Mac file and folder names.)
So, a typical path might look like this:
"Hard Disk:System Folder:Control Panels (Disabled):Launcher"
Hope this helps.
Mr Tea
And here, as promised, is that list of error numbers (as originally posted
by Bill Fancher on the MacScript list about 14 months ago)
From Applescript Language Guide:
Operating System Errors
An operating system error is an error that occurs when AppleScript or an
application requests services from the Mac OS. They are rare, and more
important, there's usually nothing you can do about them in a script. A few,
such as "File <name> wasn't found" and "Application isn't running" , make
sense for scripts to handle.
Error number
Error message
0 No error.
-34 Disk <name> is full.
-35 Disk <name> wasn't found.
-37 Bad name for file.
-38 File <name> wasn't open.
-39 End of file error.
-42 Too many files open.
-43 File <name> wasn't found.
-44 Disk <name> is write protected.
-45 File <name> is locked.
-46 Disk <name> is locked.
-47 File <name> is busy.
-48 Duplicate file name.
-49 File <name> is already open.
-50 Parameter error.
-51 File reference number error.
-61 File not open with write permission.
-108 Out of memory.
-120 Folder <name> wasn't found.
-124 Disk <name> is disconnected.
-128 User canceled.
-192 A resource wasn't found.
-600 Application isn't running.
-601 Not enough room to launch application with special requirements.
-602 Application is not 32-bit clean.
-605 More memory is needed than is specified in the size resource.
-606 Application is background-only.
-607 Buffer is too small.
-608 No outstanding high-level event.
-609 Connection is invalid.
-904 Not enough system memory to connect to remote application.
-905 Remote access is not allowed.
-906 <name> isn't running or program linking isn't enabled.
-915 Can't find remote machine.
-30720 Invalid date and time <date string>.
Apple Event Errors
An Apple event error is an error that occurs when Apple events sent by
AppleScript fail. Many of these errors, such as "No user interaction
allowed" , are of interest to users. Also of interest to users are errors
that have to do with reference forms, as well as errors such as "No such
object" .
Error number
Error message
-1700 Can't make some data into the expected type.
-1701 Some parameter is missing for <commandName>.
-1702 Some data could not be read.
-1703 Some data was the wrong type.
-1704 Some parameter was invalid.
-1705 Operation involving a list item failed.
-1706 Need a newer version of the Apple Event Manager.
-1707 Event isn't an Apple event.
-1708 <reference> doesn't understand the <commandName> message.
-1709 AEResetTimer was passed an invalid reply.
-1710 Invalid sending mode was passed.
-1711 User canceled out of wait loop for reply or receipt.
-1712 Apple event timed out.
-1713 No user interaction allowed.
-1714 Wrong keyword for a special function.
-1715 Some parameter wasn't understood.
-1716 Unknown Apple event address type.
-1717 The handler <identifier> is not defined.
-1718 Reply has not yet arrived.
-1719 Can't get <reference>. Invalid index.
-1720 Invalid range.
-1721 <expression> doesn't match the parameters <parameterNames> for
<commandName>.
-1723 Can't get <expression>. Access not allowed.
-1725 Illegal logical operator called.
-1726 Illegal comparison or logical.
-1727 Expected a reference.
-1728 Can't get <reference>.
-1729 Object counting procedure returned a negative count.
-1730 Container specified was an empty list.
-1731 Unknown object type.
-1750 Scripting component error.
-1751 Invalid script id.
-1752 Script doesn't seem to belong to AppleScript.
-1753 Script error.
-1754 Invalid selector given.
-1755 Invalid access.
-1756 Source not available.
-1757 No such dialect.
-1758 Data couldn't be read because its format is obsolete.
-1759 Data couldn't be read because its format is too new.
-1760 Recording is already on.
Application Scripting Errors
An application scripting error is an error returned by an application when
handling standard AppleScript commands (commands that apply to all
applications). Many of these errors, such as "The specified object is a
property, not an element" , are of interest to users and should be handled.
Developers can define new application errors in the -10,000 range for their
applications.
Error number
Error message
-10000 Apple event handler failed.
-10001 A descriptor type mismatch occurred.
-10002 Invalid key form.
-10003 Can't set <object or data> to <object or data>. Access not
allowed.
-10004 A privilege violation occurred.
-10005 The read operation wasn't allowed.
-10006 Can't set <object or data> to <object or data>.
-10007 The index of the event is too large to be valid.
-10008 The specified object is a property, not an element.
-10009 Can't supply the requested descriptor type for the data.
-10010 The Apple event handler can't handle objects of this class.
-10011 Couldn't handle this command because it wasn't part of the
current transaction.
-10012 The transaction to which this command belonged isn't a valid
transaction.
-10013 There is no user selection.
-10014 Handler only handles single objects.
-10015 Can't undo the previous Apple event or user action.
AppleScript Errors
An AppleScript error is an error that occurs when AppleScript processes
script statements. Nearly all of these are of interest to users. For errors
returned by an application, see the documentation for that application.
Error number
Error message
-2700 Unknown error.
-2701 Can't divide <number> by zero.
-2702 The result of a numeric operation was too large.
-2703 <reference> can't be launched because it is not an application.
-2704 <reference> isn't scriptable.
-2705 The application has a corrupted dictionary.
-2706 Stack overflow.
-2707 Internal table overflow.
-2708 Attempt to create a value larger than the allowable size.
-2709 Can't get the event dictionary.
-2720 Can't both consider and ignore <attribute>.
-2721 Can't perform operation on text longer than 32K bytes.
-2729 Message size too large for the 7.0 Finder.
-2740 A <language element> can't go after this <language element>.
-2741 Expected <language element> but found <language element>.
-2750 The <name> parameter is specified more than once.
-2751 The <name> property is specified more than once.
-2752 The <name> handler is specified more than once.
-2753 The variable <name> is not defined.
-2754 Can't declare <name> as both a local and global variable.
-2755 Exit statement was not in a repeat loop.
-2760 Tell statements are nested too deeply.
-2761 <name> is illegal as a formal parameter.
-2762 <name> is not a parameter name for the event <event>.
-2763 No result was returned for some argument of this expression.
--
Brew of the day: Orange Pekoe