ContributionsMost RecentMost LikesSolutionsRe: ignore tab and space in a property for FindChild Thanks for you help Allen ! I'll try this workaround. Regards, Nicolas.Re: ignore tab and space in a property for FindChild Hello, Thanks for the answer. Unfortunately, even if it's working, It's possible that I have two objects including same word so '*' wildcard is too large. I.e.: I can have "save" and "save you profile" on two different objects and the "*save*" will find one or the other depending on their position. That's why I'm looking for something like "ignore space/tab" to put before and after in order to limit the "risk". Thanks, Nicolas.ignore tab and space in a property for FindChildHello, I would like to know if there's a way to use wildcards/regexp in order to make a findFindchild on a property. My aim is to find out some objects based on their properties but with a name like "share" I would like to find for example a link even if the property that I'm checking contains tab or space characters before/after "share". For example I would like to get with myProcess.FindChild("innerText","Share",10) an object even if it's innerText property is " Share" or " Share " ...etc. I've looked wildcards/regExp but I don't know how to use it for that purpose. If someone have an idea :). Thanks for your Help Nicolas. Re: different behavior between aliase and the same direct pathHello Allen, thanks for your answer. Using the breakpoint I see the same object. I'm mostly using the direct call for object because some of them are not working by mapping in the flex embedded. for example I've tried mapping to click on a listItem of a dynamic dropdown list in the flex and I can use the Sys ref without problem but the mapped object is not clickable even with the same sys reference. direct ref: Sys.Process("iexplore", 2).Page("https://XXXX").Frame("bottom").Object("myFlashContent").List(1).ListItem("New_Email") Alias: Aliases.iexplore.pageCampaignCommander.frameBottom.objectMyflashcontent.List(1).ListItem("New_Email").Click(); And via alias or namemapping I can't even see the list, when clicking on it I get message '...underkying object missing...' because the drop down list is a non permanent item. It looks like namemapping and aliasing is not stable for dynamic content inside flex. Please note that I'm currently testing my application just with "accessible true" in options but without the flexclient.swc or automation.swc (I'm waiting for some internal support to clear that point). I don't know if this can explain the behavior I'm currently facing. Thanks, Nicolas.Re: different behavior between aliase and the same direct pathHello Allen, thanks for your answer. Using the breakpoint I see the same object. I'm mostly using the direct call for object because some of them are not working by mapping in the flex embedded. for example I've tried mapping to click on a listItem of a dynamic dropdown list in the flex and I can use the Sys ref without problem but the mapped object is not clickable even with the same sys reference. direct ref: Sys.Process("iexplore", 2).Page("https://XXXX").Frame("bottom").Object("myFlashContent").List(1).ListItem("New_Email") Alias: Aliases.iexplore.pageCampaignCommander.frameBottom.objectMyflashcontent.List(1).Click(); And via alias or namemapping I can't even see the list, when clicking on it I get message '...underkying object missing...' because the drop down list is a non permanent item. It looks like namemapping and aliasing is not stable for dynamic content inside flex. Please note that I'm currently testing my application just with "accessible true" in options but without the flexclient.swc or automation.swc (I'm waiting for some internal support to clear that point). I don't know if this can explain the behavior I'm currently facing. Thanks, Nicolas.different behavior between aliase and the same direct pathHello, I have a strange behavior that I can't clarify. I'm testing a flex application embedded into a web page. In my script, in some specific cases when I call directly the item (ie: Sys.Process("iexplore").Page("https://XXXX").Frame("bottom").Object("myFlashContent").Button(0).Click();) it's clicking in the middle of the frame but if I use the mapped object (to the same link) then it's clicking at the right place. I don't wan't to mix aliases and direct calls in the same script so I would like to understand how I can have different behavior from the single link and the mapped alias to this link. Does any of you already faced this kind of things? Thanks, Nicolas.