Altimeter

Open HMI/gls_altimeter database.

In Models, you will find the two GL-Studio components loaded (_adi & _altimeter).

These two components can be found in runtime/glstudio. You can open the .gls file to modify the content.

Each vsTASKER GL-Studio component encapsulates the graphical object itself. The component is able to parse the gls file to extract variables (properties) and callbacks.

Using graphical properties is straightforward as shown in the both components (see pane Code::Runtime of both _adi & _altimeter components).

In order for the graphical object to send callback event to vsTASKER, the following code must be added inside all GL-Studio object callback:

vt_rtc->raiseEvent(self->InstanceName(), T_Ptr, self);

and in file ….cpp, add the following:

#include <vt_rtc.h>

You can then compile the demo (force regenerate check button in each GL-Studio form force GL-Studio to regenerate the code of the object before vsTASKER compile it. It is not necessary to do so if the gls file is left untouched).

Load the simulation engine and start it.

Two little window will appear on the top left corner. Adi and Altimeter windows.

If you select player (Scenario::Scn::Player in Environment), you will see that Lgk logic behavior symbol is magenta (running).

Open it and start playing with knob and buttons of the Altimeter to see the effect on the two Actions.