Community
Participate
Working Groups
Build Identifier: 20100218-1602 I have 3 monitors. When I drag a tab the outline of where it is going to go goes to the monitor to the left. If the window is on the left-most monitor, the outline doesn't appear at all. Reproducible: Always Steps to Reproduce: 1. Setup 3 monitors 2. Drag a tab
Not sure where this goes. The DND component says "does not include dragging views and editors" but doesn't say where to put those. And since Eric is watching D&D, I figure he would know...
Sean, what happens if you limit yourself to 2 monitors? I'm just trying to narrow the scope of the problem...
(In reply to comment #2) > Sean, what happens if you limit yourself to 2 monitors? I'm just trying to > narrow the scope of the problem... I get similar behavior with 2 monitors. Sorry, I just re-read my original description and it's vague. The outline goes to the monitor to the left of the monitor that it's supposed to go to, for 2 or 3 monitors. For one monitor, it works as expected. I just realized that I have my monitors re-ordered. They are labeled 3, 1, 2 in the screen resolution preferences. If I change the order to be 1, 2, 3 the outline goes to the proper monitor. (But then I need to move the mouse off the right side of the right-most monitor to get it onto the left-most monitor, so that's not really a solution.)
(In reply to comment #2) > Sean, what happens if you limit yourself to 2 monitors? I'm just trying to > narrow the scope of the problem... I have tested this with two monitors and the same problem is exhibited. (Note that it probably has something to do with the Windows Monitors being re-mapped (when monitor 2 is to the left of monitor 1 as identified by the Windows Control Panel).
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.
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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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.
