 | | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) Exactly because it's not likely to be used, ever, by mistake. Anyone can put whatever comments they like in a dat, right? So if I write a dat, and want to enter 0 METAL RAIL STARTS HERE and typo it into 0 META LRAIL STARTS HERE (which is a (...) (22 years ago, 16-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) Yep. (...) Exactly. I'll make a side note on the { } issue. One of my goals (as Kevin knows) is to see this software more useable and accessible to general computer users and even kids in the intermediate level on up. I'd like people to have (...) (22 years ago, 16-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) Yup, LEdit chokes on it, just tried it out using unused line type 9 with text after it. D'oh. (...) I know how to use a keyboard. I'm talking convenience on the part of someone editing by hand. {} isn't necessary, so why add it to the mix? (...) (22 years ago, 16-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) As A C programmer, I'm quite adept at { and even } :) A a developer of L-CAD software, I'd rather see the syntax for current meta-commands unchanged. If we were to formalize meta-commands with a syntax change, we'd have to support both old and (...) (22 years ago, 16-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) besides, if we add a new linetype, we're breaking LDRAW.EXE and LEDIT.EXE, wouldn't we? (...) I think that's a great idea :) (...) I'm sorry, I can't understand why it's "too difficult" to enter {} by hand. It's on the standard keyboard. The (...) (22 years ago, 16-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) Remember that it is in the current specification that all META-commands be uppercase. I don't know many people that write with caps-lock on but I'm sure it won't happen enough to be a problem. -Orion (22 years ago, 16-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) I understand the point, but yep - my line of thinking was what you just said, META isn't that common. (...) Ok. (...) Yeah. Well, the suggestion is something new - which ultimately should be considered by a standards body, and not decided upon (...) (22 years ago, 16-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) The main reason I suggested the braces is that they make it basically impossible for the text to show up at the beginning of a standard comment line. In this case, they're probably unnecessary, since META isn't exactly a common word. (...) (...) (22 years ago, 16-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) Right. While a lock would be well meant, it just isn't the right approach. (...) Yep. (...) Not selfish in the least, I don't think. If you're doing this for your own enjoyment, why should you be expected to get a group opinion before adding (...) (22 years ago, 16-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) Right. Sorry -- my support of that was on a quick response, brain fart I suppose. (...) Good goals we should all focus on. (...) Yup, not the first time. I do think we should work through this, stay on task, and get it right this time though. (...) (22 years ago, 16-Mar-03, to lugnet.cad.dev)
|
