Use input control as fake label to avoid flickering on update

[KaFu 185]

One more work-around for the old problem :). Update procedure must be quite different for these two control types under the hood.

 

#include <WindowsConstants.au3>
#include <EditConstants.au3>

HotKeySet("{ESC}", "_Exit")

GUICreate("My GUI")
GUISetBkColor(0x00ff00)

$c_Label = GUICtrlCreateLabel(0, 10, 10, 200, 20)

$c_Input = GUICtrlCreateInput(0, 10, 60, 200, 20, $ES_READONLY, $WS_EX_TRANSPARENT)
GUICtrlSetBkColor(-1, 0x00ff00)
GUICtrlSetCursor(-1, 2) ; Arrow

GUISetState(@SW_SHOW)

While 1
    GUICtrlSetData($c_Label, TimerInit())
    GUICtrlSetData($c_Input, TimerInit())
WEnd

Func _Exit()
    Exit
EndFunc   ;==>_Exit

 

Edited July 21, 2015 by KaFu

[UEZ 1,081]

Nice catch KaFu

Here an additional one:

#include <WindowsConstants.au3>
#include <EditConstants.au3>

HotKeySet("{ESC}", "_Exit")

GUICreate("My GUI", 300, 200, -1, -1, -1, BitOR($WS_EX_LAYERED, $WS_EX_COMPOSITED))
GUISetBkColor(0x00ff00)

$c_Label = GUICtrlCreateLabel(0, 10, 10, 200, 20)

$c_Input = GUICtrlCreateInput(0, 10, 60, 200, 20) ;, $ES_READONLY, $WS_EX_TRANSPARENT)
GUICtrlSetBkColor(-1, 0x00ff00)
GUICtrlSetCursor(-1, 2) ; Arrow

GUISetState(@SW_SHOW)

While 1
    GUICtrlSetData($c_Label, TimerInit())
    GUICtrlSetData($c_Input, TimerInit())
WEnd

Func _Exit()
    Exit
EndFunc   ;==>_Exit

 

[BrewManNH 1,100]

Really great idea, at least this way you wouldn't have to add code to check to see if the value has changed just to avoid the flickering.

When you click on the title bar it freezes the display, and one thing I noticed when I changed the code to what's below, that the Input control almost always has an earlier TimerDiff value than the label does even though it's in the script after the update to the label.

While 1
    GUICtrlSetData($c_Label, TimerDiff($Timer))
    GUICtrlSetData($c_Input, TimerDiff($Timer))
WEnd

 

[coffeeturtle 4]

Nice catch KaFu

Here an additional one:

Hi UEZ.  Why does this work: BitOR($WS_EX_LAYERED, $WS_EX_COMPOSITED))  ???

 

Thanks to you both!

[UEZ 1,081]

According to MS

WS_EX_COMPOSITED (0x02000000):

Paints all descendants of a window in bottom-to-top painting order using double-buffering. For more information, see Remarks. This cannot be used if the window has a class style of either CS_OWNDC or CS_CLASSDC.

Windows 2000:  This style is not supported.

WS_EX_COMPOSITED works by forcing child windows to draw back to front and by double buffering them; however, the double buffering used by WS_EX_COMPOSITED for the child windows conflicts with the double buffering used by WS_EX_LAYERED windows and DWM so it does not remove the flicker in those contexts.

 

Unfortunately, this means that your composited test application flickers with DWM turned on but not with DWM turned off.

 

Narrowing the area invalidated to the minimum necessary and using WS_CLIPCHILDREN and WS_CLIPSIBLINGS appropriately can help reduce the amount of flicker.

    WS_EX_COMPOSITED does not eliminate flashing on Windows 8 with DWM (Desktop Windows Manager)

WS_EX_COMPOSITED appears to work fine until you minimize then restore the window.  Then the child windows will start flashing.  To avoid flashing do not set the WS_EX_COMPOSITED style, do your own double buffering, and ignore the WM_ERASEBKGND message.  This is a know issue with Microsoft. 

 

WS_EX_LAYERED (0x00080000):

The window is a layered window. This style cannot be used if the window has a class style of either CS_OWNDC or CS_CLASSDC.

Windows 8:  The WS_EX_LAYERED style is supported for top-level windows and child windows. Previous Windows versions support WS_EX_LAYERED only for top-level windows.

WS_EX_LAYERED windows and all windows when DWM is enabled are rendered into an offscreen buffer and that buffer is then rendered to the screen.  WM_PAINT messages can be skipped to update the onscreen buffer so long as the offscreen buffer is valid.

 

Maybe this helps a little bit.

[coffeeturtle 4]

Thank you for the thorough answer!

Appreciate your input as always!