Window Word +8 and +12 fields can be used by Delphi Shops as a unique way to identify objects (Component Classes) on forms.
Compuware has been assisting us in handling an issue to lessen our reliance on Index as a significant field by instead using the Window Data field.
The QARun term Window Data (4 Byte Offsets) refers to the data associated with a window created by Windows and is accessible using the Windows API Function GetWindowLong().
Windows allows apps to modify windows with user defined data. QARun can extract this user defined data up to 4 long values and uses these values in an object map entry to identify a control. If the window data values are unique and these are the only significant fields, QARun uses these values over the standard techniques to identify the control.
This is a pretty large topic and what I have given here is only a general overview and does not cover any programming modifications necessary for delphi apps in order to pass Windows Data used by QARun -- post back if you would like to discuss further.
Sorry it took so long to reply -- little busy -- spoke with our developers and am trying to get them to prepare a brief email on their mods -- on how they reregister classes in Delphi to pass Window Word information. However, I suggest that you contact Compuware -- they should be able to provide you with a white paper on "Attach Mapping with Window Data -- Technical Documentation" This paper was our starting point. Please note that this modification to rely on Window Word 3 field only lessens your reliance on Index. In our case -- we have a mature Object Map Master and could not easily implement this change -- it actually required us to create a new database. I set up this database with Significant Field masks -- to only pass Window Word information for specific classes that were set up to pass this unique identifier and ignore the index -- for everything else we ignore the Window Word 3 field and pay attention to index. Basically -- the problem fields were objects aliased as Edit fields.
Anyway there is a lot on this topic and it probably deserves an offline discussion. However, I would first contact Compuware about the White Paper first.