This dialog displays preprocessor header file for importing header files during/after Inserting a DLL. See Notes for more information.
This is the contents of Preprocessor Header File, "ATEasyPreprocessor.h" located in the ATEasy directory. This file contains #define(s) and typedef(s) of some of built-in data types and defines. Especially it contains typedefs for C pointer types. You can further add new #define and typedefs, or modify, and/or delete existing ones. During Importing process, ATEasy reads this header file prior to any header files.
This allows you to save what you have modified. The dialog closes after save.
This will close the dialog.
This button allows you to reset the file to the ATEasy preprocessor original header file - the contents originally provided by ATEasy.
The Import C Header File dialog is not intended to 100% precise and cannot be that way since the C data types are not defined that way for example 'Short *' parameter type (pointer to a short) can be in ATEasy 'Var Int', 'Var Int[]' or 'Val Int[]'. Microsoft came up with ActiveX/COM type libraries and .Net assemblies to avoid this and provide a precise description of data types.
Make sure the header file contains legal C statements.
The import will not work properly when attempting to import C++ statements (i.e. classes etc). There is no standard way of exporting C++ classes from a DLL.
ATEasy provides the Ambiguous C Data Type dialog to help finding the C data type that best match ATEasy data type.
You should always check the imported definitions (functions, parameters and data types) by comparing it to the header file content and correct them manually (using the Variable Properties) after Import is complete. This will help you avoid memory exceptions, stack corruption and other problems when using the DLL.