 | | Re: Part Numbering Crisis in LDraw
|
|
(...) The problem with that solution is that we would then have the 4106548 hard coded as yellow. And when the tan version is released are we then going to have another 410xxxx for it - hard coded to tan? That may not seem like a big deal, until you (...) (25 years ago, 27-Feb-99, to lugnet.cad.dev)
|
| |
| | Re: Part Numbering Crisis in LDraw
|
|
(...) Is it not possible to say in the definition of 410etc., like: top half yellow, lower half yellow underneath. That way, the only information in the 410etc file is the color, and which constituents parts there are. Then if anything needs to (...) (25 years ago, 27-Feb-99, to lugnet.cad.dev)
|
| |
| | Re: Part Numbering Crisis in LDraw
|
|
(...) I concur. Part of the beauty and flexibility of LDraw is that you can model with parts in colors that those parts don't come in. Once we start down the road of having parts hard coded only in the color(s) they really exist in, we limit our (...) (25 years ago, 27-Feb-99, to lugnet.cad.dev)
|
| |
| | Re: Part Numbering Crisis in LDraw
|
|
(...) method > for other parts - parts that may well come in many colors. Then, using that (...) I > would prefer to have one basic version of the part, color being > user-selectable. (...) But it would be nice to at least have a .dat file for each (...) (25 years ago, 27-Feb-99, to lugnet.cad.dev)
|
| |
| | Re: Part Numbering Crisis in LDraw
|
|
(...) That's not much better, because a new part-file is still required whenever a new color is released. Steve "I should probably keep these responses in the outbox until after I've read all 60 incoming messages" Bliss (25 years ago, 1-Mar-99, to lugnet.cad.dev)
|
| |
| | Re: Part Numbering Crisis in LDraw
|
|
(...) Why don't we reference these part numbers as comments in the part-file, perhaps on a 0 KEYWORDS line? Although that would be a headache to deal with, making sure that all new parts get all the appropriate part numbers... Steve (25 years ago, 1-Mar-99, to lugnet.cad.dev)
|
| |
| | Re: Part Numbering Crisis in LDraw
|
|
(...) about (...) part (...) That still wouldn't make it possible in Ldraw to (I)nsert a new piece, change the (P)art number, then type the part number of the part which is in your hand, and have it inserted. Multi-part parts are a problem, of (...) (25 years ago, 1-Mar-99, to lugnet.cad.dev)
|
| |
| | Re: Part Numbering Crisis in LDraw
|
|
(...) True, you wouldn't be able to use the related part numbers as parts, but you could search for them (especially once some software uses the KEYWORDS and CATEGORY meta-commands) (...) That would be the problem. Are these real parts, or not? If (...) (25 years ago, 1-Mar-99, to lugnet.cad.dev)
|
| |
| | Re: Part Numbering Crisis in LDraw
|
|
(...) Why's that such a big problem? I mean... it's not like a 20 byte part file, or 10000 of them, will take up a significant amount of space. Especially zipped, when you don't have to worry about cluster sizes. By the time there are so many (...) (25 years ago, 1-Mar-99, to lugnet.cad.dev)
|
| |
| | Re: Part Numbering Crisis in LDraw
|
|
(...) The big problem is someone has to notice the new color, and then someone has to make the change in the next part update. Why subject ourselves to this headache? (...) But we aren't zipped, and there are plenty of people with Win95/FAT16 hard (...) (25 years ago, 2-Mar-99, to lugnet.cad.dev)
|
| |
| | Re: Part Numbering Crisis in LDraw
|
|
Terry K (legoverse@geocities.com) comments Karim's "30086.dat" and "30087.dat" in colour 16, and "4106548.dat" in yellow/yellow suggestion (which I support): (...) Yes. The problem is that this is a multi-mold part which is likely to appear in (...) (25 years ago, 5-Mar-99, to lugnet.cad.dev)
|
| |
| | Re: Part Numbering Crisis in LDraw
|
|
(...) For now, that would be a good solution. Of course, Steve would need to split the pieces first. (...) I finally just released it as 104.dat in color 16. A compromise of sorts. The problem is, other pieces will (do) have the same problem. The (...) (25 years ago, 6-Mar-99, to lugnet.cad.dev)
|
| |
| | Re: Part Numbering Crisis in LDraw
|
|
(...) I'll look into it. The main problems are (1) I'm not sure it can be done without rewriting the existing code, which I don't *really* feel like doing. And (2) I'm not planning on cutting a dinghy open to see what the inside looks like. So any (...) (25 years ago, 8-Mar-99, to lugnet.cad.dev)
|
| |
| | Re: Part Numbering Crisis in LDraw
|
|
(...) 1. Understood. 2. That's a given. I don't really expect to see detail. It is not something that would be a requirement, IMO. (...) No idea. It was news to me. Joshua might know something about it, but he never mentioned that one to me. (...) I (...) (25 years ago, 9-Mar-99, to lugnet.cad.dev)
|
| |
| | Re: Part Numbering Crisis in LDraw
|
|
(...) You rang? :-P The pink raft (dinghy is too much typing :-) can be seen here: (URL) Now the canoe is a different matter....... Oh gawd. :-P When even *I* get the joke, it's old news Terry. -- joshua (25 years ago, 10-Mar-99, to lugnet.cad.dev)
|
| |
| | Re: Part Numbering Crisis in LDraw
|
|
(...) At this point, after this much time, I consider the canoe to be a time-honored joke. To be used at every available opportunity. :-) -- Terry K -- (25 years ago, 11-Mar-99, to lugnet.cad.dev)
|
