Provisional support for Windows ARM64 has been hadded.
It is now possible to contribute custom image processors using the
org.eclipse.wb.core.java.imageProcessor extension point. Those
contributes are used by the property table to generate the Java code responsible
for setting the image of a composite.
It is now possible to use lambda expressions to implement (event) listeners, in addition to anonymous classes.
Example: addHelpListener(e -> { ... });
With limited functionality, it is also possible to use factory methods used by e.g. SWT.
The name of the factory method is expected to be of the form
<method>Adapter(Consumer<Event> c)
Example: addMouseListener(MouseListener.mouseUpAdapter(e -> { ... }));
The technology is effectively dead and the project no longer actively maintained. In prevent compilation errors inside the workspace, those components have been removed from the project.
All special characters in the description need to be properly encoded.
Example: <b>...</b>
The wbp-factory.xml files should use the http://www.eclipse.org/wb/WBPComponent namespace.
WindowBuilder now uses class-local instances of LocalResourceManager, instead of the global SWTResourceManager, to keep track of SWT resources.
Note that WindowBuilder is still able to recognize usage of the SWTResourceManager in user code, but any further modifications will exclusively use the LocalResourceManager.
Users can migrate their code by manually creating a local LocalResourceManager
variable, by initializing it with JFaceResources.managerFor(...) and by then
replacing all calls to ASTResourceManager with calls to the local variable.
It is no longer possible to use the Design editor with a Java 8 JRE. If your application requires to compile against this Java version, consider upgrading to the latest JDK and instead simply setting an appropriate project-specific compiler compliance.