GUICtrlSetState($controlID, $GUI_ONTOP) Doesn't set on top

[jmon]

GUICtrlSetState($controlID, $GUI_ONTOP) Doesn't set the control on top of others. This constant doesn't seem to do anything.
The problem has been tested and discussed here:​http://www.autoitscript.com/forum/topic/146182-solved-change-z-ordering-of-controls/#entry1034615

Example:

#include <GUIConstantsEx.au3>

$GUI = GUICreate("Test", 800, 600)
GUISetState()

$LABEL1 = GUICtrlCreateLabel("under", 20, 20, 500, 300)
GUICtrlSetBkColor(-1, 0xFF0000)
$LABEL2 = GUICtrlCreateLabel("above", 40, 60, 500, 300)
GUICtrlSetBkColor(-1, 0x00FF00)

GUICtrlSetState($LABEL1, $GUI_ONTOP)

Do
Sleep(50)
Until GUIGetMsg() = -3
Exit

[czardas]

I searched hard to find a link I read about this recently. Although I couldn't find it, I I found this instead which may be more relevant.

​http://msdn.microsoft.com/en-us/library/microsoft.visualbasic.compatibility.vb6.support.zorder%28v=vs.100%29.aspx

"In Visual Basic 6.0, the ZOrder method was used to specify the layering of controls; in Visual Basic 2010 .it is replaced by the BringToFront and SendToBack methods. This function is used by the upgrade tools to map between the methods."

I'm not sure, but this may help to explain why $GUI_ONTOP appears to be not functioning.

[trancexx]

$GUI_ONTOP does what it's docummented that it does. There is no bug here.
Documentation says that control will get to the top of z-order. By default if the control is on top, it's the closest to the parent window (GUI) and it's therefore covered by all other controls being lower down the z-order.

On the other hand, for example, if the GUI would have WS_EX_COMPOSITED ex-style, you would see different effect (also docummented).

[Jon]

Fixed by revision [10301] in version: 3.3.13.2