Community
Participate
Working Groups
3.3RC2 I20070525-1350 public class A { // Numbers int one, two, three, four, five, six, seven, eight, nine, ten, eleven, twelve, thirteen, fourteen, fifteen; } Configuration: - Enable Java folding. - Have all element types folded by default. - Using the Eclipse [built-in] code formatter. Steps: 1. Paste the above code as a new class file. 2. Format the code (in case Bugzilla has reformatted it). 3. Close and reopen the file. -> The variable declarations are not visible. -> Line numbers (if visible) show 1, 2, 5. -> No fold marks (+/-) are visible in the margin. 4. Select each variable in turn from the Outline view. -> Each highlights the third visible line (}). There is no obvious way to access the first fifteen fields in the editor. (This is possible with the Folding -> Expand All option, though to a casual user this isn't immediately obvious as a folding issue). Variant: - Without the comment line -> The declarations vanish but reappear when selecting a field node.
>There is no obvious way to access the first fifteen fields in the editor. Hit the + on the left side. Same bug in 3.2.x. Might have been introduced by fix for 60688.
Created attachment 70544 [details] Screenshot with missing code and folding control > Hit the + on the left side. There is no + in the margin - see attached screenshot.
Perhaps the + is there, but on line 3 - which is hidden.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
This bug still occurs in latest Eclipse and also occurs on Linux. Removing stalebug keyword.
(In reply to Jeff Johnston from comment #5) > This bug still occurs in latest Eclipse and also occurs on Linux. Removing > stalebug keyword. Replacing stalebug keyword as it still applies.
