"I don't mind having to do it, but the tool, TestComplete in this case, should be able to do it by itself when needed."
Which is true, and fair enough.
But the test tool can only get the information available to it. And controls can only accept the methods allowable to them. If something (in my case, a Delphi "cell" object within a grid) does not accept click as a method, then it doesn't. Not much you, I, or TestComplete can do about it. Throw a control an unknown method, and it'll throw you an error back.
Same with properties. If a control does not expose certain properties, then there isn't much you can do about.
It's a hassle. But sometimes you need to doo calcs like that. I spoke to our Delphi devs and even they have to calculate relative co-ordinates and offsets to activate certain event triggers in parent objects and so on.
Still, as you say, keeps life interesting! :)
