Open topic with navigation
You are here: User Interface Elements - How to Use Each One > Providing a Developer with a Header File
Providing a Developer with a Header File
If it is decided that you are responsible for creating the header file (a file containing an .h extension in your project), you must provide a copy of it to the software developer. The developer will then use the header file to "hook" the numerical values in the header file to the appropriate dialogs or windows in the software.
When you are finished creating the header file, you can export it using the steps below so that the developer has access to it. If you make further changes to the header file, you need to ensure that the developer receives a new copy of it.
How to export header files
- Do one of the following:
The Export Header Files dialog opens.
- On the left side of the dialog, select the format(s) that you want to use for exporting the header file(s). Work with your developer to determine the appropriate type of format.
- C/C++ (.h) If this option is selected, a copy of the header file will be created with an .h file extension.
- Visual Basic (.bas) If this option is selected, a copy of the header file will be created with a .bas file extension.
- Java (.properties) If this option is selected, a copy of the header file will be created with a .properties file extension.
- Delphi Pascal (.inc) If this option is selected, a copy of the header file will be created with an .inc file extension.
- On the right side of the dialog, select the header file(s) to be exported.
- Click the Browse button and select the location where the exported file(s) will be sent.
- Click Export.
- (Optional) If the file(s) are not in a shared location where the developer can retrieve them, you need to copy the exported files(s) from that location and send them to the developer.
Note: For more information see About Header Files.
WHAT'S NEXT?
In addition to providing the developer with a copy of the header file, you need to build the output for the target and provide the developer with a copy of the output files. Then, after the developer "hooks" the CSH on the software end and creates a new "build" of the software application, you need to install that build so that you can test the CSH.
See Also
Open topic with navigation