Drag and drop pointer not accurately identifying its position correctly on screens other than screen 1

[michaelansley]

Archi Version

5.5.0

Operating System

Windows 11

Archi Plug-ins

jArchi 1.8.0, coArchi 0.9.2, Excel for Archi 1.0.0, Lightbox for Archi 1.2.0

Description

When using Archi on screens 2 or 3 (my laptop screen is 1, two large monitor are 2 and 3), when I try to drag something from the Models tree to a view, Archi shows the various drag icons, but as if the pointer is in another place on the screen. So, the pointer can be at a perfectly valid place on the view to drop, e.g.: an application-component, but the drag icon shows that dropping is not available. Or perhaps it shows that it can be dropped, but then when dropped, it appears in a very different place.

Please note that screen 1 appears to work fine. I have also tried Windows Explorer on screen 2, testing the D&D functionality, and it works fine.

Steps to reproduce

1. Start Archi
2. Create a new model, add a single application-component or other object to the model
3. Open the Default view
4. Move Archi to another monitor (Windows-Shift-Left/Right)
5. Try to drag an object from the Models window to the open view

What I expect:

1. Object appears in the view at the place where it is dropped
2. While busy dragging, the drag icon represents where it is being dragged accurately, i.e.: when dragging on a view where the object can be dropped, not to show the icon indicating that it cannot be dropped

What I see:

1. When I drop the object into the view (assuming the drag icon indicates a drop is allowed), it appears in the view at a completely different place to where the pointer was when I dropped it
2. When dragging the object, the drag icon does not accurately align with what I should be able to do (please note that the drag icon does align with what will actually be allowed, i.e.: if I drop the object while the icon shows that no dropping is allowed, then the drop will be ignored)

[Phillipus]

Hi, problems with using more than one monitor could be related to problems with Eclipse SWT or Eclipse GEF or there might be something in Archi's code that needs to change.

I don't have access to a multi-monitor setup to test this, so this will need someone with such a setup to debug this one.