 | | Re: Problems with LDCfgalt.ldr and between LDConfig.ldr and LDDP
|
|
(...) I was wondering what this file was for. I wish I had known, as I really prefer colored edges. I have been providing a colored edge LDconfig file with my software that converts it for MLCAD use: (URL) you want to give my file a try, would it (...) (15 years ago, 30-Sep-09, to lugnet.cad)
|
| |
| | Re: Problems with LDCfgalt.ldr and between LDConfig.ldr and LDDP
|
|
(...) People? You mean person. I think the only real reason for creating that file in the first place was to hush my whining about boring colors. (URL) got a nice laugh from the delicious irony of stealthily replacing the shiny candy colors with the (...) (15 years ago, 30-Sep-09, to lugnet.cad)
|
| |
| | Re: Quirks with Peeron part inventory images
|
|
(...) FYI, this problem now appears to be resolved - I now see the correct part images in the inventory mentioned above. Thanks, Jim (15 years ago, 30-Sep-09, to lugnet.cad)
|
| |
| | Re: 11-16 primitives?
|
|
(...) In the mklist beta I posted there's an undocumented -r switch to turn off the ragged edges and make room for 25 char filenames. There's also an undocumented -t to twiddle with the 78 vs 80 character line formats. But there's nothing yet for (...) (15 years ago, 29-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
Sorry to follow-up my own post, but I did a quick test on MLCAD. (...) I had a DUH! moment after posting the previous message. If MLCAD can use a ragged format file, of course it can use a fixed-25 format file. DOH. (...) I prepared a PARTS.LST file (...) (15 years ago, 29-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | mklist 1.6beta1
|
|
(...) I'm assuming the 80 char lines is what you're aiming for here, so based on the 64 char limit on descriptions I started the descriptions on the 16th character of the line. That gives room for a 15 character name and a single space before the (...) (15 years ago, 29-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Problems with LDCfgalt.ldr and between LDConfig.ldr and LDDP
|
|
(...) I seem to remember that part of the reason to have LDCfgalt.ldr was for people who prefer the colored edge lines. Actually, it seems like that was a big part of the reason to have the file. So why drop that functionality? Steve (15 years ago, 29-Sep-09, to lugnet.cad)
|
| |
| | Re: 11-16 primitives?
|
|
(...) My thinking is the 'ragged' format has the least impact - if there are no long part nambers, then the output PARTS.LST would exactly match the classic format, without the user having to know anything about long/short part nambers. Of course, (...) (15 years ago, 29-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Problems with LDCfgalt.ldr and between LDConfig.ldr and LDDP
|
|
(...) LDCfgalt.ldr has been kept for backwards compatibility but colors have been substituted with grey to encourage the shift to the new LDConfig.ldr file and colors. w. (15 years ago, 29-Sep-09, to lugnet.cad)
|
| |
| | Problems with LDCfgalt.ldr and between LDConfig.ldr and LDDP
|
|
I noticed two issues with the new versions of LDConfig.ldr: - LDCfgalt.ldr contains only grey colors (#c1c1c1) with black edge. Though I never used LDCfgalt this seems weird to me. - When I install the new LDConfig.ldr, LDDP replacement feature is (...) (15 years ago, 29-Sep-09, to lugnet.cad)
|
| |
| | Re: Quirks with Peeron part inventory images
|
|
(...) Hmmm. All the images are re-generated as part of a Parts Update, so that's probably the source of this problem. But nothing has changed in that process since 2009-01. However, at around that time there were problems with the server where these (...) (15 years ago, 29-Sep-09, to lugnet.cad)
|
| |
| | Quirks with Peeron part inventory images
|
|
Hi all, I was perusing a Peeron inventory and noticed the wrong images were displayed for a few parts. Parts 3062b, 6233, and 6019 are displayed as other parts in the following inventory: (URL) is a screenshot just in case it is a temporary problem: (...) (15 years ago, 29-Sep-09, to lugnet.cad)
|
| |
| | 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 (...) (15 years ago, 28-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: LD4DStudio 1.1 Beta 3 Released
|
|
(...) Hello Mike, I've looked at those specs when I worked on the program but it seemed, to me, in a very early stage of development. So I build the 'suggestion database' instead for the time being. Also the proposed information far surpasses the (...) (15 years ago, 28-Sep-09, to lugnet.cad)
|
| |
| | Re: LD4DStudio 1.1 Beta 3 Released
|
|
I was wondering if your program uses same format as or could output to the LDraw Connection Database? (URL) would be cool to have a single database for connections, and even allow users to "submit" newly discovered connections just by using your (...) (15 years ago, 27-Sep-09, to lugnet.cad)
|
| |
| | 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)
|
