Thank you for the comments. I am confused by the following situation.
The link you provide http://www.autohotkey.com/board/topic/56987-com-object-reference-autohotkey-l/ contains the top post by jethrow that states:
“AutoHotkey_L supports COM natively (thank you Lexikos, Sean, & fincs ). This doesn't eliminate the COM Standard Library, but it does add quite a bit of functionality to AutoHotkey. However, if users don't know or understand any COM objects, this Native COM support is less appealing/useful. Therefore, I am creating this thread …”.
The link to the COM Standard Library in jethrow’s post is http://www.autohotkey.com/board/topic/21142-com-standard-library/ and that link states “DOWNLOAD: COM.zip or COM_L.zip (for AutoHotkey_L) or AutoHotkey32/64 (COM is built into)” but the link to that COM_L.zip on jethrow’s site is broken.
Given that jethrow on his site indicates the native COM support in AHK_L “doesn't eliminate the COM Standard Library” and given that the link on "COM Standard Library" site for the “COM_L.zip (for AutoHotkey”L)” is broken, is the required action of the user to comply with the advisory on jethrow’s site about “COM Standard Library” to install the COM.ahk (not COM_L.ahk) with the current version of AHK_L, or am I misinterpreting what jethrow is saying about the need for the use of the COM Standard Library with the native support for COM in AHK_L?
I am among the new users of COM who unfortunately currently fall under the “less appealing” group described in jethrow’s post. I can’t find a site which focuses on getting novice users up and running with native COM in AHK_L in a manner similar to the approach taken by jethrow on his site for the legacy COM_L libraries. Does one exist?
The current state of my AHK_L script is below where the intent is to perform COM operations to modify a few existing Word files, most of which were created in the beginning portions of the script. The script uses a sequence of ControlGet and then Acc_ObjectFromWindow operations after using the window’s title to iteratively make the individual Word windows active. An example for just one Word file is shown in the below script extract. The intent for the pasted extract is to perform COM operations on the WordRawWindow object which is one of the many objects that are created by the script for the various Word documents that are simultaneously open. The script where the extract is taken from makes a sequence of changes to the various Word documents in an order that is dependent on content results. I am looking for any solution technique that includes instructions or examples to make simple formatting, cutting, pasting, copying and saving modifications of those Word documents via COM. I am happy to use the native AHK_L COM functionality or external libraries, but given this is my first attempt at COM I would greatly benefit from examples like those on jethrow’s site for the legacy COM_L library.
; … Beginning of Script not shown here …
run C:\Program Files\Microsoft Office\Office12\winword.exe /q /t"C:\Users\Account\AppData\Roaming\Microsoft\Templates\HeaderMacro.dotm"
; … More Script code that is not shown here …
IfWinNotActive, %Word_Raw%, , WinActivate, %Word_Raw%,
ControlGet, hwnd, hwnd, , _WwG1, ahk_class OpusApp
WordRawWindow := Acc_ObjectFromWindow(hwnd, -16)
; … I need to write more script that uses COM operations to manipulate the contents of the various Word files …