Community
Participate
Working Groups
The problem: When executing tests, while having the AUT on the right screen (Screen 1), everything goes fine, but as soon as the aut is on my left screen (Screen 2) the text execution fails due to negative coordinates. That doesn't make any sense, because negative coordinates don't imply that they are aren't correct. When having the right screen as screen 1 and the left screen as screen 2, the x coordiante 0:0 is at the top left corner of screen 1, as shown in the example below: -1280 0 1279 ------------------- | | | | 2 | 1 | | | | ------------------- The same problem might occur with the y-coordinates, depending on the screen setup.
I know, that this has been asked of a while ago, but still, i'd like to point this out again, maybe you have changed your mind.
Thanks for the Information, since multi monitor setups are getting more and more frequent, I agree that this feature indeed might be useful. But at this moment we have not enough resources to test this and find all places where checks like this(mentioned in 367156) are implemented. Maybe we could remove easily some of the checks and look what happens. If someone wants to make a contribution we will happy to review it.
I did a quick check of the code, and I think there is a single place where we check against negative coordinates, and funnily, this only in RobotSwtImpl. I think other places in the code are fairly neutral with respect to negaive coordinates, so it might worth simply removing this artificial check. Or before that it may worth testing what happens in a Swing / JavaFX AUT if we use multiple screens. Unfortunately I only have a single monitor, so I cannot myself test this...
Contribution: https://git.eclipse.org/r/#/c/101324/ This contribution removes the extra check from the SWT / RCP tests. In theory this should allow to use multiple screens to the same extent as Swing / JavaFX allows. I'm not setting the ticket Resolved yet, because I'm not able to properly test the above assumption.
Gerrit change https://git.eclipse.org/r/101324 was merged to [master]. Commit: http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=b5a0cf7f8a1c59be70059c9b7cf426a8205d275a
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
We have removed most of the checks with the Screen. If there ist still such errors please reopen the bug
