Subject:
|
Re: BRICKFEST MOONBASE (follow-up count)
|
Newsgroups:
|
lugnet.admin.nntp
|
Date:
|
Thu, 5 Jun 2003 21:56:49 GMT
|
Viewed:
|
2718 times
|
| |
|
|
As an experiment I posted the below-quoted message from my NNTP newsreader by
using the Content-Type: text/x-ftx header. It worked! Only trouble is, it
didn’t recognize my signature file. Signature files should be treated as
literal text when submitted using a newsreader; otherwise I’d have to have a
separate .signature just for FTX posts.
I notice in the “Preview” that it trimmed the signature. I don’t think it
should do that autmoatically, but instead should use the same “fix it for me”
approach that is triggered by my top-quoting in this case. (Though I think that
top-quoting is appropriate in this context...)
--Bill.
In lugnet.events.brickfest, William R. Ward wrote:
| |
Frank Filz ffilz@mindspring.com writes:
| |
At NW BrickCon we had monorail track at +0, +10, and +20 (and even a
small amount at +30 I think). +20 was necessary to clear most modules
since it turns out it’s easiest to just run the track whereever.
However, if a station is actually built into a module, there also needs
to be an X-Y standard. I think the simple standard is to start with a
basis of a piece of straight monorail has it’s centerline along the
boundary between two modules, and starts at one end of the module (so
three straights would exactly cover the boundary between 4 modules).
Then from this, any offset of 8 studs can be accomodated. If several
modules with built in track are intended to be placed close together,
more care must be taken because you won’t have the space to put in 8
stud track segments to adjust track positions.
|
David Wegmuller worked out a standard last summer that I think should
be adopted. See http://news.lugnet.com/space/?n=16346 and the
ensuing thread.
--Bill.
|
|
|
Message has 1 Reply:
 | | Re: BRICKFEST MOONBASE (follow-up count)
|
| (...) Oh, BTW, the use of the 'Content-Type:' header isn't guaranteed to be supported forever. The server now posts FTX messages using a different header, because 'Content-Type: text/x-ftx' was causing problems for MSOE users (and some other (...) (21 years ago, 5-Jun-03, to lugnet.admin.nntp, FTX)
|
4 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
