 | | GLUT for MacOS X
|
|
This looks like a customized version of GLUT this guy built: Date: Sun, 03 Mar 2002 22:54:44 +0100 Subject: ANN: Improved GLUT for MacOS X From: Dietmar Planitzer <dave.pl@ping.at> To: <mac-opengl@lists.apple.com> Hi, As announced last week, an (...) (24 years ago, 4-Mar-02, to lugnet.cad.dev.mac)
|
| |
| | Re: video card
|
|
(...) You could also try adding this: if ((!strcmp(verstr, "1.1 APPLE-1.1")) && (!strcmp(vendstr, "Apple")) && (!strcmp(rendstr, "Generic")) ) { printf("Stencil buffer disabled for XOR with Apple driver.\n"); // Generic Apple driver has problem with (...) (24 years ago, 26-Feb-02, to lugnet.cad.dev.mac)
|
| |
| | Re: how to get a debugger going
|
|
(...) Suggestions besides fighting with gdb: are you sure the keyboard() routine is getting to glutPostRedisplay() ? this is at the bottom of keyboard(). You could add a printf() there to find out. Maybe your 'E' key case is returning early? If it's (...) (24 years ago, 25-Feb-02, to lugnet.cad.dev.mac)
|
| |
| | Re: how to get a debugger going
|
|
(...) You could try running ldglite in the background to give gdb control of the console. Try this on the command line: ldglite blah blah blah & Then attach the debugger. Or maybe in gdb try: r blah blah blah & It might help, but I'm not positive. (...) (24 years ago, 25-Feb-02, to lugnet.cad.dev.mac)
|
| |
| | how to get a debugger going
|
|
Now that I've got some bugs, I'd like to get into the code with a debugger. In particular, I am trying to set a breakpoint in the keyboard() method so that I may trace the execution of key commands. Id like to figure out why pg-up/pg-down refreshes (...) (24 years ago, 25-Feb-02, to lugnet.cad.dev.mac)
|
| |
| | Re: video card
|
|
(...) I have tried all 4. The differences are subtle, I'm not sure I see them all. I like -le the best because I can see the entire model on each refresh. (...) I commented this out but it did not make the trailing go away. I can always get the (...) (24 years ago, 25-Feb-02, to lugnet.cad.dev.mac)
|
| |
| | Re: video card
|
|
(...) Before you debug, I'd try all 4 of (-le, -ledit, -LE, and -LEDIT) to see which methods have problems. Then comment out this line in main.c and recompile: #define USE_OPENGL_STENCIL This might fix the wireframe droppings at the cost of some (...) (24 years ago, 23-Feb-02, to lugnet.cad.dev.mac)
|
| |
| | Re: video card
|
|
(...) Here is the printout at startup. GL_VERSION = 1.1 APPLE-1.1 GL_EXTENSIONS = GL_APPLE_specular_vector GL_APPLE_transform_hint GL_APPLE_packed_pixel GL_APPLE_client_storage GL_ARB_transpose_matrix GL_EXT_clip_volume_hint GL_EXT_rescale_normal (...) (24 years ago, 23-Feb-02, to lugnet.cad.dev.mac)
|
| |
| | Re: video card
|
|
(...) I forgot to mention this, but if you only want to look at the model, or *mostly* just want to look, you can skip the -le, -ledit, -LE, or -LEDIT on the command line. Then when you want to edit, just press the INSERT key to enter and exit from (...) (24 years ago, 23-Feb-02, to lugnet.cad.dev.mac)
|
| |
| | Re: video card
|
|
(...) Some of that might be normal behaviour, but I'm not positive from the description. Using -ledit on the command line turns on the draw to current piece mode that LEDIT uses. If you just use -le I think it should draw the whole model. You can (...) (24 years ago, 23-Feb-02, to lugnet.cad.dev.mac)
|
