vsTASKER 7 User Manual
×
Menu
Index
Search
 
   
   
   
 
Copyright VirtualSim 2004-2020 - All rights reserved

Properties

 
Properties
1

Name

1. Name
Name of the GdiOsg. Must be unique whatever its type.
vsTASKER will generate a class whose name will be <Name>_Spt. For the moment, this class will inherit from Vt_Sprite class.
Any Sprite can be accessed using its name in a generated union named s.
 
2

Keyboard Handler

2. Keyboard Handler
Generates a keyboard handler for the user to use.
 
3

GDI Definition

3. GDI Definition
Call the GDI property window.
 

  • Initialization

By default, the slct_ent pointer is set with the camera hook value (5).
NULL if cam_hook is empty.
 

  • Draw

This part can be modified. The code is defaulting a behavior for Terrain Centered and Entity Hook modes.
It can be clean to put user code in the cam_mode == 0 block. By doing so, activating it would be done from the GdiOsg drop box itself.
In this part, the code is only setting the camera position and orientation.
It is called at maximum frequency.
User can add whatever OSG code it needs.
If the code that must be added in this part is quite big and is mostly developed and debug in Visual Studio, it is advisable to put it into the file myOsgCode.cpp in D:\VirtualSim\vsTasker\7\Sprite\GdiOsg. This code is automatically inserted into the Draw part.
 

  • Mouse

Put here the code that reacts to the mouse input (position and button) when used over the GdiOsg vindow.
Use mouse.button to get the actual depressed button.
By default, the Mouse inner part takes care of the mouse to control the camera position using ms_azim and ms_pitch variables.