 | | Re: GLUT for MacOS X
|
|
(...) A .m file is a method file. It's the file extension used for Objective C source files in place of .c, .cpp, etc. --Travis Cobbs (tcobbs@REMOVE.halibut.com) (24 years ago, 4-Mar-02, to lugnet.cad.dev.mac)
|
| |
| | 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)
|
| |
| | 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)
|
| |
| | Re: video card
|
|
Opps. I just noticed you do have -l3 there. I missed that. So, no, I have no idea what is wrong. I can test ldglite on some beige G3/300's next Monday. James (...) (24 years ago, 23-Feb-02, to lugnet.cad.dev.mac)
|
| |
| | Re: video card
|
|
Try: ldglite -v3 -l3 -ledit myfile.dat -l3 tells it to do stuff different or something like that.. ? Anyway, it is alot faster for me with -l3 James (...) (24 years ago, 23-Feb-02, to lugnet.cad.dev.mac)
|
| |
| | video card
|
|
I have been doing an analysis of the ldglite 0.9.5 code base. Most of the ledit commands cause the image to be either invisible or render incorrectly. Also, I get a wireframe trail when I use the arrow keys. Everything re-renders fine if I cycle (...) (24 years ago, 22-Feb-02, to lugnet.cad.dev.mac)
|
| |
| | Apple Design Awards: Best Mac OS X Open Source Port
|
|
Hi all, Though many of the programers will likely see this, I thought I'd forward it here just in case. Since getting LDraw tools on the Mac is an unpaid (and underappreciated!) prospect, the idea of winning one of the prizes below might be a bit of (...) (24 years ago, 22-Feb-02, to lugnet.cad.dev.mac)
|
| |
| | Re: Status of ldglite 0.9.5 source on Mac ?
|
|
(...) I have a pretty good idea where those problems might be. If you want, I could try and help you over the trouble spots one at a time like I did with James on OS X. Don (24 years ago, 19-Feb-02, to lugnet.cad.dev.mac)
|
