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
Copy file name to clipboardExpand all lines: news/4.36/jdt.html
+46-54Lines changed: 46 additions & 54 deletions
Original file line number
Diff line number
Diff line change
@@ -99,36 +99,29 @@ <h2>Java Editor </h2>
99
99
</td>
100
100
</tr>
101
101
<trid="customFoldingRegions">
102
-
<tdclass="title">Custom folding regions</td>
102
+
<tdclass="title">Custom Folding Regions</td>
103
103
<tdclass="content">
104
104
It is now possible to create custom folding regions by specifying a comment at the start and end of the region.
105
105
You can enable and configure this feature under <b>Window > Preferences > Java > Editor > Folding > Custom folding regions</b>.
106
+
<imgsrc="images/custom_folding_regions_preferences.png" alt="Preference page for custom folding regions" />
106
107
<p>
107
-
<imgsrc="images/custom_folding_regions_preferences.png" alt="Preference page for custom folding regions" />
108
-
</p>
109
-
<p>
110
-
In that preference page, you can specify the text that should be used to start and end a custom folding region.
108
+
on that preference page, you can specify the text that should be used to start and end a custom folding region.
111
109
When this is enabled, writing a comment starting with the specified region start followed by another comment starting with the specified region end creates a folding region.
112
110
</p>
113
-
<p>
114
-
<imgsrc="images/custom_folding_regions_code_expanded.png" alt="code containing comments with the text 'region' and 'endregion'" />
115
-
</p>
111
+
<imgsrc="images/custom_folding_regions_code_expanded.png" alt="code containing comments with the text 'region' and 'endregion'" />
116
112
<p>
117
113
Custom folding regions can be collapsed like any other folding regions.
118
114
</p>
119
-
<p>
120
-
<imgsrc="images/custom_folding_regions_code_collapsed.png" alt="custom folding regions are collapsed" />
121
-
</p>
115
+
<imgsrc="images/custom_folding_regions_code_collapsed.png" alt="custom folding regions are collapsed" />
122
116
</td>
123
117
</tr>
124
118
<trid="foldingProjectPreferences">
125
-
<tdclass="title">Project Properties page for folding</td>
119
+
<tdclass="title">Project Properties Page for Folding</td>
126
120
<tdclass="content">
127
-
Preferences for folding can now be configured on a per-project basis in addition to configuring folding for workspaces.
121
+
Preferences for folding can now be configured on a per-project basis in addition to configuring folding for the workspace.
128
122
This page is available under <b>Project > Properties > Java Editor > Folding</b>.
129
-
<p>
130
-
<imgsrc="images/folding_property_page.png" alt="Project Properties page for folding" />
131
-
</p>
123
+
<p></p>
124
+
<imgsrc="images/folding_property_page.png" alt="Project Properties page for folding" />
132
125
</td>
133
126
</tr>
134
127
<!-- ******************* End of Java Editor ************************************* -->
@@ -164,68 +157,67 @@ <h2>Debug</h2>
164
157
</td>
165
158
</tr>
166
159
<trid="collapsing-stackframes">
167
-
<tdclass="title">Collapsing stack frames</td>
160
+
<tdclass="title">Collapsing Stack Frames</td>
168
161
<tdclass="content">
169
-
Navigating in deep stack frames can be challenging during debuging, due to high number of stack frames that are not relevant for most of the time, for example because they are provided by either the JDK or a testing framework, or by some library</b>
170
-
This feature tries to help focusing on the stack frames, that are the coming from the user created projects, drastically reducing the unnecessary noise in the Debug View
<tdclass="title">Navigate to variable declaration</td>
181
+
<tdclass="title">Navigate to Variable Declaration</td>
188
182
<tdclass="content">
189
-
Users can now navigate to a variable’s declaration directly from the Variables view during a debug session, making it easier to trace variables—especially in methods with numerous local variables.
190
-
<br><br>
191
-
Choose <b>Navigate to Declaration</b> from context menu of variables
183
+
Users can now navigate to a variable’s declaration directly from the Variables view during a debug session,
184
+
making it easier to locate a variable, especially in methods with numerous local variables.
Trigger points can now be configured to automatically resume execution when hit, allowing breakpoints after the trigger point to be activated while skipping those before it,
207
-
enabling more focused and efficient debugging workflows.
208
-
<br><br>
209
-
On enabling a trigger point a new option will be shown its left to <b>Continue execution </b> on hit or not
199
+
Trigger points can now be configured to automatically resume execution when hit,
200
+
allowing breakpoints after the trigger point to be activated while skipping those before it,
201
+
thereby enabling a more focused and efficient debugging workflow.
210
202
<p>
203
+
Upon enabling a trigger point, a new option will be shown to <b>Continue execution on hit</b> or not.
Resume trigger also supports conditions, meaning if condition is met true it will resume the execution else it will suspend
220
210
<p>
211
+
Resume trigger also supports conditions, meaning if condition is true it will resume the execution otherwise it will suspend.
212
+
</p>
221
213
<imgsrc="images/ResumeWithCondition.png" alt="Resume-Triggerpoint with conditions" />
222
-
</p><br>
223
-
<br><br>
224
-
Now when you run in debug, Trigger point wont hit, allowing you to skip previous breakpoints and hit on the actual breakpoint you need to focus. <br><br>
225
-
For example, here <i>Resume trigger</i> was set on line number 7 and during debugging it hit on line number 8 by skipping all the previous breakpoints
226
214
<p>
215
+
Now when you run in debug mode, the trigger point won't hit, allowing you to skip previous breakpoints, and stop on the actual breakpoint on which you need to focus.
216
+
</p>
217
+
<p>
218
+
For example, here <i>Resume trigger</i> was set on line number 7 and during debugging it hit on line number 8 by skipping all the previous breakpoints.
0 commit comments