 | | Re: *** MLCad V3.30 ***
|
|
(...) LDView's blending code was originally written to handle LDLite's 0 COLOR syntax, since that is what was originally used in LDConfig.ldr. LDLite's syntax allows for the dithering of two arbitrary colors, either or both of which can themselves (...) (15 years ago, 11-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Flex-system names
|
|
Hi guys, I'm a little confused with the Flex-System naming. We have Flex-System cables (342c01.dat). I found out about these parts' existence only recently on TBs and do not have any. But it seems it's some sort of pull/push mechanism. Then we have (...) (15 years ago, 11-Feb-10, to lugnet.cad)
|
| |
| | Re: Using MPD syntax in official part files
|
|
(...) I think this is a good one: MPD parts would be a great way to store "default" textures for texture mapping (hex encode them). That would encapsulate the design with the part, overcoming one of the big "pain points" of adopting textures. (...) (15 years ago, 11-Feb-10, to lugnet.cad.dat.parts, FTX)
|
| |
| | Re: Warning: Printing Bug in MLCad!
|
|
(...) Exactly! But there is a work-arround patch available - which has to be introduced into the source code :-< Michael (15 years ago, 11-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: Using MPD syntax in official part files
|
|
(...) You know, it occurs to me that if MPD's were allowed as parts, it would be a GREAT place to put a texture file (properly hex encoded, no doubt). They're almost always single-part-only. And if one wanted better textures than "come standard?" (...) (15 years ago, 11-Feb-10, to lugnet.cad.dat.parts, FTX)
|
