 | | Re: 11-16 primitives?
|
| (...) Yeah, I was actually planning a -f to force it to finish and -q for quiet. (...) For now I've added a -8 to make it use the 8.3 format. As per Travis' suggestion it converts to the canonical short form under Windows. The function uppercases (...) (17 years ago, 28-Sep-09, to lugnet.cad.dat.parts.primitives)
| | | | | 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 (...) (17 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 (17 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 (17 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, (...) (17 years ago, 27-Sep-09, to lugnet.cad.dat.parts.primitives)
|
|
