 | | Re: GLUT for MacOS X
|
|
(...) Yeah, just look at: (URL) (24 years ago, 4-Mar-02, to lugnet.cad.dev.mac)
|
| |
| | Re: GLUT for MacOS X
|
|
(...) I just checked the code in glutmenu.m (what's a .m file?) and it looks like it creates View, GLUT, and Tools menus when you attach to the left, middle, and right mouse buttons. I guess that's OK as it would put the ldglite menus under Tools. (...) (24 years ago, 4-Mar-02, to lugnet.cad.dev.mac)
|
| |
| | Re: GLUT for MacOS X
|
|
(...) Probably it's just one menu up top that equals the right-click popup menu. I can't tell from his code (I'd have to build something and see.) (...) OS X apps are supposed to put mini snapshots in the dock. (24 years ago, 4-Mar-02, to lugnet.cad.dev.mac)
|
| |
| | Re: GLUT for MacOS X
|
|
(...) ... (...) I wonder how this works. As far as I know there's no way to associate a name with a particular glut menu. Does it just paste all the options in the top level menu across the menu bar? If so, how does it know which toplevel menu to (...) (24 years ago, 4-Mar-02, to lugnet.cad.dev.mac)
|
| |
| | 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)
|
