 | | Re: Using MPD syntax in official part files
|
|
(...) In lugnet.cad.dat.parts, Joshua Delahunty wrote: (...) In lugnet.cad.dat.parts, Travis Cobbs wrote: (...) I was actually thinking "uuencode" when I wrote this, and used hex for shorthand and because I figured it was more universally (...) (15 years ago, 11-Feb-10, to lugnet.cad.dat.parts, FTX)
|
| |
| | Re: Flex-system names
|
|
(...) Yes, the flex system is a form of push-pull or (URL) Bowden cable>. It was introduced in 1991 and was used on a number of (URL) sets> throughout the 1990s. The cable came in various lengths and there were ends that could be clipped on to (...) (15 years ago, 11-Feb-10, to lugnet.cad, FTX)
|
| |
| | Re: Using MPD syntax in official part files
|
|
(...) Yeah, what he said. (15 years ago, 11-Feb-10, to lugnet.cad.dat.parts, FTX)
|
| |
| | Re: Using MPD syntax in official part files
|
|
(...) I really don't like this idea. I agree that it has the cool property of encapsulating everything in one file, but it has three big problems that I can think of off the top of my head: "Hex" encoding of the texture file increases its size by a (...) (15 years ago, 11-Feb-10, to lugnet.cad.dat.parts, FTX)
|
| |
| | 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)
|
| |
| | Re: Using MPD syntax in official part files
|
|
(...) Yeah, I know what's available at the low end of OpenGl. That's where I live. I was just trying to keep up the curmudgeonly atmosphere of this place with the whipper-snapper comment. Did I do it wrong? Oh well, at least there's still that gloss (...) (15 years ago, 11-Feb-10, to lugnet.cad.dat.parts)
|
