Use Windows MessageBox API for error when GLFW can't create a Window.

[Bluebugs]

Description:

This use Windows native API to create a MessageBox that display an error for all problem related to the GL driver. Specifically useful when the OpenGL driver is not available.

Fixes #2689

Checklist:

• Tests included.
• Lint and formatter run with no errors.
• Tests all pass.

[coveralls]

Coverage decreased (-0.006%) to 61.533% when pulling 9f671e6 on feature/graceful-failure-windows-gl into 61b61b4 on develop.

[toaster]

This PR let me think about error reporting in general and I’ve the following questions:

1. Shouldn’t GL errors always be fatal because a Fyne app without graphics output is fairly useless?
2. Shouldn’t we present errors on all platforms consistently (this does not only apply to GL errors), i.e. with some kind of native message box if the user is unlikely to see the log?

[andydotxyz]

Looks good to me thanks

[Bluebugs]

1. Shouldn’t GL errors always be fatal because a Fyne app without graphics output is fairly useless?

In the code path that trigger this MessageBox, it is indeed fatal and the application will quit after the MessageBox is acknowledge by the user (driver.go:initFailed#149 and driver.go:initFailed#152). I would think if there is other path that should abort, they should call initFailed too.

2. Shouldn’t we present errors on all platforms consistently (this does not only apply to GL errors), i.e. with some kind of native message box if the user is unlikely to see the log?

That would be nice. It might be possible on macOS, but it won't on Linux/BSD which doesn't have a native message box API (Arguably on those OS, people are more used to the command line, so maybe less of an issue). Maybe opening another issue to look into how to do things on macOS would make sense?

[toaster]

That would be nice. It might be possible on macOS, but it won't on Linux/BSD which doesn't have a native message box API (Arguably on those OS, people are more used to the command line, so maybe less of an issue). Maybe opening another issue to look into how to do things on macOS would make sense?

I think, we could even try to make this work on Linux. At least we might try notify-send or xmessage or alike in addition to the command line error.

I’ll open an issue.