import (Config): Difference between revisions
m (→from keyword: Updated example so it does not look like it can be used outside of description.ext) |
m (clarification) |
||
Line 3: | Line 3: | ||
== <b>import</b> keyword == | == <b>import</b> keyword == | ||
The <tt>import</tt> keyword | The <tt>import</tt> keyword '''can only be used''' in [[description.ext | mission config]], pretty much like <tt>class</tt> keyword, in order to import a class from main config into mission config. Useful for UI creation as UI controls have a lot of properties which are already defined in main config, so if only some tweaks are required, it could be easily done after importing the class. | ||
The keyword tells parser to copy given class during parsing of the mission config so the imported class will be placed where the keyword <tt>import</tt> was placed. For example if one needs to inherit from <tt>RscText</tt>, the <tt>import RscText;</tt> should precede the inheritance: | The keyword tells parser to copy given class during parsing of the mission config so the imported class will be placed where the keyword <tt>import</tt> was placed. For example if one needs to inherit from <tt>RscText</tt>, the <tt>import RscText;</tt> should precede the inheritance: |
Revision as of 14:05, 23 November 2020
import keyword
The import keyword can only be used in mission config, pretty much like class keyword, in order to import a class from main config into mission config. Useful for UI creation as UI controls have a lot of properties which are already defined in main config, so if only some tweaks are required, it could be easily done after importing the class.
The keyword tells parser to copy given class during parsing of the mission config so the imported class will be placed where the keyword import was placed. For example if one needs to inherit from RscText, the import RscText; should precede the inheritance:
import RscText;
class MyText: RscText
{
...
};
The import keyword tells the engine to look for the base class in main config, which means classes in base directory. However, it is also possible to look in other dirs using from keyword.
from keyword
The from keyword is used to indicate specific config path from where the class should be imported. For example, one can do things like this, not that one will even need this particular usage:
import Default from CfgTasks;
class CfgTasks
{
class MyAwesomeTask: Default
{
name = "My Awesome Task";
};
};
Modifying properties
The properties override is done in the same way it is done for modding.
import RscText;
class MyText: RscText
{
style = 2;
};
When property is inside another class, this is how it could be done:
import RscStructuredText;
class MyText: RscStructuredText
{
class Attributes: Attributes
{
align = "right";
};
};
Here is example of overriding the color of vignette:
import RscDisplayEmpty;
class MyRscDisplayEmpty: RscDisplayEmpty
{
class controls: controls
{
class CA_Vignette: CA_Vignette
{
colorText[] = {1,0,0,1};
};
};
};
And the result, after executing findDisplay 46 createDisplay "MyRscDisplayEmpty";
in debug console:
Checking imported classes
In debug console type utils 2, LOCAL EXEC, and select mission config from drop down menu. The mission config will be displayed including imported classes