I mention the solution to this in my other post called "A Tale Of Two Slaves"
Rather than the double click being the problem, I would look at the two examples you gave and the error message.
The difference in your two examples is that in the first one you are using an object name and the second one you are using coordinates. The error message is telling you that TC can't find the coordinates.
You can try to solve the issue with not finding the coordinates, but you'd be much better off if you don't use the coordinates and use the object name instead. As you can see, the coordinates are not reliable, and they will result in your tests not being as portable as you need. Screens are different and test systems are different, so the coordinates will likely not be consistent, where the object name will remain the same throughout.
i have no problem with using the name, however, intellisense did not seem to offer a version of the double click method that allowed using a name. Only the ClickTab method which imitates a single click. There are certain spots where the double click action is an imperative. I will continue to research, try different things, see what i can come up with and report back. Any help is welcome. Thanks!
My bad, they're not screen coordinates, they're coordinates of the actual object
Try leaving out the coordinates (that's one of the examples in the article) and see if the double click happens.
If that doesn't work, then I'd dig deeper into the the error message. Is there any machine where the test runs as expected?
You mentioned that the problem started happening when you shifted to the Network Suite. So, while Marsha_R suggestions are still valid, I'd look at a couple of other things as well.
ClickTab is executing a specific action on the tab that doesn't require the recognition of screen location where as DoubleClick is doing a screen location. What this seems to indicate to me is that the remote machine executing the network job MIGHT be dealing with screen resolution issues where the object may be dimensioned smaller than on the originating machine. So, while a pixel location on the object of 90,15 may work on the developer box, that might not work on the remote box. If you don't want to have to mess around with changing code around too much, you might want to see what screen resolution, scaling, etc., is implemented on that remote box.
