more info in case of errors

[Kevin Rushforth]

I think that's a great idea to log as much information as we can about 
the failure modes for each failing pipeline if all of them fail or if 
prism.verbose=true.

-- Kevin


On 7/9/2021 5:53 AM, Johan Vos wrote:
> Hi,
>
> I've seen countless error reports from JavaFX applications that goes as
> follows:
>
> Graphics Device initialization failed for :  es2, sw
> Error initializing QuantumRenderer: no suitable pipeline found
> java.lang.RuntimeException: java.lang.RuntimeException: Error
> initializing QuantumRenderer: no suitable pipeline found
>
>
> That message is correct, but it doesn't help much. My typical next step is
> to ask the user to run with -Dprism.verbose=true, but even that is not
> helpful in case something fails e.g. in the ES2Pipeline init methods.
>
> For reasons I don't always agree with, many software components try to
> reduce verbose output as much as possible. The issue here though is that
> without more information on why a pipeline is not initialized, we are stuck
> with pure guessing/trial and error, which I consider much more ugly than
> verbose output.
>
> I do agree that in case there are 2 or more candidate pipelines, we don't
> need to print every failure detail in case at least 1 is not failing. But
> if all are failing, it would be nice to have more information. Therefore, I
> suggest that we track the errors of the individual pipelines, and print
> them in case none of the options is working.
>
> Thoughts?
>
> - Johan