W I N D E V (TM) Copyright ©, 1992-3 ALL RIGHTS RESERVED Helios Software Solutions Carr Brook House Chorley Old Road Brindle CHORLEY PR6 7QZ England Tel/Fax: +44 (0772) 324353 CompuServe Mail: 100041,235 (QUICKGO.TXT) QUICK START =========== A) Tips ------- 1) The File Open dialog allows you to open multiple files at once. You just use Ctrl or Shift in conjunction with the left mouse button to select all the files to open. 2) Dialogs that accept multiple file names, such as File Open, Manage Files and Extract Strings, can take a directory name as the first name in the list. All subsequent names are then assumed to be files in that directory. eg: "c:\apps *.txt *.ini" is the same as "c:\apps\*.txt c:\apps\*.ini" B) File Filters Customization ----------------------------- File filters are a means of using wild cards to list only files with matching names in the File Open/Save As dialogs. You can predefine up to 10 filters for commonly used wild cards. Note that you can have different sets of filters for each project, and for when you are working in non-project mode. In project mode, the default set of filters depends on which environment you select. To configure the filters on the File Open dialog, choose the Global Settings command on the settings menu, and click on the File Filters button on the Global Settings dialog. Then specify your own filters, or click on the help button for further information. C) Existing Makefiles --------------------- If you want to use Windev to build a project for which you have an existing makefile, follow these steps: 1) Choose the Select Project command from the Project menu. 2) In the Select Project dialog, fill in the full path to the directory in which your makefile and source files are stored, and press the Change To button. 3) Windev will change its working directory to your project directory, and create a configuration file called windev.ini. 4) Choose the Configure Project dialog by selecting the Configure Project command on the Project menu. 5) Fill in the name of your target executable (this is needed for the Debug and Test commands). 6) Choose the relevant compiler from the Environment list box, or if your compiler is not in the list, select "Other" and then configure each of the settings. Use the predefined compiler, linker and builder (make program) settings as an example, and see the online help on project variables for a description of each setting. 7) If you require the make program (eg. nmake.exe) to be run with any arguments, click on "BuildArgs" in the scrolling list, type the arguments in the Setting edit field, and click Set. Typically, you will at least require something like "-f project.mak" (without the quotes). 8) If you want to do a debug build, check the "Debug Build" box. This will have the effect of adding the arguments specified against "BuildDebug" in the scrolling list box. If the defaults are not appropriate, change it in the same way as "BuildArgs". 9) Close the Configure Project dialog. Check that it all works by choosing the Build command from the Project menu. This will execute your make commands in a minimized DOS window. The output is automatically displayed in a window if there are any errors, but you can see it anyway, after the build has completed, by selecting the View Results command on the Project menu.