Select from the pull-down list box to select the Version Field items. You can set a value for each Version Field item. Examples of Version Field items are FileVersion, CompanyName, ProductVersion, SpecialBuild, etc...
Enter a value for the selected Version Field. The text of the value will be based on the Version Field selected. After you build the EXE or DLL file, you can check the version and its value description by clicking on the Properties icon in Windows Explorer for the EXE file generated by ATEasy.
If this is checked, then every time you build an executable or DLL,
the File Version build number will increment. Project file must be saved
in order to maintain the build number. File Version consists of
4 numbers: Major.Minor.Revision.Build. For example "1.2.3.4.".
Build number is up to 64K (Word) and user can set it manually.
Checked by default. This option causes the ATEasy compiler to generate warning for each variable that is not used (not referenced). This includes global variables and procedure local variables. It does not generate warning for public system or driver variables or constants that are not in use (since these may be used in another project).
Checked by default, ATEasy excludes procedures that are not referenced or called during build. But when you have a procedure name initialized by a string variable, ATEasy parser does not know the procedure being called and thus will exclude it from the build. You can check this flag to prevent from those procedures being included during the build.
Not-checked by default. This option causes the ATEasy parser to generate warning for each procedure parameter variables that are not used (un-referenced) inside the procedure.
v5-v10 (156c) not checked by default v10 156d or newer checked by default. ATEasy provides an option to optimize boolean expressions. For example:
if Expr1 and Expr2
If the expression Expr1 is
evaluated to False value, then Expr2
will not be evaluated or executed. Thus provides a faster evaluation
of the If expression.
This feature is not only an optimization, but also it makes code simpler.
For example, you can now write the following code in one line:
if ob<>Nothing and ob.xxx
instead of using a nested if statement as shown here:
if ob<>nothing
if ob.xxx
Enter conditional identifier(s) sprated by spaces or commas to be used with the #ifdef directive. When defined, the identifier can be used in all the modules contained within the project file. Usually the identifier is entered in uppercase characters. For more information on conditional identifiers, see Conditional Compilation.
The following example demonstrates the use of the DEBUG identifier in code. You would enter DEBUG in the Defines field:
#ifdef DEBUG
! code to be included in debug
#endif
In ATEasy 5.0,
a pre-define symbol ATEASY5 is
available for version 5:
#ifdef ATEASY5 ! defined by ATEasy if version 5 is running
TestStatus=PASS
#else