Listview flicker when in tab item

[JohnOne]

Then up to now, the simplest and fastest is.

Locking the GUI in tandem with using _GUICtrlListView_BeginUpdate and _GUICtrlListView_EndUpdate.

Func PopulateLV()
    Local $hTimer = TimerInit()
    _GUICtrlListView_BeginUpdate ($hLV)
    GUISetState(@SW_LOCK)
    For $i = 0 To 1000
        GUICtrlCreateListViewItem($sLVI, $hLV)
    Next
    GUISetState(@SW_UNLOCK)
    _GUICtrlListView_EndUpdate( $hLV)
    MsgBox(0, "Time Difference", TimerDiff($hTimer) / 1000)
EndFunc   ;==>PopulateLV

EDIT:

Adding the update function halves the timer at least.

Edited February 23, 2015 by JohnOne

[mLipok]

Interesting as it may accelerate in the case of not using the TAB.

I have not tried yet but can not wait until I do the test on several of my programs.

[JohnOne]

Wonder if anyone knows why this does not work?

Func PopulateLV()
    Local $hTimer = TimerInit()
    _GUICtrlListView_BeginUpdate($hLV)
    ;GUISetState(@SW_LOCK)
    $hwnh = _WinAPI_GetDlgItem($Gui, $hLV) ; Get handle of ListView
    _WinAPI_LockWindowUpdate($hwnh) ; Lock ListView 
    For $i = 0 To 1000
        GUICtrlCreateListViewItem($sLVI, $hLV)
    Next
    _WinAPI_LockWindowUpdate(Null)
    ;GUISetState(@SW_UNLOCK)
    _GUICtrlListView_EndUpdate($hLV)
    MsgBox(0, "Time Difference", TimerDiff($hTimer))
EndFunc   ;==>PopulateLV

Just passing the handle of listview instead of parent gui.

[kylomas]

_WinAPI_LockWindowUpdate wants the handle from GuiCreate not the control

[Kilmatead]

I'm wondering now if _WinAPI_LockWindowUpdate and GUISetState(@SW_LOCK) are actually the same thing.

 

I started using the API version in general because it works reliably for all windows (especially useful for hiding the ugly "send" machinations applied to 3rd-party programmes), and (with the additions of regional invalidation) allows a more granular control over what's happening.  Also, whenever I use the API I'm learning something - using native commands is more for "general" use.  90% of the UDF's such as  _GUICtrlListView_BeginUpdate are really just wrappers for direct API calls anyway, so it's useful to dig through them and learn "how" they do what they do - which things like GUISetState hide for the sake of simplicity.

[JohnOne]

_WinAPI_LockWindowUpdate wants the handle from GuiCreate not the control

 

I'm not sure that is entirely true, as far as windows OS is concerned, all "controls" are just child windows.

[JohnOne]

Found another way to make it even quicker 90% of the time, maybe it's skipping an API call.

Func PopulateLV()
    Local $hTimer = TimerInit()
    _GUICtrlListView_BeginUpdate($hLV)
    _SendMessage($Gui, $WM_SETREDRAW, False)
    For $i = 0 To 1000
        GUICtrlCreateListViewItem($sLVI, $hLV)
    Next
    _SendMessage($Gui, $WM_SETREDRAW, True)
    _GUICtrlListView_EndUpdate($hLV)
    MsgBox(0, "Time Difference", TimerDiff($hTimer))
EndFunc   ;==>PopulateLV

[kylomas]

I'm not sure that is entirely true, as far as windows OS is concerned, all "controls" are just child windows.

 

You're right, have'nt used the function enough (or at all) to test...

[mLipok]

indeed faster