Matrix mvBlueFOX3 User Manual

Figure 3: wxPropView - LastResult property
18.1.2 Using the result of the code generator in an application
Each header file generated by the code generator will include
"mvIMPACT_CPP/mvIMPACT_acquire.h" thus when an application is compiled with files that
have been automatically generated these header files must have access to this file. This can easily
achieved by appropriately settings up the build environment / Makefile.
To avoid problems of multiple includes the file will use an include guard build from the file name.
Within each header file the generated data types will reside in a sub namespace of
"mvIMPACT::acquire" in order to avoid name clashes when working with several different created
files in the same application. The namespace will automatically be generated from the ModelName
tag and the file version tags in the devices GenICam XML file and the interface layout. For a device
with a ModelName tag mvBlueIntelligentDevice and a file version of 1.1.0 something like this will
be created:
namespace mvIMPACT {
namespace acquire {
namespace DeviceSpecific { // the name of the interface layout used during the process of code creation
namespace MATRIX_VISION_mvBlueIntelligentDevice_1 { // this name will be constructed from the version and product
// information that comes with the GenICam XML file. As defined
// by the GenICam standard, different major versions of a devices
// XML file may not be compatible thus different interface files should be created here
18 Use cases
148

Matrix mvBlueFOX3 Specifications

General

Brand	Matrix
Model	mvBlueFOX3
Category	Digital Camera
Language	English