fix: Scene Builder now shows a message which FXML imports were not resolvable #577
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
Up to now, Scene Builder did not load FXML files with unresolvable imports. This is basically enabled by PR #576.
This PR enables Scene Builder to provide a list of failing imports to the user, together with an instruction on how to include the missing classes/JAR files in Scene Builder.
The
EditorDialog
incom.oracle.javafx.scenebuilder.kit.editor.panel.util.dialog
has been updated so that its Detail window has also the correct application icon and window title. The main EditorDialog also now has the correct application icon.Fixes #281 but requires PR #576 first
Progress