|
|
 | | Re: 11-16 primitives?
|
| (...) For MLCAD it doesn't matter. Steve said that MLCAD worked fine with long filenames inside parts.lst. The only reason to put the short filename in is for other programs that might have problems with the long filename. And as long as mklist is (...) (15 years ago, 27-Sep-09, to lugnet.cad.dat.parts.primitives)
| | | | | Re: 11-16 primitives?
|
| (...) Sounds easy, but I think nobody can read that short filenames that would appear in the MLCad list!? cu mikeheide (15 years ago, 27-Sep-09, to lugnet.cad.dat.parts.primitives)
| | | | | Re: 11-16 primitives?
|
| (...) If it's running in Windows, I think a backwards-compatible switch should use the Win32 API to get the short filename (with the ~1 at the end, usually, determined using PathGetShortPath) and use that in place of the long filename. --Travis (15 years ago, 27-Sep-09, to lugnet.cad.dat.parts.primitives)
| | | | | Re: 11-16 primitives?
|
| (...) That would be good, I think. (...) Can you have two levels? Level One that still shows the warnings, but doesn't stop, and Level Two suppresses all warnings. (...) I'd keep the current line-format for all parts conforming to the 8.3 format, (...) (15 years ago, 27-Sep-09, to lugnet.cad.dat.parts.primitives)
| | | | | DATHeader Update (The Reviewer Tool) Version 2.0.8
|
| Just uploaded a new version. New in Version 2.0.8 (Released 27.09.2009) 1) Now detailed scan is disabled if any change has been made. (This was necessary, as detailed scan needs the line number.) 2) History Dialog made new. 3) If last line is only (...) (15 years ago, 27-Sep-09, to lugnet.cad, lugnet.announce)
|
|
