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
Outline View subclasses are fully expanded by default whenever a class is selected, whereas before the Outline View was not fully expanded by default
#1480
Open
jmohrmann opened this issue
Jun 26, 2024
· 5 comments
In Eclipse 2024-06, I noticed that, when selecting a Java class, the Outline View loads all the methods, subclasses, etc. for that class, but the subclasses and inner anonymous classes are all fully expanded by default.
In previous versions of Eclipse (2024-03 and prior), only methods that contained anonymous classes were expanded, not all the methods of every subclass. In 2024-06, I usually have to click "Collapse All" and then expand just the top-level type to get a view similar to what it used to be.
I surmise that this is not an intentional change to the way Eclipse operates and am therefore reporting this as a bug.
The text was updated successfully, but these errors were encountered:
@iloveeclipse If this issue is reported to the JavaOutlinePage, then there is probably something different going on here.
The bug reported in ui was referring to the ProjectExplorer using "setAutoExpandOnSingleChildPaths" of AbstractTreeViewer, yet I don't believe this view uses that feature.
I still need to check how to solve the other issue
In Eclipse 2024-06, I noticed that, when selecting a Java class, the Outline View loads all the methods, subclasses, etc. for that class, but the subclasses and inner anonymous classes are all fully expanded by default.
In previous versions of Eclipse (2024-03 and prior), only methods that contained anonymous classes were expanded, not all the methods of every subclass. In 2024-06, I usually have to click "Collapse All" and then expand just the top-level type to get a view similar to what it used to be.
I surmise that this is not an intentional change to the way Eclipse operates and am therefore reporting this as a bug.
The text was updated successfully, but these errors were encountered: