On Mi, 23.10.2013, 18:41, Timothy Reaves wrote: > This is a very confusing topic.
Indeed... > In my code, I am using QOpenGLFunctions_1_2, and it is working. I think the real fun starts with versions beyond 2.0. > But each plugin that uses OpenGL > must do this, and it's unclear what version should be used. I simply used > the minimum version that supported the functionality I needed. It's also > unclear what happens of two different versions are used in the same application. I understood that's the way to go, and the classes are allowed to do just that - implement the minimum version required for their funcionality. It is the failure of bool QOpenGLFunctions_3_2_Compatibility::initializeOpenGLFunctions() on a fat gaming notebook (NVidia, OpenGL 4.2) that puzzles me, to begin with. (And I do understand that this compatibility profile would not be supported on a Mac, but that's a final thing to solve.) Interestingly, with the QOpenGLFunctions_3_2_CoreBackend class, its constructor requires the OpenGL context, but I don't even see the functions to return the OpenGL context for our StelMainView. I must pause on the plugin again at least for a week for other, real-world work. :-( Anyone willing and understanding enough to dive in here? Kind regards, Georg > > On Oct 21, 2013, at 5:10 AM, Georg Zotti <[email protected]> wrote: > >> Dear Qt/OpenGL experts, >> After the return of the 0.11 StelPainter classes I am trying again to prepare the Scenery3D plugin for integration. This plugin was developed mostly by a few students with much better OpenGL knowledge than I have, but who are no longer available to me. They managed to hack around Qt4 limitations with GLee, GLU, etc, which should not be used in Qt5. I find >> the used functionality in the OpenGL3.2 compatibility profile. >> Qt5 brings (according to docs) easier integration of advanced OpenGL functions. However, when I derive my classes from >> QOpenGLFunctions_3_2_Compatibility, the required calls to >> initializeOpenGLFunctions() in the constructors always fail. Everything else concerning OpenGL then leads to a crash. I can compile and link shaderPrograms, but even deleting the shaderProgram without ever using it >> causes a crash. >> The docs always mention dealing with the GL context and classes which are >> not used by Stellarium. We use the QtDeclarative module which is now declared deprecated, and has been replaced by QML and QtQuick1 [also declared deprecated], and should be replaced by QtQuick2. >> Does anybody know: Can I use OpenGL3.2 at all with our current >> deprecated >> classes? Do I just have to call QOpenGLContext::create() (or something else?) somewhere (where??) before a class calls its OpenGL3.2 functions? >> Or do we need to update the StelMainView to use QtQuick2? >> Kind regards, >> Georg >> ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk _______________________________________________ Stellarium-pubdevel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel
