So this should get you the "abbreviated "paths right away, unless the path is not precise enough to retrieve a single element, in which case the path will be extended until it is. Right?IanF wrote:I went over the settings again (got it right this time)
This is a generated XPath based on those settings.
It could still be useful, you are right. However, what we try to do is move away from the error-prone "Abbreviate..." functionality and replace it by some more reliable and still comfortable feature.odklizec wrote:So even with new optimized generation of RXpaths, it may still be useful to have this feature back? Maybe just for advanced users, who know the danger of using this feature but who still prefer to use it in their tests?
Our idea was to make the automatic RanoreXPath generation flexible enough to let the user decide whether to generate really short RanoreXPaths in the first place, instead of having to manually click on the paths in the repository afterwards (and hope for the abbreviated path to still get the correct element...)
Changing the RanoreXPath generation parameters is currently almost impossible for Ranorex users, I agreeIanF wrote:Moving on how hard would it be to provide basic settings for things like Silverlight or HTML or GUI apps would certainly make stuff easier to deal with.
My idea to improve that would be something like the security slider in IE, where the user can decide whether he wants shorter or longer RanoreXPaths to be generated - with all the pros and cons (speed, reliability, maintainability).