Subject:
|
Re: LDScript Suggestions
|
Newsgroups:
|
lugnet.cad
|
Date:
|
Fri, 4 Dec 1998 13:09:19 GMT
|
Viewed:
|
2859 times
|
| |
|
|
Once upon a time, Tore Eriksson <tore.eriksson@mbox325.swipnet.se>
wrote:
> Steve Bliss wrote:
>
> > This is mostly for Tore, but I'll make it public in case anyone wants to
> > agree/disagree.
> >
> > First: thank you for version 0.09. That was a very fast update!
>
> It depends on how you look at it. :)
True.
> I have had plans of making a variant of POLYLINE, namely LINE, with a
> starting P and an ending P
> Example:
> LINE [<colour>] P5 P8
> gives:
> 2 24 X5 Y5 Z5 X6 Y6 Z6
> 2 24 X6 Y6 Z6 X7 Y7 Z7
> 2 24 X7 Y7 Z7 X8 Y8 Z8
> (plus ECHOes and MIRRORs)
Hmm. I'm not sure if that would be as useful -- there'd be all the extra
lines of code to get the points into the Pn list, in the right order.
That would almost offset the convenience of generating the polyline in a
single command. See my idea, below.
> But yes, with a given upper limit of points, I could add POLYLINE, too.
You could use this syntax:
LINE <colour>
POINT <point>
POINT <point>
...
END
maybe even skipping the keyword POINT, if nothing else was allowed
between the LINE and END key-commands.
> > Suggestion 2: Cross-lines in ECHOs
> > One thing ECHO does not generate is a set of lines connecting the
> > orginal points to their echoed complement. This would be a very useful
> > feature.
>
> I have thought of that, but decided not to, for two reasons:
> 1. It would be difficult to avoid crosslines to be doubled, since every
> point currently has to be entered twice.
> 2. Very often, I use ECHO mode in LDS to make curved profiles go 3-D. In
> those cases, the cross-lines should be of type-5. The compiler can
> inpossibly distinguish between when to use type-2 and type-5 lines.
>
> Maybe you could set a mode that generates either type-2 or type-5
> cross-lines for POLYLINEs, but their rules will probably be complicated.
To allow for echoed cross-lines, either as conditional or
non-conditional, and to be more flexible on colors, how about this:
LINE <colour> [CONDITIONAL]
[START <point>]
POINT <point> [NOECHO] [NOCROSS] [NOFILL]
COLOUR <colour>
END [<point>]
The CONDITIONAL keyword indicates that echoed line-commands should be
generated as line-type 5.
The START command and the <point> parameter on the END command give
points to be used for conditional cross-lines. If the CONDITIONAL flag
is not used, these points will be ignored.
The NOECHO, NOCROSS, and NOFILL keywords turn off the various components
of echoing for a single point. NOECHO turns off the echoed line (I
would have used this one already), NOCROSS turns off the cross-line, and
NOFILL turns off the quad.
The COLOUR statement changes the color of the line. This may be used
multiple times.
Did I miss any possible feature?
> > Suggestion 4: Vector Addition
> > I'd like to be able to write:
> > p0 = 10 20 30
> > p1 = 100 200 300
> > p2 = p0+p1
> >
> > and have p2 set to <110, 220, 330>
>
> That's not so easily coded, I think, but it should be very nice. It has
> been
> noted.
OK. This suggestion is low-priority for me. I'm not even sure how I'd
use it, exactly. It seems like it could be useful while initializing
point-values. Especially if I need two sets of points, with one set
being an exact ECHO of the other set.
Steve
|
|
Message is in Reply To:
 | | Re: LDScript Suggestions
|
| (...) It depends on how you look at it. :) (...) I have had plans of making a variant of POLYLINE, namely LINE, with a starting P and an ending P Example: LINE [<colour>] P5 P8 gives: 2 24 X5 Y5 Z5 X6 Y6 Z6 2 24 X6 Y6 Z6 X7 Y7 Z7 2 24 X7 Y7 Z7 X8 (...) (26 years ago, 3-Dec-98, to lugnet.cad)
|
3 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
