Raedor/Sandbox – User

From Bohemia Interactive Community
Jump to navigation Jump to search
No edit summary
(RscControlsGroups ...)
Line 9: Line 9:
List of known problems/inconsistencies
List of known problems/inconsistencies


==Config Params==
==Config Params and Classes==


===Displays===
===Displays===
Line 17: Line 17:
===Controls===
===Controls===


* moving: Seems to have no effect on RscActiveTexts
* class ControlsBackground seems to be not working for RscControlsGroups
* moving: Seems to have no effect on RscActiveTexts, RscControlsGroups
* moveOnEdges: What does this do? -- Seems to be used only with maps.
* moveOnEdges: What does this do? -- Seems to be used only with maps.



Revision as of 13:44, 9 October 2008


What makes the difference for controls is the "type" entry. We have 30(+?) different types. Also important is the "style" entry, I think we better use the base classes as name for them or the macro for the type number from resincl instead of the clean type number, as it is easier to read then.

I think it would be good if we write some info about each control type/style and which combinations are possible (e.g. button + picture is not).


List of known problems/inconsistencies

Config Params and Classes

Displays

  • movingEnable: Nobody knows what this does

Controls

  • class ControlsBackground seems to be not working for RscControlsGroups
  • moving: Seems to have no effect on RscActiveTexts, RscControlsGroups
  • moveOnEdges: What does this do? -- Seems to be used only with maps.


Control commands

ctrlSetFade

  • no effect on maps

Control Eventhandlers

mouseEnter/Exit/Moving/Hold

  • For static texts (and static pictures) it seems to trigger only when you set the focus on it