Custom Query (3933 matches)

missing UDFs from 3.2.13.6 (30th July, 2008) (Beta):

UDFs:
- Added: _ExcelHorizontalAlignSet, _ExcelFontSetProperties, _ExcelBookAttach (litlmike)
- Fixed: Excel Examples
- Added: _WinAPI_SetEndOfFile, _WinAPI_SetFilePointer (Zedna)
- Fixed #465: _DateTimeSplit if seconds omitted defaulted to -1, now defaults to 0

Note: In AutoIt3.chm::/html/autoit_changelog_complete.txt it's OK

changelog 3.2.13.2 (15th June, 2008) (Beta):

• Changed: @ProcessorArch changed to @OSArch as it was misleading.

AutoIt3.chm::/html/intro/64-bit_support.htm

To see if you are running under a 64-Bit Edition of Windows use @ProcessorArch macro. To see if you are using the 32 or 64-bit version of AutoIt use @AutoItX64.

ObjGet doesn't seem to be doing what I expect it to. I placed files named "test.doc", "test.txt" and "test.xls" in my root folder and used the following code to test:

		
	$file = "C:\" & InputBox("","file?")
	$oExcel = ObjGet($file)
	If @error Then
		msgbox(1,"", "Path Not Found for: " & $file)
	Else
		msgbox(1,"", "Path Found for: " & $file)
	EndIf
	Exit

ObjGet appears to be sometimes functioning like "FileExists", ruturning 0 whether the file is in use or not. Sometimes ObjGet works the first time a file is referenced, and then continues to report it (after thinking for a few seconds) as active long after the process was closed. Oddly, when referencing a previously opened .txt file, ObjGet consistantly causes autoit3.exe to abend with 0xc0000005 at offset 00042a376. Just with the .txt extension. Weird...

The only other factors that may be in play here that I can think of are that this PC did get the recent SP3 update to XP Pro, and that I'm running my tests interpretively, via SciTE, rather than as compiled stand-alones.

Thanks.