Does anyone know if there is a limit to how many class you can set for one significant field mask. We are a Delphi shop and are trying to use the Windows Word Field 3 for some of our components. I am trying to set up a significant field mask to enable the Window Word Field 3 attribute for about 40 Delphi Component Classes. Anyone know of class limit issues or any other issues with doing this?
In the Significant Field Mask option -- on the Signature tab -- you can set the Specific Module, Class and Window Type. According to help -- determines the fields that are used when the object is located by QARun. For example, if you are auto-creating objects for ADOBE.EXE and never want to pay attention to the Parent Title, but you do want to pay attention this for every other program. You could set up a significant mask specifically for the module adobe.exe.
In my case -- we have specific classes that are enabled to pass unique information via Windows Word 3 field. Class refers to the Windows class name of the window (i.e. TSSIEdit, TSSIKeyCombo, etc.). When recording new objects we want to pick up the Windows Word 3 as a sig. field and disregard the index.
My question is that based on the fact that we have around 40 shared Delphi Component Classes that produce Windows Word 3 info -- is there a limit on QARUN as to how many Classes you may specify under Class on the Signature Tab of the Significant Fields Mask Option.
Well, you never know w/QARun. I remember hitting the limit for include statements a while back - don't remember the # or know if it is still there. Either way, I highly doubt that the limit is below 40 if there is a limit for the number of classes.
I am still curious as to why you ask this question unless you are getting an error or some problem.
A problem is a difference between what is perceived and what is desired, that
we want to reduce (Dewey 1933)