| || |
Change in msw_id
User ERIC TREXLER (email@example.com) posted:
I had a similar problem occurring with our CAD/CAM application.
Everytime our software is launched, the main "cad window" of our application
has a new msw_id.
This cause almost everything in our application to not be recognized, since
most of the items are "children" of this main cad window in the GUI map. To
resolve this issue, I modified the physical description for our main cad
window to :
label: "!.*: .*",
I also had to address an issue of the window label, because unless I had the
same part file loaded every time I launched the software.
A key to doing this is using the " ! " along with " .* " to signify varying
input or properties.
Try to retain as much of the description that remains constant as possible,
to avoid the description being too general.
Hope this helps.
Quality Assurance Analyst
Re: Change in msw_id
User Richard Weber (firstname.lastname@example.org) posted:
You could collect other descriptive info about each object that you might n=
ot want to be used in the GUI map. Like x, y coordinates. You could even st=
ore this in a temporary GUI map (one without MSW_id). Now just loop through=
that data and grab the MSW_id directly from the object. Update your main G=
UI map with the new MSW_id.=20
I do something similar for screens that have objects that can only be uniqu=
ely identified by location but the number of objects change... To specify a=
an object I pass the general coordinates and in return get the location pr=
operty for that object. Now I can mess with the object normally.