 | | Re: Thoughts on File Format for LDraw Animation
|
|
(...) Yes, but you can give the 'files' any name you want inside the MPD. They don't *have* to match the part name outside of the MPD. So you *can* get named parts inside an MPD (with the help of a suitable 'post-processing' program). I certainly (...) (19 years ago, 27-Oct-05, to lugnet.cad.dev)
|
| |
| | Re: Thoughts on File Format for LDraw Animation [DAT]
|
|
(...) Well, hair goes under the category "Hat". It may sound a little strange, but that's the way it has to be. Like I said: 0 FILE Head 0 Name: Head 0 [This Object] 1 16 0 0 0 1 0 0 0 1 0 0 0 1 3626bp01.dat 0 [Child Objects] 1 0 0 0 0 1 0 0 0 1 0 0 (...) (19 years ago, 27-Oct-05, to lugnet.cad.dev)
|
| |
| | Re: Thoughts on File Format for LDraw Animation
|
|
(...) Yes, this is what Anders was trying to get me to understand. The MPD framework provides a name visibility barrier (scope). I still say that LDraw type 1 lines are used to specify hierarchy. The <file> names within the MPD can be used to (...) (19 years ago, 27-Oct-05, to lugnet.cad.dev)
|
| |
| | Re: Thoughts on File Format for LDraw Animation [DAT]
|
|
(...) That's a very good idea I didn't think of! The approach I was thinking of is unnecessarily complicated. Looks like there will be no need for the tags I mentioned earlier. No pain at all. I think all current minifig generators can be easily (...) (19 years ago, 27-Oct-05, to lugnet.cad.dev)
|
| |
| | Re: Thoughts on File Format for LDraw Animation [DAT]
|
|
(...) Um, I'm not sure this has been worked out... I think James was saying that the subfiles in an MPD can be treated as the 'name'. This is true, as long as you also require that each subfile only be used once. So a file like: 0 FILE test1.mpd 1 (...) (19 years ago, 27-Oct-05, to lugnet.cad.dev)
|
