Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Scene Builder now shows a message which FXML imports were not resolvable #577

Closed
wants to merge 11 commits into from

Conversation

Oliver-Loeffler
Copy link
Collaborator

@Oliver-Loeffler Oliver-Loeffler commented Oct 3, 2022

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 in com.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

unresolved imports.

There is also a new option (preserve unresolved imports) which also
allows to keep the imports in saved FXML files.
…d and how this could be avoided. This is only active when the preference `keep unresolved imports` is set true.
…of FXML with unresolved imports' as it exactly does the 2nd.
@Oliver-Loeffler Oliver-Loeffler changed the title fix: Scene Builder now shows as message, which imports were not resolvable fix: Scene Builder now shows a message which FXML imports were not resolvable Oct 9, 2022
@abhinayagarwal abhinayagarwal added this to the 22 milestone Sep 25, 2023
@Oliver-Loeffler
Copy link
Collaborator Author

This one is no longer needed as the related change is now part of #576 .

@Oliver-Loeffler Oliver-Loeffler deleted the issue-281 branch April 11, 2024 05:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ClassDefNotFoundError when importing custom component
2 participants