 | | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
(...) Speaking of which, that 3002peye is one of those early mistakes that needs to be fixed. -- Terry K -- (25 years ago, 7-Jul-99, to lugnet.cad.dev, lugnet.general)
|
| |
| | Re: LDraw Parts Update 9905
|
|
(...) I have no problem with LEdit using the installed version of piece 30359. That is the piece you mean, right? Email me the part file you have and I will check to see if it causes a problem. -- Terry K -- (25 years ago, 7-Jul-99, to lugnet.cad.dev, lugnet.cad)
|
| |
| | Re: LDraw Parts Update 9905
|
|
(...) there is a serious bug in 9905. using the laser piece in ledit crashes ledit. someone want to take a look at the problem??? ldlite gives a syntax error on line 126 for the part but there is nothing wrong with line 126 that i can see. (25 years ago, 7-Jul-99, to lugnet.cad.dev, lugnet.cad)
|
| |
| | (canceled)
|
|
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
Simon Robinson wrote in message ... (...) and (...) Hey, those aren't "hollow space wheels", they're "podracer jet engines"... Frank (25 years ago, 7-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general)
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
Todd Lehman wrote in message ... (...) problem... in the above database, part 3002 is a 2x3 brick, part 3002PEYE is a 2x2 brick with printing of an eye). Frank (25 years ago, 7-Jul-99, to lugnet.cad.dev, lugnet.general)
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
(...) I'd agree. In principle, where bricks do have obvious uses you'd need to keep that use in the name for simplicity. After all, I'm sure it wouldn't be too hard to find some exotic uses for wheels, but is anyone seriously going to suggest that (...) (25 years ago, 7-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general)
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
John Matthews wrote in message ... (...) different (...) I think parts descriptions have to assume a "top/up" of a part, otherwise, we'll have really long names" "5x5x2 rectangular piece with one stud centered on one 5x5 face with hollow on (...) (25 years ago, 7-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general)
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
(...) Correction: it would be bad to put each image *only* on a separate web page. Right? It really needs both (or multiple) types of displays. Here are a couple of crude, semi-working examples... * One piece: (URL) A bunch of pieces in a numeric (...) (25 years ago, 7-Jul-99, to lugnet.cad.dev, lugnet.general)
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
(...) Words can't be copyrighted (well, maybe supercalifrigilistic...alidocious can be :-) but trademark searches are free at the USPTO (but they're delayed by 2 months so that they can charge fees for up-to-date searches). USPTO search of their (...) (25 years ago, 7-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general)
|
