To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cadOpen lugnet.cad in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / *45116 (-10)
  Re: 11-16 primitives?
 
(...) If I understand that, this would mean that we could use a new mklist tool and we can start using that long filenames. The possibility to use MLCad for generating PARTS.LST will be away, but this only a little cut. cu mikeheide (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
 
  Re: 11-16 primitives?
 
(...) Were any other issues anticipated? (...) I did a short test of MLCAD with a modified PARTS.LST. The results were mixed - MLCAD seems OK using an altered-format PARTS.LST file, but re-generating PARTS.LST from MLCAD results in an invalid file. (...) (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
 
  Re: 11-16 primitives?
 
(...) When the LSC updated the spec to allow 21.3 filenames, I don't think any of us were aware that this would create a problem for PARTS.LST. However, looking at the file, there's a chance that MLCAD will work perfectly well with longer filenames (...) (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
 
  Re: 11-16 primitives?
 
(...) Parts Tracker-wise (if I remember right, and if nothing's been changed), there's only one script which needs to be modified to accept 21.3 files instead of 8.3 files. Organizationally, I dunno if there is actually a hold-up. The specifications (...) (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
 
  Re: 11-16 primitives?
 
(...) This is the status quo now for many months. What action has been taken to solve that problem? To me it seems only to be a little adjustment to some lines of code (but maybe I am wrong). So my question would be: where is the bottleneck that (...) (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
 
  Re: 11-16 primitives?
 
(...) Well... imho this should not be an issue at all - if the parts tracker was updated! Philo (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
 
  Re: 11-16 primitives?
 
(...) These truncated filenames never went past the LSC, and as such should probably be held. I personally feel that they are inappropriate, but whether or not I think they are appropriate, I believe that it's the LSC's job to determine that. (...) (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
 
  Re: Tools that output SVG?
 
(...) LDView has experimental SVG/PS/EPS snapshot support, but you have to set a registry key for it to be enabled. Create the following DWORD registry key and set it to 1: HKEY_CURRENT_USER\So...are\Travis Cobbs\LDView\GL2PSAllowed Once you have (...) (15 years ago, 25-Sep-09, to lugnet.cad, FTX)
 
  Re: 11-16 primitives?
 
Hi Steve, (...) One reason: the Parts Tracker still doesn't like >8 names :( Philo (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
 
  Re: 11-16 primitives?
 
(...) I ditto Phillippe's primary suggestion: use multiple files. It's good for multiple reasons. However, the current standards allow at least 25 characters in the filename, so is there a reason to worry about a 9 character primitive name? Steve (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)


Next Page:  5 more | 10 more | 20 more

Redisplay Messages:  All | Compact

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR