Details
-
Enhancement
-
Resolution: Fixed
-
P4
-
None
Description
The handling of choosing the best GraphicsPipeline is typically a very smooth process, that requires no feedback and that allows the JavaFX platform to select the most appropriate pipeline for the current runtime configuration.
However, when a candidate pipeline "fails", there is not much logging information, and the system will try the next candidate. The only information that is provided (when prism.verbose is true) is something like
`GraphicsPipeline.createPipeline: error initializing pipeline com.sun.prism.es2.ES2Pipeline`
In case the sw pipeline is a valid candidate as well, this will be used. But the user has no idea why the ES2 pipeline failed.
This can especially go wrong in case e.g. 3D effects are requested.
It would be good to have a more detailed trace of why initializing a candidate pipeline failed. There are many logging approaches in the OpenJFX codebase, and I suggest simply using the one we already use in GraphicsPipeline.java for this: in case `prism.verbose` is `true`, `System.err` can be used to provide error information.
However, when a candidate pipeline "fails", there is not much logging information, and the system will try the next candidate. The only information that is provided (when prism.verbose is true) is something like
`GraphicsPipeline.createPipeline: error initializing pipeline com.sun.prism.es2.ES2Pipeline`
In case the sw pipeline is a valid candidate as well, this will be used. But the user has no idea why the ES2 pipeline failed.
This can especially go wrong in case e.g. 3D effects are requested.
It would be good to have a more detailed trace of why initializing a candidate pipeline failed. There are many logging approaches in the OpenJFX codebase, and I suggest simply using the one we already use in GraphicsPipeline.java for this: in case `prism.verbose` is `true`, `System.err` can be used to provide error information.
