Leaderboard

Introduction In the course of my research for a project involving, among other things, the transfer of large amounts of data, I came across the BITS service and from that the idea for this UDF was born. For a brief overview, I'll quote from Microsoft's BITS website (https://docs.microsoft.com/en-us/windows/win32/bits/background-intelligent-transfer-service-portal). Availability 🛒 The BITS UDF can be downloaded from my GitHub repository: 🔗 https://github.com/DonChunior/BITS-UDF Comments 💬 Currently, only an alpha version of the UDF is available. This contains by and large the full functionality of the object interfaces, but still completely lacks error checking and handling. I will implement this in the upcoming beta version. Therefore I ask you to use the UDF only for testing purposes but not in productive code! Acknowledgment 🤝 Many thanks to @Nine and @Danyfirex. You helped me very well in solving some tricky problems.

I have no idea what these two functions do.. Please explain. Sample script direct from the help file: #include <GUIConstantsEx.au3> Example() Func Example() GUICreate("GUICtrlCreateDummy", 250, 200, 100, 200) GUISetBkColor(0x00E0FFFF) ; will change background color Local $idUser = GUICtrlCreateDummy() Local $idButton_Event = GUICtrlCreateButton("event", 75, 170, 70, 20) Local $idButton_Cancel = GUICtrlCreateButton("Cancel", 150, 170, 70, 20) GUISetState(@SW_SHOW) Local $idMsg ; Loop until the user exits. Do $idMsg = GUIGetMsg() Select Case $idMsg = $idButton_Event GUICtrlSendToDummy($idUser) Case $idMsg = $idButton_Cancel GUICtrlSendToDummy($idUser) Case $idMsg = $idUser ; special action before closing ; ... Exit EndSelect Until $idMsg = $GUI_EVENT_CLOSE EndFunc ;==>Example What does GUICtrlSendToDummy($idUser) actually do?

Thank you so much for your response and in showing me what I needed to do to make it work! I have been reading these forums for a while now and am very impressed w/ the content and the considerable support given to the participants.

I see your argument, but I can't totally sympathize. Firstly, I appreciate that you worked hard on something and shared it with the community here. However, multithreading has been a sensitive topic here because the meaning is misused or not understood. Please don't take it personally, but we're dealing with the minutia of what multithreading is. I fail to see how multiprocessing emulates multithreading. They are fundamentally different and to oversimplify equating the two to mean 'parallel execution/operation' is a mistake in my opinion.