To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cad.devOpen lugnet.cad.dev in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / Development / 5627
5626  |  5628
Subject: 
Re: numbers for "Castle" minifig torso patterns?...
Newsgroups: 
lugnet.cad.dev
Date: 
Wed, 29 Nov 2000 20:23:44 GMT
Viewed: 
665 times
  
In lugnet.cad.dev, Chris Dee writes:

Based on recent discussions here, I think we have agreed
to allow alpha characters after the "p",
to prevent pxx number expanfding to three digits
(not a problem for 973pxx, but potentially for 3626bpxx and similar).

I remember it being discussed, but I don't recall any agreement.
The flaw I saw with this proposal is, is the file "973p4a.dat"
an independent part all its own, or is it merely the first _sub_part
of "973p4.dat"?

The more I've been thinking about it, the more I'm liking what I do
here on my own hard drive: _extra_ sub-directories.  For example:

PARTS\
PARTS\973.DAT
PARTS\973\
PARTS\973\P108.DAT
PARTS\973\P108A.DAT
PARTS\973\P108B.DAT
PARTS\973\P109.DAT
PARTS\973\P109A.DAT
PARTS\973\P109B.DAT
PARTS\3626B.DAT
PARTS\3626B\
PARTS\3626B\P108.DAT
PARTS\3626B\P108A.DAT
PARTS\3626B\P108B.DAT
PARTS\3626B\P109.DAT
PARTS\3626B\P109A.DAT
PARTS\3626B\P109B.DAT

I am _not_ suggesting that we could realistically or conveniently
implement this alternative solution for _every_ part that has patterns,
but I _do_ think that it's a viable alternative for those parts
that have a large number of patterns (or the _potential_ for
a large number of patterns, i.e., minifig torso and head patterns,
and decorated slopes and tiles).

But I digress...

Getting back to my critique of the "alphanumeric" proposal,
I also don't like the idea of an alphabetic character
as the first "digit" of the pattern number, because
that is _also_ where a part-number _suffix_ would go
(as I believe Steve pointed out).

However, I _do_ like the option of adding a two-character
alpha_BETIC_ (and _not_ alphaNUMERIC) pattern number range.
Thus, whenever we see "p11" or "pgq", we will _know_
that the "11" or "gq" respectively is _without_a_doubt_
the pattern number.  We could re-sequence the StarWars patterns
as "paa", "pab", "pac", "pad", (etc.), thus keeping them together.

In the case of a subpart for an alphabetic pattern number,
the subfile would use a numeric suffix, e.g., the first
subpart of "paa" would be "paa1", and so on.

Thoughts?

Franklin



Message has 1 Reply:
  Re: numbers for "Castle" minifig torso patterns?...
 
(...) I see three reasons why this argument may be flawed, but I think we are confusing the meaning of subpart. 1) The Pxx number are all two digits, so 973p4.dat should never exist. 2) The same pattern on a part varient would be demand a suffix for (...) (24 years ago, 29-Nov-00, to lugnet.cad.dev)

Message is in Reply To:
  Re: numbers for "Castle" minifig torso patterns?...
 
(...) Based on recent discussions here, I think we have agreed to allow alpha characters after the "p", to prevent pxx number expanfding to three digits (not a problem for 973pxx, but potentially for 3626bpxx and similar). That means that we can (...) (24 years ago, 29-Nov-00, to lugnet.cad.dev)

5 Messages in This Thread:

Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact

This Message and its Replies on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR