supersonic

I thank you for the feedback, however it is beyond me.... Is there "the" one/correct structure (for 32 and 64 bit)?

Sorry to post again in this old thread, but I needed the mentioned structure again. This time for a TreeView - and - because I used AutoIt 3.3.14.5 - ran into the same error AGAIN. 😉 I followed the thread to the end and have to note for AutoIt 3.3.16.1 that for '$tagNMLVKEYDOWN' or '$tagNMTVKEYDOWN' the following is defined: Global Const $tagNMLVKEYDOWN = $tagNMHDR & ";align 2;word VKey;uint Flags" Global Const $tagNMTVKEYDOWN = $tagNMHDR & ";align 2;word VKey;uint Flags" Is this finally correct after all? Or is: $tagNMHDR & ";word VKey;align 2;uint Flags" "more correct"? And if yes: Why resp. where can this be understood (e.g. MSDN)?

Currently I have something like this: ... $hBitmap = _GDIPlus_BitmapCreateFromHBITMAP($aDllCall[0]) $hBitmapResized = _GDIPlus_ImageResize($hBitmap, $iResizeWidth, $iResizeHeight, $GDIP_INTERPOLATIONMODE_NEARESTNEIGHBOR) _GDIPlus_ImageSaveToFileEx($hBitmapResized, $sPathFile, _GDIPlus_EncodersGetCLSID("PNG")) ... $hFile = FileOpen($aTest[0], $FO_BINARY) If ($hFile <> -1) Then $sData = FileRead($hFile) If (Not @error) Then ... EndIf FileClose($hFile) ; !!! EndIf ... I'm looking for something like that: ... $hBitmap = _GDIPlus_BitmapCreateFromHBITMAP($aDllCall[0]) $hBitmapResized = _GDIPlus_ImageResize($hBitmap, $iResizeWidth, $iResizeHeight, $GDIP_INTERPOLATIONMODE_NEARESTNEIGHBOR) $hPNG = _GDIPlus_ConvertBitmapToPNG($hBitmapResized) $sPNG = _GDIPlus_PNGToString($hPNG) ... ... to avoid creating/reading a file.

This is pretty cool! Could the function _WriteImageToText() be extended so that a bitmap is first converted to PNG and then saved?

I wish it was that simple... My "favorit" would only work if GUIDelete() actually returned 1 on success - at least that's how it's described in the help. In my attempts GUIDelete() always returns 0. An bug/error? At the moment I use: $__g_hGUI = GUIDelete($__g_hGUI) * 0 ; Forcing the variable always to be zero in any case. WM_COMMAND and WM_NOTIFY still triggers if a window handle/pointer variable is an integer (-1, 1, ...) - this is what I observe...

At least I'm not the only one who had such a "problem", and somehow satisfying that it is solved in the same way I wish _all_ functions like *Shutdown*(), *Destroy*(), *Delete*(), *Close*(), ... set IDs or handles to zero automatically - but in the end it's the care or responsibility of each scripter Regarding GUIDelete(), this is my favorite: $__g_hGUI = GUIDelete($__g_hGUI) - 1 If all goes well the variable is set to zero, if not you can check the variable against -1. In the end it is not a handle/pointer anymore.

I have found a solution myself: Although the GUI has been deleted with GUIDelete(), I additionally had to set the GUI variable to zero ($hGUI = 0). Without this WM_NOTIFY still interfered.

I have a sub-GUI with a strange behavior. This sub-GUI for a POS system is called from time to time within the main-GUI. The _first_ time it is called it is displayed completely with all controls - all controls are also fully functional (WM_COMMAND, WM_NOTIFY). With each further call of this GUI only the first 4-5 controls are created, following controls fail (GUICtrlCreate*() = 0). From the second call on, the last successfully created control ID is always 119. This should still be far away from the internal AutoIt limitations.... The affected GUI is always deleted after use with GUIDelete() and everything else is cleaned up afterwards as well... I would like to provide a test script, but the script is very very large and builds completely on external applications - a call without these applications is almost not possible. Has anyone observed such behavior before? Or even found a workaround? ( Edit: Currently I use AutoIt 3.3.14.5 on Windows 10. )

Great! Perhaps this "rewrite" deserves its own topic?

Definitely a good way to start. A COM error handler is mandatory - just my 2 cents. I put all constants into a seperate AU3 in order to not collide with AutoIt's own "ExcelConstants.au3" - sooner or later...

@water That would be great!

Wow! Thanks for sharing 😀 Can you provide a ListView example with 10+ columns and at least 1000 rows, please?

Thank you, sir, for providing the FreeBasic source!

Nice share! Any reservations about the publication of the FreeBasic code? That would be awesome...

@pixelsearch ... and all others involved: Thank you so much - I really appreciate your effort. I have very often wondered if or how to implement such functionality at all. All thumbs up! ☺️