vsTASKER 7 User Manual
×
Menu
Index

Settings

 
Features are defined outside vsTASKER using specific DLL.
They are structured into /Feature directory. They can be included or excluded from the product environment.
 
Settings
1

Feature List

1. Feature List
Uncheck a Feature to keep it in the file but forbid it to be loaded into vsTASKER.
To reduce the size of the vsTASKER memory footprint, uncheck the feature you will not use in your databases.
 
2

Update

2.
Use this button to update the selected Feature (from the left list) with the data from the Item Properties block.
 
3

GUI Name

3. GUI Name
Specify here the name to be used in the menus, for the selected Feature entry.
 
4

DLL Name

4. DLL Name
Name of the DLL in the /Features directory (needless to add the file extension).
The GUI will load the <name>M.dll interface that handle all windows while the <name>.dll (compiled with VisualStudio) will be handling the data objects. The <name>X.dll will be used for drawing the feature onto the OpenGL device.
 
5

Lib Name

5. Lib Name
Name of the library that will be produced into /lib/vcxx.
This lib will automatically be added into the makefile produced by vsTASKER to compile a simulation engine produced with a database using the corresponding Feature.
 
6

Include File

6. Include File
Name of the include file in /Feature/Include
 
7

Add

7.
Add a new Feature (entry) into the list.
This capability is only reserved for advanced users who are expanding the GUI using their own CodeGear C++ Builder IDE.
8

Delete

8.
Suppress the selected user added Feature.
This capability is only reserved for advanced users who are expanding the GUI using their own CodeGear C++ Builder IDE.
9

Activate on/off

9. Activate on/off
Use these buttons to tick/activate all or none of the Feature Manager.
When a Manager is not ticked, it will not be available next time vsTASKER will be started. That means the associated DLL will not be loaded and the corresponding button in the toolbar will be disabled. When a database is loaded, if a Manager is disabled, all corresponding Features of the database will not be loaded. This can be useful when working with databases that do not have Features. Starting vsTASKER will be faster as Feature DLL will not be loaded. Memory footprint will also be reduced.
Do not forget to activate some or all Managers if you intend to use Features.
10

Save

10. Save
Fix the configuration on a file so that next time vsTASKER is loaded, only the selected Feature DLLs will be loaded.
This capability is only reserved for advanced users who are expanding the GUI using their own CodeGear C++ Builder IDE.