You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Latest version of Eclipse 2024-12 with all of the updates. 4 4k displays. Windows 11. Scale: 150% 150% 150% 250% (primary display).
Some dialogs can be resized to compensate for the scaling issues but many can not be resized leaving much dialog content unviewable.
Thank you for the report! Unforunately, with 3 monitors at 150%, 150%, and 225%, I was not able to reproduce the issue. I "only" achieved that dialogs pop up outside of the visible area. Can you explain in a bit more detail how to reproduce the issue? In particular, on which of the displays did you place your workbench window and the according dialogs? It was probably one of the 150% monitors, wasn't it?
@akoch-yatta can you please check whether you can reproduce this (at best, once there is more input on how to reproduce, and only once you find some time to do so) and put it into our backlog?
Did you set your primary display's scale to a scale higher than the display that Eclipse is on? I think that is the key: Windows 11 Primary Display Scale set to 250% and the display that Eclipse is on set to a lower scale like 150%.
Did you set your primary display's scale to a scale higher than the display that Eclipse is on? I think that is the key: Windows 11 Primary Display Scale set to 250% and the display that Eclipse is on set to a lower scale like 150%.
Yes, that's exactly the configuration I tried. Unfortunately, I am still not able to reproduce the issue. I moved the issue to the SWT repository, as it is caused by SWT, and assigned the HiDPI label for better tracking.
There has not been any update on this for quite a while. Does the issue persist?
For the previous release and the upcoming release, many improvements also regarding the proper scaling of new shells/dialogs have been made, so likely the issue has been addressed by them.
Closing this as currently the initially reported issue is not reproducible and several improvements in this area have been made since the original report.
Activity
HeikoKlare commentedon Dec 10, 2024
Thank you for the report! Unforunately, with 3 monitors at 150%, 150%, and 225%, I was not able to reproduce the issue. I "only" achieved that dialogs pop up outside of the visible area. Can you explain in a bit more detail how to reproduce the issue? In particular, on which of the displays did you place your workbench window and the according dialogs? It was probably one of the 150% monitors, wasn't it?
@akoch-yatta can you please check whether you can reproduce this (at best, once there is more input on how to reproduce, and only once you find some time to do so) and put it into our backlog?
losmurfs commentedon Dec 10, 2024
I have my Eclipse running in the second display from the left: 4k, Windows 11 Display Scale 150%
losmurfs commentedon Dec 10, 2024
Did you set your primary display's scale to a scale higher than the display that Eclipse is on? I think that is the key: Windows 11 Primary Display Scale set to 250% and the display that Eclipse is on set to a lower scale like 150%.
losmurfs commentedon Dec 10, 2024
Primary Display: Intel(R) UHD Graphics 4k Scale 250%
Display 2: Intel(R) UHD Graphics 4k Scale 150%
Display 3: Intel(R) UHD Graphics 4k Scale 150%
Display 4: NVIDIA RTX 2000 Ada Generation Laptop GPU 4k Scale 150%
HeikoKlare commentedon Jan 3, 2025
Yes, that's exactly the configuration I tried. Unfortunately, I am still not able to reproduce the issue. I moved the issue to the SWT repository, as it is caused by SWT, and assigned the HiDPI label for better tracking.
HeikoKlare commentedon May 19, 2025
There has not been any update on this for quite a while. Does the issue persist?
For the previous release and the upcoming release, many improvements also regarding the proper scaling of new shells/dialogs have been made, so likely the issue has been addressed by them.
HeikoKlare commentedon May 28, 2025
Closing this as currently the initially reported issue is not reproducible and several improvements in this area have been made since the original report.