Re: [PyOpenGL-Devel] Test program?
Brought to you by:
mcfletch
From: Ian M. <ia...@ge...> - 2014-05-27 19:45:48
|
On Tue, May 27, 2014 at 3:44 AM, Sam Bull <sam...@se...> wrote: > On lun, 2014-05-26 at 23:10 -0700, Ian Mallett wrote: > > I spot-checked it just now: there are three chapters dedicated to (now > > completely) deprecated APIs (inc. display lists and GLU). What they > > did have of GL 3, 4 functionality still used deprecated APIs > > (glVertex3f, etc.). My guess is that the current edition continues the > > trend, leaving a lot of legacy cruft in there. > > Fortunately, you're wrong. The book has never mentioned display lists, > glVertex3f and the like. The book approaches it as this is the new-style > OpenGL, it's all shaders, VBOs etc., we're not going to look at > old-style (which is probably why it took so long for them to rewrite > this edition). The whole book is focused on how to use OpenGL 3.3-4.3, > and doesn't even look at old style OpenGL anymore. > > > Oooo excellent. I might be able to recommend it again. Thanks. > So, with the new style, as I understand it, it's not even possible to > use the old OpenGL 2 pipeline (which is why it's not really mentioned in > the book anymore). For example, you need a basic shader to draw even the > most primitive shape, you can't use glVertex3f() etc. to draw a simple > shape, you would have to use a VBO and shader. > Correct. With, say, a GL 4 context, although it's not a GL error to call into deprecated APIs (it just might not do as you expect; in my experience it has no effect), it will be reported as a "high severity" error if you created the context as a debug context (which, if you're using C-level APIs, you should do). Ian |