 | | Noting gaps in parts sequences —Todd Lehman
|
| | | I just noticed that the oilcan is missing from the 6246 group: (URL) this because it hasn't been modeled yet (maybe due to its complexity?) or is it just located elsewhere for some historical reason? Anyway, presumably it would go in as 6246F when (...) (25 years ago, 20-Feb-99, to lugnet.cad.dev)
|
| | | |
| | | | | Re: Noting gaps in parts sequences —Steve Bliss
|
| | | | (...) It hasn't been modeled yet because I wanted to get the other parts released without waiting for the oilcan. Then I got distracted. It will be a bit more challenging than the other tools, but now that I've got the LDAO Lathe, and have some (...) (25 years ago, 22-Feb-99, to lugnet.cad.dev)
|
| | | | |
| | | | | | Re: Noting gaps in parts sequences —Todd Lehman
|
| | | | (...) Cool -- that's a neat and extremely low-effort way to get labels! Here's one way to write the program in Perl (also handling spaces and Æ=>AE): $ cat datstart #!/usr/local/bin/perl5 -w my %brick = ( ' ' => "3005", 'Æ' => "3005-AE", map {$_ => (...) (25 years ago, 22-Feb-99, to lugnet.cad.dev)
|
| | | | |
| | | | | | Re: Noting gaps in parts sequences —Steve Bliss
|
| | | | | (...) '8' and '9' aren't currently defined. Also, don't forget to handle other undefined characters (maybe the above does this?) (...) Could {part number} and {author name} be turned into arguments, as well? Actually, if you have a generic app which (...) (25 years ago, 22-Feb-99, to lugnet.cad.dev)
|
| | | | | |
| | | | | | | Re: Noting gaps in parts sequences —Todd Lehman
|
| | | | | | (...) Oh. OK, then the '0'..'9' would be '0'..'7'. (Any idea why 8 & 9 aren't defined? Did LEGO forget to include them or has no one gotten around to DAT-ifying them yet?) (...) These are handled, and mapped into spaces (plain 3005.dat) brick by: my (...) (25 years ago, 22-Feb-99, to lugnet.cad.dev)
|
| | | | | | |
| | | | | | Re: Noting gaps in parts sequences —Todd Lehman
|
| | | | (...) Garrgh! Monkey-florkin spelling checker always converts 'I' to 'I' and won't let me fix it! >%^( --Todd (25 years ago, 22-Feb-99, to lugnet.cad.dev)
|
| | | | |
| | | | | | Re: Noting gaps in parts sequences —Jasper Janssen
|
| | | | (...) Uh-huh.. Converts capital I to capital I. How eville. Jasper (25 years ago, 24-Feb-99, to lugnet.cad.dev)
|
| | | | |
| | | | | | Re: Noting gaps in parts sequences —Todd Lehman
|
| | | | (...) LOL! Ok, now -that- really burns me up. :) Not only does it not let me write lowercase "I", but it doesn't even let me complain about it. That's truly evil. Now the "I" (lowercase) that I just wrote is going to show up as "I" (uppercase). (...) (25 years ago, 24-Feb-99, to lugnet.off-topic.fun)
|
| | | | |
| | | | | | Re: Noting gaps in parts sequences —Todd Lehman
|
| | | | (...) Okie dokie, I figured out how to work around it. There aren't any options in the Gravity spell checker not to convert "i" to "I" (it seems to be some special-case handled by code rather than data), but I fixed the problem by adding "i" to my (...) (25 years ago, 24-Feb-99, to lugnet.off-topic.fun)
|
| | | | |
