Subject:
|
Re: BrickDraw3D development announcement
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Wed, 6 Feb 2002 00:59:38 GMT
|
Viewed:
|
484 times
|
| |
|
|
In lugnet.cad.dev, Erik Olson writes:
> P.P.S. Does anybody know why glBegin(GL_LINES) would return
> GL_INVALID_OPERATION other than because some earlier glBegin is still
> outstanding?
It's easy to miss OpenGL errors. Are you sure it's the glBegin causing the
error, and not some previous command? Remember that successful commands
don't clear the GL error state. Did you check for an error right before
calling glBegin?
--Travis Cobbs (tcobbs@REMOVE.halibut.com)
|
|
Message has 1 Reply:
 | | Re: BrickDraw3D development announcement
|
| (...) Heh heh. Fixed this bug last night. err = glCheckError(); // no error! glBegin(GL_LINES); err = glCheckError(); // dies! In my zeal to add error checking everywhere to find the real error, I put glCheckError inside a lot of glBegin/glEnd (...) (23 years ago, 11-Feb-02, to lugnet.cad.dev)
|
Message is in Reply To:
| | Re: BrickDraw3D development announcement
|
| (...) No, I just am fed up with OS X, that's all. I'd rather crash Mac OS 9 than lock up the debugger on OS X. It's a personal preference. P.S. It was spider poop. P.P.S. Does anybody know why glBegin(GL_LINES) would return GL_INVALID_OPERATION (...) (23 years ago, 5-Feb-02, to lugnet.cad.dev)
|
6 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
