User customisation¶
The program defaults for the tractrix module are first loaded from the file geoschlepp.dflt in <InstallPath>u\1600\geo\geoschlepp\dflt. This file should be not be modified here. Customisations made here, in spite of being preferred, may be reset with the next software update. A software update can possibly replace the module file geoschlepp.dflt at this location.
Instead customisations should be made in the customer geoschlepp.dflt file under $KUNDE\geoschlepp\dflt. The entries from $KUNDE\geoschlepp\dflt\geoschlepp.dflt supersede the entries from <InstallPath>u\1600\geo\geoschlepp\dflt.
The variable $KUNDE in this path is replaced with the environment variable KUNDE. In case the environment variable KUNDE is not defined, $KUNDE from ..\Users\<USERNAME>\Documents will replace it and the customer geoschlepp.dflt from ..\Users\<USERNAME>\Documents\geoschlepp\dflt will be assumed.
The environment variable KUNDE can refer to a network path. In this way, the settings in the customer geoschlepp.dflt can be adopted by several users. Even with a change in computer or the installation of a new program version, it is simple to apply the old default settings.
In your customer geoschlepp.dflt file, you only need to assign values to the variables if they differ from the values in <InstallPath>u\1600\geo\geoschlepp\dflt\geoschlepp.dflt. Comment lines are started with a "#".
Variables¶
LOCAL NAME¶
You can assign the variable LOCAL NAME in geoschlepp.dflt a country code.
For English select
LOCAL NAME = en
and for German
LOCAL NAME = de
In case the variable LOCAL NAME in geoschlepp.dflt is not defined, the country setting from ELITECAD will be used.
Using the variable LOCAL NAME you can, for example, set the menu language of the program. Currently only English and German are supported. The default language is German. In case the menu language of the ELITECAD Module Tractrix Curve is not in your desired language, you can use the variable LOCAL NAME to select a different menu language.
VEHICLE FILE PATH N¶
Use the VEHICLE FILE PATH N variable in geoschlepp.dflt to assign names (last directory in the path) and the associated paths to the tabs in the vehicle selection. The "N" in VEHICLE FILE PATH N is a placeholder for a whole number. The numbers in VEHICLE FILE PATH N must start with 1 and count up in order from there.
If, for example, in the geoschlepp.dflt module for the vehicle definitions, the following path is defined:
VEHICLE FILE PATH 1 = ...
VEHICLE FILE PATH 2 = ...
VEHICLE FILE PATH 3 = ...
VEHICLE FILE PATH 4 = ...
and you defined the path in the customer geoschlepp.dflt:
VEHICLE FILE PATH 4 = ...
VEHICLE FILE PATH 5 = ...
VEHICLE FILE PATH 6 = ...
Then the path designation from VEHICLE FILE PATH 4 of the customer geoschlepp.dflt will replace the path of the variable of the same name in the module geoschlepp.dflt.
2 additional paths and tabs will be defined with VEHICLE FILE PATH 5 and VEHICLE FILE PATH 6 from the customer geoschlepp.dflt.
The path assigned to the variable VEHICLE FILE PATH N, may begin with the variables $GEODIR and $KUNDE. The variable $GEODIR refers to <InstallPath>u\1600\geo and the variable $KUNDE is superseded by the environment variable KUNDE. In case the environment variable KUNDE is not defined, $KUNDE from ..\Users\<USERNAME>\Documents will replace it.
Proprietary vehicle definitions should not be stored in $GEODIR. This directory is used for the program standards. Proprietary vehicle definitions should be stored under the paths with the variable $KUNDE. You can, of course, also assign the variable VEHICLE FILE PATH N an absolute path.
Create user-defined vehicle¶
To create your own vehicle definitions, copy, for example, the def-file that has the closest match to your new vehicle in terms of type, from $GEODIR/geoschlepp/vehicles/FGSV to one of your (VEHICLE FILE PATH 4 to VEHICLE FILE PATH N) vehicle paths defined in the customer “geoschlepp.dflt. There you can rename this file and modify the content with an editor. The vehicle definitions under $GEODIR/geoschlepp/vehicles/FGSV are provided with detailed comments for better understanding. Further information about the file format can be found in the vehicle file structure chapter. Also remember to provide the corresponding BMPs or JPGs in the specified directory for the preview.
Alternatively, you can also temporarily adapt an existing vehicle definition using the vehicle dimensions parameter window. Then a vehicle.def file with these settings can be found under ..\Users\<USERNAME>\AppData\Roaming.geo\geoschlepp. This file can then be copied to the designated directory and renamed there. The corresponding BMPs or JPGs for these vehicles should also be provided. The paths to these vehicle images may have to be adjusted in the vehicle def-file*.
© GEO DIGITAL GmbH