OverviewExamples
This action will cause all debug output to be written to the specified file. To turn off the logging simply pass a blank string as the filename.
Note: If the Debug dialog is visible and you are logging information to a file, debug output will be sent to both the dialog and the file.
(string) The full path to the file where the debug output will be written to.
(boolean) Whether the debug information will overwrite Filename, if it exists, or append to it.
(number) Returns one of the following numeric codes:
CONSTANT |
VALUE |
DESCRIPTION |
FE_NONE |
0 |
No error occurred. |
FE_GENERIC |
1 |
An unspecified error occurred. |
FE_FILE_NOT_FOUND |
2 |
The file could not be found. |
FE_BAD_PATH |
3 |
All or part of the path is invalid. |
FE_TOO_MANY_OPEN_FILES |
4 |
The permitted number of open files was exceeded. |
FE_ACCESS_DENIED |
5 |
The file could not be accessed. |
FE_INVALID_FILE |
6 |
There was an attempt to use an invalid file handle. |
FE_REMOVE_CURRENT_DIR |
7 |
The current working directory cannot be removed. |
FE_DIRECTORY_FULL |
8 |
There are no more directory entries. |
FE_BAD_SEEK |
9 |
There was an error trying to set the file pointer. |
FE_HARD_IO |
10 |
There was a hardware error. |
FE_SHARING_VIOLATION |
11 |
SHARE.EXE was not loaded, or a shared region was locked. |
FE_LOCK_VIOLATION |
12 |
There was an attempt to lock a region that was already locked. |
FE_DISK_FULL |
13 |
The disk is full. |
FE_END_OF_FILE |
14 |
The end of file was reached. |
When adding an action with the script editor, you can use this field to specify a variable that the return value will be stored in.
See also: Related Actions