When designing a web page or some application pages, we often set font properties in one place, such as ** ‘Song Typeface’, so that the entire page or the entire project of hundreds of objects, display Chinese characters, will be song Typeface. At this point, if we need a particular object to be displayed as’ italic ‘**, simply set the font property to italic for that object independently.
This mechanism not only makes our design information more concise, but also enhances the readability, stability, efficiency and manageability of design information.
Similarly, in the TASKCTL design, there are mechanisms.
Learn defaults, inheritance, and overloading from code
Those attributes have default, inherited, and overloaded technical characteristics
In TASKCTL, there are a number of attributes for string groups and job nodes, but not all of them have this feature. How do we know in time which attributes have such technical characteristics? In fact, when designing with Designer, you can click on a job node in the flowchart and see the properties box to clear up which properties have default, inherited, and overloaded technical characteristics.
Learn more about the property box:
For attributes with technical characteristics such as inheritance, the flag label represents the source state of the current value of the attribute through the expansion of the attribute box. Vfinherit stands for inheritance; VfDefault indicates the default. VfSelf stands for custom, that is, overload.
There are some special uses for this technical feature in TASKCTL.
In fact, features like attribute inheritance in TASKCTL not only simplify code design and enhance code manageability, but also enable specific technical scenarios.