 | | Re: Trouble creating building instructions using lpub and mpd file
|
|
(...) I used them until I got a VERY bizarre image of the 10016 tanker in L3p/PovRay. I promptly switched to using hyphens prefixed by the model id :) (20 years ago, 10-Apr-05, to lugnet.cad, lugnet.cad.mlcad)
|
| |
| | Re: Trouble creating building instructions using lpub and mpd file
|
|
(...) Well, technically ldlite has been around since well before MLCad, and it supports the double quotes, but MLCad is more widely used. So I guess you could make that argument either way. (...) I only asked for a recommendation, not a requirement. (...) (20 years ago, 10-Apr-05, to lugnet.cad, lugnet.cad.mlcad)
|
| |
| | Re: Trouble creating building instructions using lpub and mpd file
|
|
(...) I'll do the same. (...) Hi Don, Nice post. GROUP commands are defined outside the LDraw spec, but I'd guess that the naming issues are the same. I just made a minor change to: 0 PLIST BEGIN SUB <file> // depricated 0 LPUB PLI BEGIN SUB <file> (...) (20 years ago, 10-Apr-05, to lugnet.cad, lugnet.cad.mlcad)
|
| |
| | Re: Trouble creating building instructions using lpub and mpd file
|
|
Hmmm, I'm not sure if this effort is actually making things more compatible. (...) I just did a little testing myself. MLCad seems to strip off any whitespace (tabs and space characters) at the end of the line when it grabs the filename. Is that (...) (20 years ago, 10-Apr-05, to lugnet.cad, lugnet.cad.mlcad)
|
| |
| | Re: Trouble creating building instructions using lpub and mpd file
|
|
(...) I am currently going through the L3P code and I have now added support for filenames with spaces, both in linetype 1 and in "0 FILE xxx". It now uses the rest of the line as the filename. It also accepts filenames in double-quotes. /Lars (20 years ago, 10-Apr-05, to lugnet.cad, lugnet.cad.mlcad)
|
| |
| | Re: Trouble creating building instructions using lpub and mpd file
|
|
(...) Hi Don, Using MLCad as a benchmark, the name with blanks is *not* enclosed in quotes. I use the remainder of the line, sans end of line as the file name. Alas, my efforts are for naught. L3P quietly ignores the lines that have names with (...) (20 years ago, 8-Apr-05, to lugnet.cad, lugnet.cad.mlcad)
|
| |
| | Re: Trouble creating building instructions using lpub and mpd file
|
|
(...) I think you made the right decision, but I have a question. Do the filenames with embedded spaces have quotes around them, or do they just use up all the space to the end of the LDRAW type 1 command line? The reason I ask is because I seem to (...) (20 years ago, 8-Apr-05, to lugnet.cad, lugnet.cad.mlcad)
|
| |
| | Re: Trouble creating building instructions using lpub and mpd file
|
|
In lugnet.cad, Allan Bedford wrote: snip (...) snip (...) snip (...) Allan, Your opinions are valued. Thanks. I decided to take the pragmatic way out, and adjust my parsing to support file names with blanks. I think that warnings will lead to just (...) (20 years ago, 8-Apr-05, to lugnet.cad, lugnet.cad.mlcad, FTX)
|
| |
| | Re: MLCAD 'FIND' function
|
|
Hi Ludo, "ludo soete" <ludo.soete@village.uunet.be> schrieb im Newsbeitrag news:IEBCD9.1zAH@lugnet.com... (...) 'Find' (...) You mean a find function inside the model, instead of a find function in the library right? Basically this is possible. I'll (...) (20 years ago, 6-Apr-05, to lugnet.cad.mlcad)
|
| |
| | Re: Trouble creating building instructions using lpub and mpd file
|
|
(...) You are right, but the error handling problem is larget than just blanks in file names. All of this boils down to the wimpy method that LPub uses to parse LDraw files. If you type in a meta-command “0 LPUB PIL”, rather than “0 LPUB PLI”, lpub (...) (20 years ago, 6-Apr-05, to lugnet.cad, lugnet.cad.mlcad, FTX)
|
