![]() Can be -1 if no access is required from within a script.ĭuration of fade in effect when opening in seconds.ĭuration of fade out effect when closing in seconds.ĭuration the HUD is displayed after opening in seconds. Used with findDisplay to find the display. ![]() Additionally, their properties are different. HUDs are defined in the class RscTitles, unlike displays or dialogs which are root classes in the config file. When used on the mission display (Display #46) it simulates "Save and Exit" button from escape menu Predefined controls #define IDC_OK 1 #define IDC_CANCEL 2 #define IDC_AUTOCANCEL 3 #define IDC_ABORT 4 #define IDC_RESTART 5 #define IDC_USER_BUTTON 6 #define IDC_EXIT_TO_MAINė Exit Codeĭialog was closed with a positive outcomeĭialog was closed with a negative outcome List of all DialogControls-Objects type controls the last ones will on top of the first ones).Ĭontains class names of all foreground controls associated to this dialog. The sequence in which the controls are listed will decide their z-index (i.e. See User Interface Event HandlersĬontains class names of all background controls associated to this dialog. See User Interface Event HandlersĮxpression executed when the dialog is closed. ![]() Specifies whether the game continues while the dialog is shown or not.Įxpression executed when the dialog is opened. Specifies whether the dialog can be moved or not (if enabled one of the dialogs controls should have the moving property set to 1 so it becomes the "handle" the dialog can be moved with). 3 - ReadOnlyVerified - this does not allow to do anything either in deriving classes, and a CRC check will be performed.2 - ReadOnly - this does not allow to do anything in deriving classes.1 - ReadAndCreate - this only allows creating new properties.0 - ReadAndWrite - this is the default case where properties can still be added or overridden.Can be -1 if no access is required from within a script. They are usually used to simplify user interactions, through controls like buttons, list boxes and so on. ![]() Please check the command's biki page for detailed information.ĭisplays and dialogs are defined in the config file. Some of the commands have different effects. They are defined as classes in the missionConfigFile ( description.ext), campaignConfigFile ( Campaign Description.ext) or configFile ( config.cpp). Dialogs are one way to provide custom graphical user interface in your missions and allow interaction with the player as well as they are able to run code. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |