Changeset 715 for trunk/quest-plugin-mfc/src/main/java/de
- Timestamp:
- 08/30/12 14:08:38 (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/quest-plugin-mfc/src/main/java/de/ugoe/cs/quest/plugin/mfc/guimodel/MFCGUIElementSpec.java
r655 r715 270 270 271 271 // if the hwnd and the name did not stay the same, then the name should be checked first. 272 // the current name of one of the specs must be contained in the former names of the272 // The current name of one of the specs must be contained in the former names of the 273 273 // respective other spec for similarity. Either of the specs should contain the name of the 274 274 // respective other spec in its former names. We can rely on this, as in the MFC context … … 277 277 // elements, as only one of them may have experienced more name changes then the other. 278 278 279 if ((otherSpec.name != null) && formerNames.contains(otherSpec.name)) 280 { 279 if ((otherSpec.name != null) && formerNames.contains(otherSpec.name)) { 281 280 return true; 282 281 } … … 286 285 } 287 286 288 // ok. Even the names to not match. This is usually a clear indication, that the elements287 // ok. Even the names do not match. This is usually a clear indication, that the elements 289 288 // are distinct. However, we check, if the former handles matched. This is very unlikely 290 289 // to happen. But it may occur, if a GUI element does not have a name or its name stays
Note: See TracChangeset
for help on using the changeset viewer.