![]() If you need clarification on anything, please leave a comment and I will respond. I will also assume at least a base understanding of OpenGL. At least of signals and slots, and how to create a simple application from code. Because of the aforementioned reasons, my blog posts will usually cover what I’m working on, while I’m working on it (I should have changed to this model years ago).Īs for these specific posts, all of my Qt5 OpenGL posts will assume you have basic knowledge of the Qt Framework. This is supposed to be at least a little fun and informative for me as well, or else it’s terribly boring. After understanding enough to make the blog post, I really wasn’t interested in making them any more. I was basically putting it off until I understood “enough”. I’ve decided my old model of blog updating wasn’t working. Note: QGL* classes are still usable through the Qt5OpenGL module, so old code relying on such classes will still work, but it is not recommended for new Qt5 OpenGL applications. One of the new things is the addition of the QOpenGL* classes – the replacement for QGL* classes – was made available in Qt 5. Now is a good time to start learning Qt, because lots of OpenGL functionality is evolving within the Qt Framework, so lots of things are changing. Recently I enrolled in a class for Advanced Rendering Techniques. In order to make the class more interesting, I’ve paired it with learning more about the Qt Framework. 13 Jan, 2015 in C/C++ / OpenGL / Qt Framework by Trent
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |