Custom Query

Hi!

DirMove() adds an extra dot to the existing one in the name of the moved directory.

Example()
;~ Example2()

Func Example()
	
	DirCreate('C:\Test Folder 1.1')
	
	Sleep(2000)
	
	DirMove('C:\Test Folder 1.1', 'C:\', 1)
	
EndFunc

Func Example2()
	
	DirCreate('C:\New Folder')
	DirCreate('C:\Test Folder 1.1')
	
	Sleep(2000)
	
	DirMove('C:\Test Folder 1.1', 'C:\New Folder', 1)
	
EndFunc

Other characters aren't affected!

PS: The "Sleep(2000)" is just to follow the script easier when it is running.

$oHTTP = ObjCreate("winhttp.winhttprequest.5.1")
$EventObject = ObjEvent($oHTTP, "Event_")
$oHTTP.open("GET", "http://google.com", True)
$oHTTP.send()

+>22:41:14 Starting AutoIt3Wrapper v.1.10.1.14    Environment(Language:0409  Keyboard:00000409  OS:WIN_VISTA/Service Pack 1  CPU:X86  ANSI)
>Running AU3Check (1.54.14.0)  from:C:\Program Files\AutoIt3
+>22:41:14 AU3Check ended.rc:0
>Running:(3.3.0.0):C:\Program Files\AutoIt3\autoit3.exe "C:\Users\blah\tmp.au3"    
!>22:41:17 AutoIT3.exe ended.rc:-1073741819
+>22:41:18 AutoIt3Wrapper Finished
>Exit code: -1073741819    Time: 4.800

This request is very similar to ticket #131 which was rejected because it was said that the IP could be made a global variable, but that reason was incorrect.

In production version 3.2.0.0 UDPRecv set the sender's IP in the third element ([2]) of the array returned by UDPBind. This allowed you to determine the sender and reply appropriately. This feature has been removed so that it seems that the only way to find the sender is to require that the sender adds a header to the data, with the header containing his IP. Since the IP of the sender is already included in the data packet it seems reasonable to me that the UDPRecv function should reveal it. In versions of AutoIt 3.3.0.0 and probably earlier, the third element is used for the receiver's IP which is not useful as that is known when UDPBind is called, it won't change and it could indeed be covered with a Global variable.

My request, obviously, is to have this feature returned. It seems that the feature was never documented so it isn't a bug.

I appreciate that the feature might have been removed because it was considered better to only have one ip sending to one port and if so then I can understand the reason for rejecting this request.

Thank you for your time. martin