Enhance error message for inadequite OpenGL version
Please update the error messages when users are informed they have an inadequate OpenGL version. Please add advice and direction for said users. Even Kitware developers are getting it wrong.
Sure, we can add some more helpful information to the error window that states what version of OpenGL is required to run and what options to try if ParaView cannot be run with the OpenGL it finds. A document with frequently used actions to get ParaView running in situations where the local OpenGL implementation is too old could be helpful. I like your idea of linking to it from the error dialog or at least saying how it can be accessed. Where should it live?
Thanks, CoryHi guys, I’m looking at the opengl issues discussion on Discourse, and wondered if you could enlighten me on a few fundamental questions. https://discourse.paraview.org/t/opengl-problems/729/9
- This person is running Linux, and somewhere there has a too old of version of OpenGL.
- The first question is, do they even have a good GLX Context. If they don’t, what do they have to do? (Update Mesa)? How can you tell?
- Once they have a good GLX context, they need a new enough OpenGL. This needs to be OpenGL 3.2. The way around this, on Kitware builds of OpenGL, is to run paraview –mesa-llvm – right?
- Why can’t ParaView cleanly tell the user that he/she either has a bad GLX Context, or too old of OpenGL? If it’s a good GLXContext, and bad OpenGL, say so. Further, why can’t we print out recommended actions right in the error screen (or, a link or advice on how to solve the issue)? For instance, “look in the Help menu for Connection Issues document”.
- Have I missed something?