 | | Things for the next part update —Michael Lachmann
|
| | | Hy, today I found a problem in 3040p32.dat line 4 which contains a statement 0 Color update: Bram Lambrecht theoretically fine but it collides with LDLite's and MLCad's COLOR meta command, I don't have a LDLite at the moment to see how it's (...) (25 years ago, 24-Apr-00, to lugnet.cad)
|
| | | |
| | | | | Re: Things for the next part update —Steve Bliss
|
| | | | (...) Good catch! I'll do something around this. (...) There is no stu25.dat. Just copy your stud5.dat to stud25.dat. I'll think about this one... Steve (25 years ago, 25-Apr-00, to lugnet.cad)
|
| | | | |
| | | | | | Re: Things for the next part update —Lars C. Hassing
|
| | | | Steve Bliss wrote... (...) You don't have to. Meta commands MUST be in UPPERCASE! (The only exception is "0 ~Moved to xxx") I just tested with LDraw and ldlite, they don't recognize "0 step", only "0 STEP" /Lars (25 years ago, 25-Apr-00, to lugnet.cad)
|
| | | | |
| | | | | | Re: Things for the next part update —Steve Bliss
|
| | | | (...) Well... (...) Which isn't *exactly* a meta-command. It's the file-title, which contains useful (but redundant) information. (...) Hmmm. Steve (25 years ago, 26-Apr-00, to lugnet.cad)
|
| | | | |
| | | | | | Re: Things for the next part update —Michael Lachmann
|
| | | | (...) <SNIP> (...) <SNIP> (...) Ok, if this is realy true means meta commands have to be UPPERCASE always, then I will update MLCad for the next release to accept only UPPERCASE commands. This would be realy no problem at all. It sounds a bit (...) (25 years ago, 27-Apr-00, to lugnet.cad)
|
| | | | |
| | | | | | Re: Things for the next part update —Don Heyse
|
| | | | | (...) then (...) This caught me by surprise as well. Is this UPPERCASE thing written down anywhere besides this thread? A quick search of the ldraw FAQ and ldlite16.html turns up no occurances of the word "uppercase". If this is an unwritten rule (...) (25 years ago, 27-Apr-00, to lugnet.cad)
|
| | | | | |
| | | | | | | Re: Things for the next part update —Lars C. Hassing
|
| | | | | | (...) The FAQ ((URL) shows uppercase syntax, e.g.: <QUOTE-BEGIN> Step meta-command. Marks the end of a building step. Line format: 0 STEP This command will cause LDraw to stop until you press <enter>, and it will cause LDraw to save the current (...) (25 years ago, 27-Apr-00, to lugnet.cad)
|
| | | | | | |
| | | | | | | | Re: Things for the next part update —Don Heyse
|
| | | | | | (...) Yes all the examples seem to use uppercase, but it's never explicitly stated that it MUST be uppercase. The only thing I could find that came close was a mention in ledit.doc that said the ledit commands were documented in uppercase for (...) (25 years ago, 27-Apr-00, to lugnet.cad)
|
| | | | | | |
| | | | | | Re: Things for the next part update —Lars C. Hassing
|
| | | | | Michael Lachmann wrote... (...) I don't think it is unflexible, it's just a matter of syntax, like C keywords (if/for/while/switch...) MUST be in lowercase. /Lars (25 years ago, 27-Apr-00, to lugnet.cad)
|
| | | | | |
| | | | | | Re: Things for the next part update —Fredrik Glöckner
|
| | | | | (...) Actually, I think it would be much less flexible if all cases were accepted for meta commands. That would seriously limit the kinds of comments one could write in a DAT file! Fredrik (25 years ago, 27-Apr-00, to lugnet.cad)
|
| | | | | |
| | | | | | Re: Things for the next part update —Steve Bliss
|
| | | | (...) I agree, but I can go with the flow on this one. I've always written my meta-commands in uppercase, but written my programs to recognize either. Steve -- A big fan of case-INsensitivity since Modula-2 (25 years ago, 27-Apr-00, to lugnet.cad)
|
| | | | |
