-
Notifications
You must be signed in to change notification settings - Fork 10
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
Workspace Resource NullPointerException #553
Comments
@kasemir - Is this the place to report issues with Display Builder, there seems to be a (partial) copy of this repository over in Phoebus? |
This is the display builder repo which was developed for the Eclipse/RCP based CS-Studio, using Java 8. Meanwhile, the Phoebus repo contains most CS-Studio components, including the Display Builder, for Java 11/12. It builds within a few minutes via maven or ant or Eclipse or IntelliJ or ..
|
I've updated the Readme.md to reflect the current state |
Not sure exactly how he did it, but Eric left me a CS Studio v4.6 product that runs on Java 11, and includes this version of Display Builder. The product also provides simple integration with Phoebus, which I think Kunal has developed. Thanks for the update. |
Yes, not sure. For this to compile and run with Java 11 and the JavaFX 11(or 12) that goes with it, some of the tweaks related to "Skins" as in #378 would be required. If you have the exact sources that were used to build, please diff against this repo and make pull requests. Because of the Java FX changes and difficulties getting the JFX libs onto the Eclipse class path, Kunal's approach removes everything based on JavaFX from the Eclipse-based CS-Studio, and instead invokes the Phoebus counterpart via the transition plugins. |
When running the latest version of CS-Studio, I get the following exceptions:
As you can see from the stacktrace, the exception is thrown here, which seems to rely on getRawLocationURI() to always return a value (instead of null).
But more problematic is that after c9b090f, the method openWorkspaceResource() never returns null and as a result file system resources (outside the workspace) will not get loaded.
The text was updated successfully, but these errors were encountered: