Leaderboard

... lets do some marketing first: pardon the image size of 225% scale on another monitor The idea is to have some DPI awareness in our GUIs and with this all you have to do is prefix "_HiDpi_" to your current code. Simple. This version ( HiDpi v. 0.2023.7.29(b) stable.zip ) is stable but only system aware. ( pictures above ) This next version ( HiDpi v. 0.2023.8.3(a) under development.zip ) is what I've got so far in regards of per-monitor awareness This one ( HiDpi v. 0.2023.8.4(ResizeTestbed) under development.zip ) is for the brave of heart. I'm looking for ideas. This is a testbed for anyone wanting to contribute regarding resizing controls. I have now started to use _WinAPI_DPI.au3 because I feel that this UDF is ready for that UDF. Therefore, too many and too big files for copy and paste. And that is good. Means that the UDF is getting closer to stable. FAQ (of sorts) Q: When did you come up with this ? A: Never. These are helper functions for _WinAPI_SetDPIAwareness.au3 but I did not get to finish. Nonetheless it's functional as is and applies to most of the cases in need of DPI awareness. Per-monitor would need more involved coding and I only have so much time and know how for now. Q: Will you open a ticket and ask to be included in the standard UDFs ? A: No. This is a just for now. Eventually the functionality would be a standard feature without the need of this. Q: Will you add ... A: Only in the case that either, I realize is needed and code it or, you code it and ask to be included in this bundle of functions UDF Q: This is not working ... A: The best way to go about a problem with this code is to open it's own thread in GUI Help and Support and post there with a mention of me. I'll read and answer there. Q: Are you going to share "logo4.gif", "SampleAVI.avi", etc. A: You are right. I forgot to say that the example file will work as expected if created in "..\Examples\GUI\HiDpi_v_n.n.n.n\", as a subfolder of where "SampleControls.au3" is at. There it will find all the files required for the example. Because after all, this example is that example but "_HiDpi_fied" ( so to say ). Q: Is there a tool that will magically update all my old scripts ? A: I've posted a script to get you closer but is not magical. Should work just fine for simple GUIs. Q: Are you going to work on a Per-monitor version ? A: yes, as time permits.

Latest update just released. See below for change log.

Too many sites like this generate versions and URLs via scripts. Sad but true 😠 For example try this direcy link to .zip archive https://download-chromium.appspot.com/dl/Win

Or maybe something like: #include <File.au3> ConsoleWrite(_UniqueFileName(@ScriptDir & "\Filename.txt") & @CRLF) Func _UniqueFileName($_sFilePath) If FileExists($_sFilePath) = 0 Then Return $_sFilePath Local $sDrive = "", $sDir = "", $sFileName = "", $sExtension = "" Local $aPathSplit = _PathSplit($_sFilePath, $sDrive, $sDir, $sFileName, $sExtension) Local $i = 1 While 1 $_sFilePath = $sDrive & $sDir & $sFileName & "-" & $i & $sExtension If FileExists($_sFilePath) = 0 Then Return $_sFilePath $i += 1 WEnd EndFunc

Thanks trancexx. Reading material:: https://en.wikipedia.org/wiki/Chunked_transfer_encoding

It's not flaw, everything is ok. If you look at the whole header you'll se that transfer-encoding is "chunked". That means the server sends data in chunks which are separated by separator and the whole transfer ends with zero size mark + double-@CRLF. Size is known in advance when Content-Length is specified as you show in your WinHttp example.