 | | Re: Assembled parts, ~ and categories —Michael Heidemann
|
| | | (...) There is one document that introduced this. (URL) found we have different problems to solve: 1) Usage of the tilde '~' for files in the \s folder. 2) Usage of the tilde '~' for files in the \parts folder 3) Is the tilde '~' part of the (...) (15 years ago, 3-Jun-09, to lugnet.cad)
|
| | | |
| | | | | Re: Assembled parts, ~ and categories —Michael Heidemann
|
| | | | | (...) As I am in the beta testing for the new DATHeader I need to have decisions for the above questions. At present many of the above is mixed on the PT. cu mikeheide (15 years ago, 13-Nov-09, to lugnet.cad)
|
| | | | | |
| | | | | | | Re: Assembled parts, ~ and categories —Chris Dee
|
| | | | | | (...) 1) the leading ~ should be enforced for files in parts/s. 2a) a leading ~ is optional for files in parts, but should be present for physical components that are always delivered in combination with another. 2b) we need a better way to deal (...) (15 years ago, 13-Nov-09, to lugnet.cad)
|
| | | | | | |
| | | | | | | | Re: Assembled parts, ~ and categories —Michael Heidemann
|
| | | | | | | (...) Thanks for make that clear now. I have just also link this post in the wiki ((URL) so we can find it much quicker in the future. I have also put there a lot of other stuff that I feel we should keep for future use. cu mikeheide (15 years ago, 14-Nov-09, to lugnet.cad)
|
| | | | | | | |
| | | | | | | | Re: Assembled parts, ~ and categories —Willy Tschager
|
| | | | | | (...) Working with the new version 3.1 I've announced today you'll notice that we included unhidden version of the Minifig Chain and String parts along with the LSynth constraints to work around this problem so changing the standard is no longer key (...) (15 years ago, 18-Nov-09, to lugnet.cad)
|
| | | | | | |
| | | | | Re: Assembled parts, ~ and categories —Sergio Reano
|
| | | | (...) Hi, I read the above article and is OK, but many parts do not follow these requirements: for example part 71427C01.DAT distributed as official is named as assembly but contains the whole part definition inside with no references to any (...) (15 years ago, 18-Nov-09, to lugnet.cad)
|
| | | | |
| | | | | | Re: Assembled parts, ~ and categories —Michael Heidemann
|
| | | | | (...) The part you mentioned is certified a long time ago and rules changes over the time. So you will find surely old part in the library that are not according our current rules. Also the ...Cxx only advices that the real part is assembled by some (...) (15 years ago, 18-Nov-09, to lugnet.cad)
|
| | | | | |
| | | | | | Re: Assembled parts, ~ and categories —Chris Dee
|
| | | | (...) Please understand that the LDraw Parts Library is over 12 years old and standards evolve over time. Things that were done in 1999, when 71427c01.dat was created, wouldn't necessarily be done the same way now. *dNN.dat files are parts with (...) (15 years ago, 18-Nov-09, to lugnet.cad)
|
| | | | |
| | | | | | Re: Assembled parts, ~ and categories —Sergio Reano
|
| | | | (...) I can understand the problem of aged parts, but, again from a programmer approach, I have to manage both "old" and "new" parts, so it will be very helpful if all parts can follow the same coding and naming standard. Please, consider the (...) (15 years ago, 19-Nov-09, to lugnet.cad)
|
| | | | |
| | | | | | Re: Assembled parts, ~ and categories —Chris Dee
|
| | | | (...) Maybe you are trying to interpret too much from the naming convention. A composite part (*cNN.dat) isn't necessarily comprised of parts that can move relative to each other, It might just be made of two or more separately moulded elements that (...) (15 years ago, 19-Nov-09, to lugnet.cad)
|
| | | | |
