| | Re: Category Statement
|
|
(...) In lugnet.cad.dev, Steve Bliss writes: (...) I would like to add those headers to my part files. I remember I've asked this before, I did get an answer back then, but it wasn't very clear to me. I discontinued the thread, because I didn't have (...) (24 years ago, 9-Jul-00, to lugnet.cad.dev)
|
|
| | Re: Category Statement
|
|
I thought about a new feature in MLCad where the user can define his own groups to be show in the part preview and in the part tree. Each group will have a certain rule (search criteria) which assigns parts to this groups. The part assignment is (...) (24 years ago, 8-Jul-00, to lugnet.cad.dev)
|
|
| | Re: Partial list of parts for 2000-02 Update
|
|
(...) I have a beef with this. The NAME I gave this was "Castle Greatsword" (not "Minifig Accessory Sword Large"). Now, if I understand correctly, you want to eventually migrate all minifig accessories *away* from the "Castle" (and "Pirate") (...) (24 years ago, 8-Jul-00, to lugnet.cad.dev)
|
|
| | Re: New Parts Category: Cockpit
|
|
(...) Does anyone else see things the same way as Jonathan does? It's not what I had been thinking, but Cockpit could be defined to include both the base parts and the canopy parts. The only thing is this: Windscreen is a fairly cleanly- defined (...) (24 years ago, 7-Jul-00, to lugnet.cad.dev)
|
|
| | Re: New Parts Category: Cockpit
|
|
Talking about the subject summarized at: (...) I think canopy pieces should probably stay in the Windscreen group. I can see putting the Space Nose and Space Cabin Base pieces in a Cockpit group. There's not really any other place to stick them, (...) (24 years ago, 7-Jul-00, to lugnet.cad.dev)
|
|
| | Re: Category Statement
|
|
(...) I'd say there are no plans to add statements for all part files. The 'default value' for category is the first word in the partname. Since, 3001.dat doesn't have a 0 CATEGORY statement, its category comes from the part name, and the category (...) (24 years ago, 7-Jul-00, to lugnet.cad.dev)
|
|
| | Re: Speaking of colors...
|
|
(...) Silver looks more like brushed aluminum. (...) I think so -- it appears that the new silver is actually the color of the plastic, not a post-molding layer that's plated onto the parts. (...) suggestions being trans-black, 32, or trans-dark (...) (24 years ago, 7-Jul-00, to lugnet.cad.dev)
|
|
| | Category Statement
|
|
I thought about making use of the category statement in MLCad. This would have allowed to group the parts by category rather than by name or something else .... ... but I did a quick check on the parts and found out that only arround 5% of the parts (...) (24 years ago, 7-Jul-00, to lugnet.cad.dev)
|
|
| | Re: Speaking of colors...
|
|
(...) I think it makes sense to use a special code for rubber, and 256 sounds like a good choice. (...) Let's see. In LDraw, if dithered color K is constructed out of solid colors I and J as 256 + I * 16 + J, I believe the edge-color of K will be (...) (24 years ago, 7-Jul-00, to lugnet.cad.dev)
|
|
| | Re: Speaking of colors...
|
|
Color 256 for Black Rubber was suggested by John VanZwieten one year ago, see eg. (URL) haven't received any suggestions for the POV setting for rubber, so I just turned off reflection. I announced the special treatment of color 256 three weeks ago: (...) (24 years ago, 7-Jul-00, to lugnet.cad.dev)
|