 | | Re: I have some ideas / suggestions for all programmers
|
|
(...) Another positive side-effect of not using the registry is if you have to move the folder that all your LDraw related tools are stored in, you dont have to dig through the registry to fix all the path names. I had to do this and it was a big (...) (22 years ago, 1-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: I have some ideas / suggestions for all programmers
|
|
(...) Another good thing is that it's much easier just to copy the ldraw.ini file from one installation to another than try to go through the huge registry file and search for LDraw related info. Thus I, for example, get all the viewing angles I (...) (22 years ago, 1-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: *** LDView Version 1.9.5 Released ***
|
|
(...) I plan to eventually try out vertex array range, but since it's nVidia-specific, there has to be a fallback. I hadn't thought about the decrease in memory consumption, but considering the huge amount of memory sucked up by the display lists, (...) (22 years ago, 1-Aug-02, to lugnet.cad)
|
| |
| | Re: I have some ideas / suggestions for all programmers
|
|
(...) I agree about using INI files instead of the registry, because it's easier/safer to directly edit INI files. And it's easier for other programmers to figure out the information. For sharing settings between programs, it makes sense (IMO) to (...) (22 years ago, 1-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: Strange thing with part 30179
|
|
(...) When using "Coarse" mode for rendering studs in MLCAD, any reference to a file like stud*.dat is replaced with the matching stu2*.dat. This method comes directly from ldraw's -FS drawing mode. :) To fix the problem, you should download (...) (22 years ago, 1-Aug-02, to lugnet.cad.dat.parts)
|
| |
| | Re: Strange thing with part 30179
|
|
Hi, I'm the author of those parts. I will try to explain what is happening: Every stud has a "Fast Draw" version. If you open the directory ldraw/p, you will see that there are the stud.dat and the stu2.dat, the stud2.dat and the stu22.dat. (...) (22 years ago, 1-Aug-02, to lugnet.cad.dat.parts)
|
| |
| | Re: Strange thing with part 30179
|
|
(...) The file Stud29 would be the fast draw version of stud9. The fast draw version is the same as the regular version but it uses 6 sides instead of 8. Go to Settings->General->Change... in MLCad. Click on the Rendering tab and under Edit-Mode (...) (22 years ago, 1-Aug-02, to lugnet.cad.dat.parts)
|
| |
| | MLCad Wish
|
|
Hello. Would it be easy to implement an "Explode" feature in MLCad? I.e. if you have inserted a "model" in your file, and explode it, it will be divided into the parts it's built up of. And then youy can explode, and explode till you're at the (...) (22 years ago, 1-Aug-02, to lugnet.cad.mlcad)
|
| |
| | Re: LGEO orientation problem
|
|
(...) Yes, some of the parts in the LGEO library are wrongly oriented. I've also noticed that the technic triangle was wrong. I've reported these two parts to the author (IIRC), but in the mean time, you can add an ad-hoc rotate statement to these (...) (22 years ago, 1-Aug-02, to lugnet.cad.ray)
|
| |
| | LGEO orientation problem
|
|
I'm sure I saw something about this some time ago, but I can't find it 8?( When I render using the LGEO library, some parts are rotated by 90 degrees from their correct orientation, eg 6536.dat (Technic axle joiner perpendicular). What causes this? (...) (22 years ago, 1-Aug-02, to lugnet.cad.ray)
|
