Summary: | [JFace] AbstractInformationControlManager.getClosestMonitor causing wrongly positioned hovers | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Soraphol (Paul) Damrongpiriyapong <sdamrong> |
Component: | UI | Assignee: | Platform-UI-Inbox <Platform-UI-Inbox> |
Status: | NEW --- | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 4.20 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux | ||
See Also: | https://bugs.eclipse.org/bugs/show_bug.cgi?id=573150 | ||
Whiteboard: |
Description
Soraphol (Paul) Damrongpiriyapong
2021-05-05 10:37:33 EDT
I have experimented with the changing AbstractInformationControlManager, and have been successful in fixing the problem. However, I fixed it in a hacky/local way, as I don't know how my changes will affect other functions that use getClosestMonitor. Summary of my patch: - Instead of getting the closest monitor through distance calculation, just use the SWT control's getMonitor function to get to the monitor the fSubjectControl is on. - Remove the offset that is present in the return value of getMonitor, aka the x & y values should be set to 0 for the monitor's client area. If the x & y values are set, this messes with the intersect/contain functions since the point we check is relative to the Shell and not the whole physical display setup. |