- Selecting a module in the project window. Instead of using the mouse or cursor keys to select a module, it may be more efficient to just start typing the module name. The environment will select a module based upon the "first" match of the name as it is entered.
- Is the text too small in the project and editor windows. Remember that you can change the font and size of the font used for the project and editor windows independently. See the Options menu.
- Is the text too small in the dialog boxes. Select the Large Dialogs option in the Options menu.
- Set a default program. If a default program is set, the build commands (such as Link, Debug, Run, ..) will operate on the program, even when it is not selected. For example, you can be editing an any source file and depress Alt-D. This will compile all modules needing compilation, link the program, and start the debugger on the default program.
Note: The first program module added to a project is automatically set as the default program.
Note: If a PGM module is currently selected, and the PGM module is not the default program, the build actions will be on the selected PGM.
- Look at the Module status flags. These will tell you if a module has it's local compiler options, if the module needs compiled, if it is ReadOnly, or if it has errors or warnings from the last time it was compiled.
- Switching between commonly used projects. The last 6 unique projects which were edited by the environment are saved in the system registry. The bottom of the environment File menu lists up to 6 projects. Selecting any of these projects, closes the current project and opens the selected project.
- Add to the text editor auto expansion and correction dictionary for commonly entered text strings.
- You can create shortcuts to your projects on your desktop, in a folder on your desktop, or on menus you create. Refer to the operating system help for the methods of creating a new shortcut on the desktop, in a folder, or in a menu. The shortcut command line would be the path and file name of your project file.
- You can run a script files easily by creating shortcuts on your desktop, in a folder on your desktop, or on menus you create. You only need enter the script file path and name in the shortcut command line. The environment will run the script automatically.
- Text indentation keys. To achieve consistent indention of source code use the Shift left indent, Shift right indent, Shift left space, and Shift right space indentation commands. If a block of text is selected, these commands will shift the entire block. If a block of text is not selected, the commands operate on the line of code containing the insertion point (text cursor).
- Correcting syntax. When a compilation error occurs the environment will automatically edit the offending file, placing the cursor on the first compilation error with a description of the error appearing at the bottom of the main window. You may correct the error then proceed to the next error by using the find next error option, F8, from the Search menu. When all errors are corrected, selecting of the Proceed with last build option, Alt+P, on the Build menu will complete the build operation in process when the error occurred.
- Use scripts to build projects this will guarantee repeatable results
- Ever want to know when you last modified a file. The Module menu Properties command for a selected module will give you information on the module. (Last edited time (changed), last compile time, ...
- Want to know which module uses a given module or which modules are used by a given module, the List module imports and List module clients options of the Tools menu will tell you.
- Want to find all occurrences of a given identifier, or change all occurrences to another identifier. Use Multi file search/replace feature of the environment.
- Mouse users, do not forget about the right click context menus.
- Problems with Standard Input/Output under Win32. When using standard I/O in a Win32 program remember that you must set the linker option to make the program a console application.
- If you have information that you include in all new files use the template files to include the information automatically. Simply edit the appropriate template file (they are all named in the form template.---) and add your text. The system already includes default templates for most all module types.
- Remember that on Unix systems file names are case sensitive. Source file names will have the same case as the module name, and all file extensions should be lower case.