 | | Re: 48 directory and non filename only line 1 part file names
|
|
(...) <snip> (...) Is it correct to assume because of this, the 48 and s dirs must not be added to the part search directories list? Roland (18 years ago, 31-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: 48 directory and non filename only line 1 part file names
|
|
(...) I've decided to drop the whole option for now, so the 48 dir is only used if parts reference to it by 48/xxx.dat . Roland (18 years ago, 31-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: 48 directory and non filename only line 1 part file names
|
|
(...) <snip> As might be expected, Steve's replies were correct (as far as I know, anyway ;-). (...) While it's true that this isn't all that useful, it can still be done, even though some parts reference primitives from the 48\ directory directly. (...) (18 years ago, 30-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: 48 directory and non filename only line 1 part file names
|
|
(...) Not exactly. The files in the ldraw\p\48 directory are all based on a 48-faceted approximation of a circle. The regular primitives in ldraw\p are all based on 16-facets. Just because a file is in one directory does not mean a corresponding (...) (18 years ago, 30-Jul-06, to lugnet.cad.dev)
|
| |
| | 48 directory and non filename only line 1 part file names
|
|
Hello all, Still working on the LDraw loader. The 48 directory in ldraw\p, as far I understand it, is a 'alternative' source for primitives, not? Jet I see some (unofficial) files using type 1 lines with the 48\ attached to the part name reference (...) (18 years ago, 29-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) It's my work system, but I rarely use 2005. Most of my customer projects demand use of Delphi 6 Pro. Because that's what the customer itself owns. I maintain their code so I have to use their tools. Because of this I don't justify spending (...) (18 years ago, 27-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) Probably. As I was reading the thread it was *loading* the MPD file that was considered two-pass, and my algorithm is definitely only one-pass for that (and no extra fixups after reading it all). OTOH, if the file should be rendered on screen (...) (18 years ago, 27-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) Don't know about that, source-wise (all my work projects are still Delphi, Win32 only). In .NET you definitely don't have to care about the language an assembly was written in, you just use it. (...) If that is your work development system, I (...) (18 years ago, 27-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) I suspect there's two definitions of "pass" at work here. I would consider a two pass algorithm to be anything requiring two loops (which we must have either way as their is no reference order specified in MPDs). Another way of considering it (...) (18 years ago, 27-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) Actually I can't get my head around 'searching for a file in the cache' as equivalent to 'do a second pass of the source file'. Every part is searched for in the cache. Each source line is only read and parsed once. What am I not (...) (18 years ago, 26-Jul-06, to lugnet.cad.dev)
|
