 | | Re: Ldlite for OpenGL and Linux (and uppercase filenames)
|
|
(...) What I meant was this: normally ledit shoes studs as lines, right. Several files were changed to uppercase so that ledit would not do the substitution and show the studs. -- Jonathan Wilson wilsonj@xoommail.com (URL) (25 years ago, 20-Jan-00, to lugnet.cad.dev)
|
| |
| | Re: Ldlite for OpenGL and Linux (and uppercase filenames)
|
|
(...) So this is not a problem, just change the primitive file "stud.dat" to "stud.DAT" (according to what I have previously proposed), and if the user wants (or not) to draw the studs, he will change the "line for stud" option of Ledit. P.S. Just (...) (25 years ago, 19-Jan-00, to lugnet.cad.dev)
|
| |
| | Re: Ldlite for OpenGL and Linux (and uppercase filenames)
|
|
(...) This is a special LEdit feature, not related to DOS at all. If the STUD.DAT filename is uppercase, it is always displayed like a full stud in LEdit, even if the user chooses to have "line for stud" to save rendering time. Fredrik (25 years ago, 19-Jan-00, to lugnet.cad.dev)
|
| |
| | Re: Ldlite for OpenGL and Linux (and uppercase filenames)
|
|
(...) Are you sure that was the problem, because Ledit runs on DOS, which doesn't care on filename case, it's case-insensitive, so it should always work in DOS. Rui Martins (25 years ago, 19-Jan-00, to lugnet.cad.dev)
|
| |
| | Re: Ldlite for OpenGL and Linux (and uppercase filenames)
|
|
(...) There is one problem. several files were "corrected" to have the stud.dat references uppercased so that ledit would show the studs. -- Jonathan Wilson wilsonj@xoommail.com (URL) (25 years ago, 20-Jan-00, to lugnet.cad.dev)
|
| |
| | Re: Ldlite for OpenGL and Linux (and uppercase filenames)
|
|
(...) Why don't we just define filenames are case-sensitive, and allow for an option to treat them differently (case-insensitive) if someone requires it ? we should look in to the future, every OS will tend to be case-sensitive, windows hasn't made (...) (25 years ago, 19-Jan-00, to lugnet.cad.dev)
|
| |
| | Re: Using parts in p\48\ (was: part 2951, more questions, nearly done)
|
|
(...) Sure, no problem. I prefer to inline and find the true coordinates of the polygons in the primitives, though. There may be some small rounding errors both in your sine calculations and in LEdit's, and if they don't match, you'll get small (...) (25 years ago, 19-Jan-00, to lugnet.cad.dev)
|
| |
| | RE: OMR Filenaming Standard Change?
|
|
Hi, (...) I agreee. (...) Maybe I don't remember correctly, but until now I assumed that the term 'alternate model' refers to those models in the instruction booklet that can be built from the same set of parts. Just to clear my understanding, (...) (25 years ago, 19-Jan-00, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: 2951 (not quite finished)
|
|
(...) The primitive .dat files invert the colour internally, so if you code 1 16 ..... it ends up correct. If you code 1 24 .... you end up inverting the inverse colour which is not correct. Chris (25 years ago, 18-Jan-00, to lugnet.cad.dev)
|
| |
| | Re: Using parts in p\48\ (was: part 2951, more questions, nearly done)
|
|
(...) hmm okay, I simply calculated the coordinates, sine and cosine relations are our friends:) (...) Yes I will really have to look in to that, I might require some help setting it up, the only time I touched my .emacs file was when installing (...) (25 years ago, 18-Jan-00, to lugnet.cad.dev)
|
