 | | ML-CAD 3.30 Problem while parts authoring
|
|
Hello Michael, I have a problem while parts authoring. When I have insert a new primitive and changing the first time it's values, like the size, evrything works fine. But when I want to change the size or so again. Then the "position & orientation" (...) (14 years ago, 16-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: MLCad.ini 2009-03 Update Now Available
|
|
(...) Willy, You caught most of the parts that got moved to new numbers, except for: 982.DAT 981.DAT Thanks as always for keeping this file up to date. Allen (14 years ago, 15-Feb-10, to lugnet.cad.mlcad, FTX)
|
| |
| | Re: BTW, Dither What Colors...?
|
|
(...) Also I am thinking that we have to use the original color values for the color 0 - 15 to build the blended colors. Otherwise we get other colors. This range should be known by every LDraw related application.and only overwritten by entries (...) (14 years ago, 12-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: BTW, Dither What Colors...?
|
|
--SNIP-- (...) Good thinking. Since the old colours were derived from the EGA colour palette I reckon the dithers would have to be derived from it too. Otherwise you could end up with some very different blends. I like your signature ;) Tim (14 years ago, 12-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: *** MLCad V3.30 ***
|
|
(...) If you have any question regarding this, please don't hesitate to contact me, as I have already made DATHeader using this new feature. (...) Yes, I miss that as they are used in parts already. But others already have answered this question (...) (14 years ago, 11-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: *** MLCad V3.30 ***
|
|
(...) That is exactly what I was thinking about last days. First load MLCad standard colours (like they have been for year). Then replace all the colors for that you will find an entry in the LDConfig.ldr. I would prefer to really keep the blended (...) (14 years ago, 11-Feb-10, to lugnet.cad.mlcad)
|
| |
| | 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 (...) (14 years ago, 11-Feb-10, to lugnet.cad.mlcad)
|
| |
| | 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 (14 years ago, 11-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: *** MLCad V3.30 ***
|
|
(...) I've been surprised by some of this discussion of dithered colors, because when Foundry was created (not by me), it was done as a "clean room" project, based entirely off of specs, so it's the closest thing out there to a reference parser, and (...) (14 years ago, 11-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: Warning: Printing Bug in MLCad!
|
|
(...) It sounds like you already discovered the root cause of this, but just in case you haven't, MFC's CDC::TabbedTextOut() always crashes in Print Preview mode in Visual Studio 2005 Service Pack 1. --Travis (14 years ago, 10-Feb-10, to lugnet.cad.mlcad)
|
