 | | Re: What does a subpart with color=24 mean?
|
|
(...) Right... but what should the contrast color be defined as within the subfile? The same? >> Mark (18 years ago, 5-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: What does a subpart with color=24 mean?
|
|
(...) Not exactly -- just use the current contrast color as the main color for the subfile. Whenever a subfile is rendered, it should already be looking up the local contrast color based on the local main color. Steve (18 years ago, 5-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: What does a subpart with color=24 mean?
|
|
(...) Does that mean that it would be appropriate for a renderer to just swap the main and contrast colors when it encounters such a line, or what? I just want know what a renderer is supposed to do. (...) Well, doing grep '^1 24 ' on the parts (...) (18 years ago, 5-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: What does a subpart with color=24 mean?
|
|
(...) It will be the constrast color for the constrast color. Which may be the same as the main color -- but it may not. Also, some viewers (like L3Lab) may balk at rendering a file which uses color 24 in a line type 1. Steve (18 years ago, 5-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: What does a subpart with color=24 mean?
|
|
(...) OK, I was partly right. There actually is a standard defined for colour extensions, you can view it here (URL) it only applies to colours defined either in ldconfig.ldr, or in the part files or model files themselves. And it is still up to the (...) (18 years ago, 5-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: What does a subpart with color=24 mean?
|
|
(...) Hi Mark, I'm pretty sure there is no standard for that, and it depends on which renderer you use. ROSCO (18 years ago, 5-Sep-06, to lugnet.cad.dev)
|
| |
| | What does a subpart with color=24 mean?
|
|
How is the contrast color defined for line type 1, when color=24? >> Mark (18 years ago, 5-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: Proposal for MLCad.ini Enhancements
|
|
(...) hi allen, many thx for the .ini file fixes you sent me via mail. I'll load them up asap. the rest is michael's territory as I'm only the maintainer of the data. bye, w. (18 years ago, 19-Aug-06, to lugnet.cad.dev)
|
| |
| | Proposal for MLCad.ini Enhancements
|
|
In the course of writing a minifigure generator for my Bricksmith program, I've really come to appreciate how nifty it is to have something like the MLCad.ini file to work with. I've very grateful to the people who designed and maintain it. However, (...) (18 years ago, 18-Aug-06, to lugnet.cad.dev, FTX)
|
| |
| | Re: 48 directory and non filename only line 1 part file names
|
|
(...) Yes, basically. It wouldn't make any sense to add the parts\s directory, because those files are segments of parts -- they aren't complete objects in any sense. They are only intended to be used by part files, which should refer to them (...) (18 years ago, 31-Jul-06, to lugnet.cad.dev)
|
| |
| | 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)
|
