How to customize ...

the Operation-tree, the Operation-list and the Operations menu

The Operation-tree and the Operation-list contain a list of all ILWIS operations and some other commands (New, Show, Edit).

To hide or show the Operation-tree and the Operation-list:

To add scripts to the Operation-tree/Operation-list and to the Operations menu of the Main window

ILWIS scripts can be added to the Operation-tree, the Operation-list and to the Operations menu of the Main window, so that the scripts will always be available.

Using a fixed Scripts folder within the ILWIS program folder:

If you have access to the folder where the ILWIS program is located, i.e. the folder where the ILWIS executable is located, you can add a subfolder/subdirectory called Scripts in which you can place one or more scripts. When you restart ILWIS, the scripts found in the Scripts folder will appear in the Operation-list, in the Script section of the Operation-tree, and as a Script section on the Operations menu.

Specifying one or more user-defined Script folders:

Scripts can also be located in other folders than in a fixed Scripts folder.

 

The scripts that are available in the specified Script folders/directories will appear:

To add external applications to the Operation-tree/Operation-list and to the Operations menu of the Main window

Similarly, external programs or executables (.exe, .com, .bat), shortcuts (.lnk) either to Windows applications or to files of registered applications, and external files of a registered file type (for instance .doc, .txt, .pdf, .xls, .ppt, .pps, .gif, .bmp, etc. ) can be made available in the Operation-tree, the Operation-list and on the Operations menu of the Main window.

Using a fixed Tools folder within the ILWIS program folder:

If you have access to the folder where the ILWIS program is located, i.e. the folder where the ILWIS executable is located, you can add a subfolder/subdirectory called Tools in which you can place one or more external tools. When you restart ILWIS, the tools found in the Tools folder will appear in the Operation-list, in the Tools section of the Operation-tree, and as a Tools section on the Operations menu.

Specifying one or more user-defined Tools folders:

External tools, shortcuts or files may also be located in other folders than in a fixed Tools folder.

 

The external programs, the shortcuts, and/or any other registered files that are available in the specified Tools folders/directories, will appear:

Mind:

Advanced (action.def)

To further customize the Operations menu, the Operation-list and the Operation-tree, advanced users may wish to modify the ILWIS action.def file, or to create their own action.def file that either replaces the ILWIS action.def file or that is used in addition to the ILWIS action.def.

In short, the action.def file lists the operations that are available on the Operations menu, in the Operation-tree and the Operation-list, and the manner in which these operations are arranged.

The action.def file can be edited for instance with Notepad; the meaning of the entries in the file are shortly described at the top of the file; entries are space-delimited.

Modifying the ILWIS action.def file:

If you have access to the folder where the ILWIS program is located, i.e. the folder where the ILWIS executable is located, you may edit, at your own risk, the ILWIS action.def file. For safety reasons, it is advised to make a copy of the original action.def file first!

Creating your own action.def file (replacing the ILWIS action.def file):

Tips:

Creating your own action.def file (used in combination with the ILWIS action.def file):

The entries in your own action.def will be listed below the regular ILWIS operations in the Operation-list, the Operation tree and the Operations menu.

Adding external applications to the action.def file and optionally use parameters for an external application:

To add an external application to an action.def, use the following syntax for the command entry in the action.def:

For more information on using commands and search paths for external applications, etc., see Appendices : ILWIS commands, section Other commands and expressions.

Examples:

 

See also: