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 annotation/quick‑fix hover now includes a “Javadoc” proposal that opens the Javadoc information pop‑up for the Java element referenced by the annotation.
39
-
40
-
You can now view an element’s API documentation directly from an annotation hover without navigating to the element’s source file.
41
-
42
-
Previously annotation hover took precedence and blocked the usual Javadoc pop‑up for the element under the annotation.
37
+
The annotation/quick-fix hover now includes a Javadoc proposal that opens the Javadoc information pop-up for the Java element referenced by the annotation.
38
+
You can now view an element's API documentation directly from an annotation hover without navigating to the element's source file.
39
+
Previously, annotation hover took precedence and blocked the usual Javadoc pop-up for the element under the annotation.
43
40
To read the Javadoc you had to open or navigate to the original Java source.
44
-
45
-
The fix removes that friction.
41
+
The change removes that friction.
46
42
47
43
#### Annotation Hover Javadoc Behavior
48
-
- When an annotation/quick‑fix hover is shown and the annotation refers to a Java element that has Javadoc, a “Show Javadoc” entry appears in the hover’s proposals list.
49
-
- Activating the proposal opens the standard Javadoc information control (the same browser‑based Javadoc pop‑up used elsewhere).
50
-
- The Javadoc pop‑up replaces the annotation hover for a natural, contextual display.
51
-
- The Javadoc pop‑up is closed automatically when the user clicks outside — preventing stale pop‑ups.
44
+
- When an annotation/quick-fix hover is shown and the annotation refers to a Java element that has Javadoc, a `Show Javadoc` entry appears in the hover's proposals list.
45
+
- Activating the proposal opens the standard Javadoc information control (the same browser-based Javadoc pop-up used elsewhere).
46
+
- The Javadoc pop-up replaces the annotation hover for a natural, contextual display.
47
+
- The Javadoc pop-up is closed automatically when the user clicks outside preventing stale pop-ups.
52
48
53
-
New Show Javadoc proposal in annotation hover
49
+
New Show Javadoc proposal in annotation hover:
54
50
55
51
56
52
57
-
Javadoc pop‑up shown after activating the proposal
53
+
Javadoc pop-up shown after activating the proposal:
58
54
59
-
55
+
60
56
61
-
### New Convert Class To Record Quick-assist / Refactoring
57
+
### New Convert Class to Record Quick-assist / Refactoring
62
58
63
59
<details>
64
60
<summary>Contributors</summary>
65
61
66
62
-[Jeff Johnston](https://github.com/jjohnstn)
67
63
</details>
68
64
69
-
A new refactoring has been added:`Right-click` -> `Refactoring` -> `Convert Class to Record...`, which will convert an appropriate class into a record.
65
+
A new refactoring has been added,`Right-click` -> `Refactoring` -> `Convert Class to Record...`, which will convert an appropriate class into a record.
70
66
71
67
1. The class must have only one or more private instance field members that are all initialized in a single constructor by simple assignment and no static members.
72
68
2. The class must have at most one getter method per instance field that simply returns the field value.
73
69
3. The class can only extend Object and cannot implement any interface.
74
70
4. The class may override `equals()`, `hashCode()`, or `toString()` from Object and these will be copied into the record but it cannot have any other methods except for the aforementioned constructor and getter methods.
75
71
76
-
The refactoring may note that the conversion is not possible or issue a warning before conversion:
77
-
for example, if there is a field that does not have a getter, a warning will be issued that the field will be exposed via an accessor and the user may choose to continue or not.
72
+
The refactoring may note that the conversion is not possible or issue a warning before conversion.
73
+
For example, if there is a field that does not have a getter, a warning will be issued that the field will be exposed via an accessor and the user may choose to continue or not.
78
74
79
75
When the record is created, all references to the previous getters will be changed to call the appropriate record accessors.
80
76
@@ -100,7 +96,7 @@ will be converted to:
100
96
101
97
A new quick-assist has been added to disable or enable a JUnit test in the editor.
102
98
To disable an active test, select within the JUnit test and perform `Ctrl-1` -> `Disable test with @Disabled`.
103
-
To enable a disabled test, select within the JUnit test and perform `Ctrl-1` -> `Enable test (remove @Enabled)`
99
+
To enable a disabled test, select within the JUnit test and perform `Ctrl-1` -> `Enable test (remove @Disabled)`.
When `Enable Markdown Javadoc formatting` is enabled, the `formatter` now recognizes structured Markdown syntax inside `///` comments and formats it appropriately instead of treating it as plain text.
135
-
Supported elements include __headings__, __ordered__ and __unordered lists__ (with proper nesting), __fenced__ and __indented code blocks__, __tables__ and __markdown-style tag annotations__.
130
+
When `Enable Markdown Javadoc formatting` is enabled, the `formatter` now recognizes structured Markdown syntax inside `///` comments and formats it appropriately instead of treating it as plain text.
131
+
Supported elements include __headings__, __ordered__ and __unordered lists__ (with proper nesting), __fenced__, and __indented code blocks__, __tables__, and __markdown-style tag annotations__.
136
132
137
133
Nested lists are aligned consistently, wrapped list items preserve correct indentation, and fenced code blocks (both ` ``` ` and `~~~` styles) are recognized and their enclosed code snippets are formatted while preserving structure.
138
134
The formatter also validates and handles malformed list or numbering patterns gracefully without disrupting the surrounding content.
@@ -144,7 +140,7 @@ The formatting behavior follows the [CommonMark specification](https://spec.comm
144
140
## Debugger
145
141
146
142
147
-
### Improved Highlighting For Inline Chained Lambdas
143
+
### Improved Highlighting for Inline Chained Lambdas
148
144
149
145
<details>
150
146
<summary>Contributors</summary>
@@ -156,7 +152,7 @@ Building on the `inline lambda breakpoint` support added in **Eclipse 4.38**, th
156
152
157
153
Previously, selecting or focusing a lambda stack frame in a chained expression highlighted the entire line, making it difficult to identify the exact lambda.
158
154
159
-
Now only the suspended lambda is highlighted, making it much easier to follow execution in complex chained expressions.
155
+
Now, only the suspended lambda is highlighted, making it much easier to follow execution in complex chained expressions.
@@ -169,8 +165,8 @@ Now only the suspended lambda is highlighted, making it much easier to follow ex
169
165
-[Sougandh S](https://github.com/SougandhS)
170
166
</details>
171
167
172
-
The `Debug Shell` now supports drag and drop from the `Variables` and `Expressions` views.
173
-
You can drag a variable or expression directly into the `Debug Shell`, where it is inserted at the caret location.
168
+
The `Debug Shell` now supports drag and drop from the `Variables` and `Expressions` views.
169
+
You can drag a variable or expression directly into the `Debug Shell`, where it is inserted at the caret location.
174
170
This makes it easier to reuse existing expressions and quickly build new ones using variables during a debug session, without manual typing or copying.
Copy file name to clipboardExpand all lines: news/4.39/platform.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,12 +21,12 @@ A special thanks to everyone who [contributed to Eclipse-Platform](acknowledgeme
21
21
<details>
22
22
<summary>Contributors</summary>
23
23
24
-
-[Elsa Zacharia](https://github.com/elsazac)
24
+
-[Elsa Zacharia](https://github.com/elsazac)
25
25
</details>
26
26
27
-
The `Colors and Fonts` preferences page now displays descriptions for the toplevel theme categories in addition to the individual sub tree elements.
28
-
Previously, only child entries in the tree provided descriptive text.
29
-
With this update, parent categories such as `Java`, `Basic`, `Debug`, `Text Compare` etc. also include descriptions, helping users better understand what each category covers and making it easier to locate relevant settings.
27
+
The `Colors and Fonts` preferences page now displays descriptions for the top-level theme categories in addition to the individual subtree elements.
28
+
Previously, only child entries in the tree provided descriptive text.
29
+
With this update, parent categories such as `Java`, `Basic`, `Debug`, `Text Compare`, etc. also include descriptions, helping users better understand what each category covers and making it easier to locate relevant settings.
@@ -81,7 +81,7 @@ The Equinox launcher executable still contained a manifest that defines a DPI aw
81
81
82
82
Until now, this led to the splash screen not properly being scaled and to potentially incorrect results at the handover of the splash screen to SWT and the Platform Workbench.
83
83
With this release, the Equinox launcher process defaults to DPI awareness "PerMonitorV2" and uses the same autoscale defaults as SWT again.
84
-
For information about the SWT defaults, which also have been updated and unified with this release, see [the according news](platform_isv.md#monitor-specific-scaling-by-default-windows).
84
+
For information about the SWT defaults, which also have been updated and unified with this release, see [the related news](platform_isv.md#monitor-specific-scaling-by-default-windows).
85
85
86
86
Monitor-specific scaling can be disabled via `-Dswt.autoScale.updateOnRuntime=false`, which will also make the Equinox launcher use the preexisting autoscaling defaults for the splash screen.
87
-
The process will still use DPI awareness "PerMonitorV2", but this will automatically be overwritten by SWT for a Display's UI thread to be "System" again.
87
+
The process will still use DPI awareness "PerMonitorV2", but this will automatically be overwritten by SWT for a Display's UI thread to be "System" again.
0 commit comments