Version 1.7 adds an analysis of browse mode if active. Revised documentation is below.
Jamal Press Control-Windows-H to harvest information from a top-level window and all its child windows. The default item in the list is the previously active window. A report is saved to a structured, Unicode text file called HarvestWindow.txt in the user profile folder. The file is then opened with the program associated with .txt files. Each section of the file lists all properties found for a window. Subsequent sections harvest its child windows, recursively. The heading of a section starts with an outline-style number that indicates the window's position within a tree hierarchy, e.g., 1.2.3 refers to a window that is the 3rd child of a window that is the 2nd child of the top level window. After the number is the window type, and then the window title, if any. Properties of the top level window include version information of the process that created the window. Properties such as Status, Style, and Type are translated to a string representation, and end with ".String" to indicate this. If a property value spans more than one line, it is started on a new line rather than on the same line as its property name. Details from Microsoft Active Accessibility (MSAA)complete a window section. Each accessible object or child begins with a line containing a subordinate outline number, role, and name if any. If browse mode is active, the script analyzes that buffer instead of a window. The properties of each browse line are analyzed, including MSAA ones. The script announces a percent estimate of progress every few seconds. If the process is taking too long, you can choose the Stop button to get the information harvested by then. With some applications, e.g., Mozilla-based ones, stopping may be necessary due to an infinite loop in traversing the MSAA tree. The Help button invokes the standard help dialog available in Script Manager. This global script requires GW Toolkit 6.2 and Homer Shared Object 2.7 (or above).
