Arma: GUI Configuration – Talk

From Bohemia Interactive Community
Jump to navigation Jump to search
No edit summary
m (wipe)
Tag: Blanking
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
This page seems to get very large. Maybe it should be splittet in more pages.
Im not very experienced with wiki editing, so maybe some 'admin' can do this ???
--[[User:HeliJunkie|HeliJunkie]] 21:31, 24 November 2008 (CET)


:I agree, it ''is'' pretty big. But I can't really think of a logical way to split it up...
:How about we make the (bigger) examples separate pages? --[[User:Kronzky|Kronzky]] 17:17, 25 November 2008 (CET)
::Maybe there can be a own page for each control, and only the links to the pages on this overview page?
::All pages should have the same suffix like "-control" or something like that. (HTML-control, StaticText-control....)
:: --[[User:HeliJunkie|HeliJunkie]] 13:47, 1 December 2008 (CET)
:::What about a Category: Dialog Control similar to the scripting commands where each command has its own page? --[[User:T D|T_D]] 15:44, 1 December 2008 (CET)
Sure, that would ''technically'' be the easiest way, but I'm not so crazy about that since, unlike commands, which are totally different from each other, controls share a lot of properties among each other, and a lot of definitions and explanations on the dialog page apply to several control types. This page is also somewhat of a mix between reference and tutorial (sort of like the [[Control Structures]] page), so you want to keep stuff together that's related, to make understanding the whole concept a bit easier.<BR>
I would much rather break it up ''hierarchically'' (i.e. have more general information on the main page, and deeper, more detailed information on a sub-page. That's why I suggested to split off the examples.)<BR>
IDEALLY though, if I had the time (or could find a volunteer) we should probably have only one big table listing the properties, rather than 10 different ones with 50% overlap. It just doesn't make sense listing 'IDC' or 'colorBackground' or 'x' & 'y' for each and every control, where they have the same function in every one of them.<BR>
Something like this:
{| border="1" align="center" cellpadding="3" cellspacing="0" |
! colspan="3" bgcolor="#bbbbff" | Properties
! colspan="6" bgcolor="#bbbbff" | Applies to
|-
! bgcolor="#ddddff" | Name
! bgcolor="#ddddff" | Type
! bgcolor="#ddddff" | Remark
! bgcolor="#ddddff" | ST
! bgcolor="#ddddff" | BU
! bgcolor="#ddddff" | AT
! bgcolor="#ddddff" | ST
! bgcolor="#ddddff" | TB
! bgcolor="#ddddff" | etc...
|-
| '''idc'''
| integer
| Unique ID number of this dialog.<br>Can be -1 if direct access to the dialog is not required.
| -
| X
| -
| -
| X
| .
|-
| '''colorBackground'''
| color array
| color of background.
| X
| -
| -
| -
| -
| .
|-
| '''text'''
| string
| default text
| X
| X
| X
| X
| -
| .
|-
|}
--[[User:Kronzky|Kronzky]] 21:49, 1 December 2008 (CET)
== movingEnable, moving, enableSimulation ==
The description of the ''movingEnable'' property is wrong:<br />
''movingEnable'' and ''moving'' are used to create dialogs that can be dragged just like windows. ''movingEnable'' is a property of dialogs whereas ''moving'' is a property of controls. Assuming both properties are present and non-zero, a dialog can be dragged by clicking the control with the ''moving'' property. It does not seem to matter whether this control is hidden by another control or not.<br />
''enableSimulation'' is used to specify whether the game continues while the dialog is open or not (in SP, haven't tested MP yet).
--[[User:Worldeater|Worldeater]] 03:58, 10 June 2009 (CEST)

Latest revision as of 13:33, 10 March 2020

Retrieved from "https://community.bistudio.com/wiki?title=Talk:Arma:_GUI_Configuration&oldid=148999"