findDisplay – Talk
Jump to navigation
Jump to search
I wrote this to help me see what I'm clicking on:
disableserialization;
for [{_i = 0}, {_i < 10000}, {_i = _i + 1}] do {
if (str (finddisplay _i) != "no display") then {
//player sidechat str (finddisplay _i);
for [{_j = 0}, {_j < 10000}, {_j = _j + 1}] do {
if (str (finddisplay _i displayctrl _j) != "no control") then {
//player sidechat str (finddisplay _i displayctrl _j);
_ctrl = finddisplay _i displayctrl _j;
_ctrl ctrlSetEventHandler ["mousebuttondown", "player sidechat str _this"];
};
};
};
};
--Doolittle 19:06, 10 October 2009 (CEST)
so called 'primary display' is misleading.
idd 46 is IDD_MISSION
ie the in-game mission screen. It has no more significance as being 'the primary display' than a chunk of cheese. It is just one of many 'primary' displays. When in the main screens, out of a game, they too are 'primary displays' (idd 0 IDD_MAIN) etc. It's not appropriate to call the mission display anything other than, mission display. Primary displays in less well understood config.cpp's are (mostly) de-facto.
Mikero (nee Ook?) 09:46, 2 July 2011 (CEST)