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

Properties

 
Properties
1

Name

1. Name
Name of the GL-Studio object. Must be unique.
 
2

File

2. File
Model file to be parsed and used.
Reload the .gls file for updating the interface.
Call the GL-Studio editor (tries to open/edit the file from a command line. gls extension must be bounded with GL-Studio)
 
3

Source Code

3. Source Code
Directory where GL-Studio generates all the files for the current model.
 
4

Cycling

4. Cycling
Select from the list the appropriate frequency for the object. As it is a graphic object, the higher the frequency the smoother the result.
 
Fixed Hz: when checked, the selected frequency is not according to the RTC but according to the wall clock.
With a fixed frequency, even if the simulation engine is accelerated or slowed down, the number of calls per seconds will remain the same.
 
5

Regenerate Code

5. Regenerate Code
Force GL-Studio to produce a new fresh code for the associated mdl model.
 
6

Disabled

6. Disabled
Exclude the GL-Studio object from the code generation.
Disabled GL-Studio object will not be included into the items using it (entities but not only) without the need to remove it from all users.
Disabling is error prone while removing might leave dangled pointers.
 
7

Sub Models

7. Sub Models
If the current GL-Studio model embed some other models, they will be listed here. Sub models can also be accessed from the source code, so, it is a good hint to get them listed here instead of checking the GL-Studio editor.
 
8

Interface

8. Interface
vsTASKER parses the .gls file and tries to extract all Properties and Callbacks.
Not all of them shall be used.
 
9

Code

9. Code
This part is the vsTASKER interface code between the data belonging to the simulation engine and the objects pertaining to the GL-Studio model.
 
The Definition panel is used to declare any variable that will be used inside the runtime part (they will persist for all the time of the simulation).
          You shall define here user interface variables (//&&) for design and runtime setup.
 
The Initialization part is called at RESET phase can be used to initialize the GL-Studio object as well as local variables.
 
The Runtime part is called before each call to the GL-Studio object update function. You can use the local variables to set the object variables.
Use O: to access any property or callback defined into the GL-Studio object.
 
The Clean part is called at simulation end (CLEAN phase).
 
10

Help

10. Help
Any description of the GL-Studio object can be put here and will be used for the automatic document generation (see Make Documents)