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
The issue was originally reported in PyvesB/eclipse-planet-themes#17, but I traced it back to the flat scroll bars provided by Xiliary. It seems that they break tree rendering in Eclipse 2024-06, which will be officially released on June 12th. Here's a screenshot of what happens with Clean Sheet:
Any clue on what may be happening?
The text was updated successfully, but these errors were encountered:
Hi, that looks pretty bad. Unfortunately, I currently do not have any MS Windows OS at my disposal nor do I have the time to investigate this thoroughly. At a first glance, it might have to do with the changes of eclipse-platform/eclipse.platform.swt@f809372 and/or eclipse-platform/eclipse.platform.swt@0b0addf to Tree, TreeColumn, and TreeItem introducing DPI zoom changes to basic controls. As the changes of other topics date back years these commits seem to match the timeframe, right? Since the TreeAdapter is an extension of Tree that reparent the adapted tree instance to the adapter instance (and might do some other ugly stuff on internals that I forgot), this might interfere with whatever new DPI Zoom mechanism is doing or it might causes a dangling reference to some parent attributes or the like.
Very unfortunate this theme is not maintained anymore, it was the last hope to have a nice looking, modern Eclipse UI... Was even hoping for a dark version of this theme, which would be the ultimate solution to compete with the other IDEs.
Hello 👋🏻
The issue was originally reported in PyvesB/eclipse-planet-themes#17, but I traced it back to the flat scroll bars provided by Xiliary. It seems that they break tree rendering in Eclipse 2024-06, which will be officially released on June 12th. Here's a screenshot of what happens with Clean Sheet:

Any clue on what may be happening?
The text was updated successfully, but these errors were encountered: