Can this one be treated as double click event handler on listview?

[lightbringer]

I am doing some practice on AutoIt about GUI. Suddenly I countered something that looks like a double click event handler on a list view

Here's the code:

#include <misc.au3>
#include <GUIConstantsEx.au3>
#include <GUIListView.au3>
Func createGUI()
   Global $main = GUICreate("", 500, 500)
   Local $displayLink = GUICtrlCreateListView("", 25, 25, 450, 300, BitOR($LVS_EDITLABELS, $LVS_REPORT))
   _GUICtrlListView_SetExtendedListViewStyle($displayLink, $LVS_EX_GRIDLINES)
   
   _GUICtrlListView_InsertColumn($displayLink, 0, "Index", 50, 2)
   _GUICtrlListView_InsertColumn($displayLink, 1, "Link", 326, 2)
   _GUICtrlListView_InsertColumn($displayLink, 2, "Status", 70, 2)   
   _GUICtrlListView_AddItem($displayLink, "a|b|c")   
   GUISetState(@SW_SHOW)   
   Do
      if _IsPressed(1) Then handleMouseClick()
   Until GUIGetMsg() = $GUI_EVENT_CLOSE
EndFunc

Func handleMouseClick()
   local $pos = GUIGetCursorInfo($main)
      msgBox("", "", $pos[0] & " " & $pos[1])
   Return
EndFunc

createGUI()

note that there must be a double click if you want to have the position of the cursor inside the listview, outside that area you only need 1.

can anyone explain that to me?

[Melba23]

lightbringer,

I have always found it advisable to use doubleclicks when using handlers to interact with ListViews as the ListView itself often appears to eat the first click internally to act as the item selection. That seems to be the case here.

If you want a rather more elegant way to handle clicks and doubleclicks on ListViews, you might like to take a look here. Intercepting the click earlier via the Windows message queue does seem to reduce, but not entirely remove, the problem.