 | | Re: Large LDraw/MPD Files? —Travis Cobbs
|
| | | (...) One of the first things I will probably try to do with LDView after I finally get 2.0 out the door is to work on its memory consumption. But first I have to figure out where all the memory is getting used. Doing some quick calculations based (...) (22 years ago, 20-Dec-02, to lugnet.cad)
|
| | | |
| | | | | Re: Large LDraw/MPD Files? —Don Heyse
|
| | | | (...) I'm not sure what you mean by this. Ldglite only creates one structure in memory per part file. It's quite frugal with the memory when you use the L3 Parser. Thanks, Lars. I think I've displayed datsville in ldglite on a PC with as little as (...) (22 years ago, 20-Dec-02, to lugnet.cad)
|
| | | | |
| | | | | | Re: Large LDraw/MPD Files? —Travis Cobbs
|
| | | | (...) I meant basically what you just said. Ldglite doesn't create a new copy of the part each time it is used; LDView does. I do this for various reasons, but I believe that when I go back and revisit those reasons now with the advantage of (...) (22 years ago, 21-Dec-02, to lugnet.cad, lugnet.cad.dev)
|
| | | | |
