Subject:
|
Re: Object Orientation & DAT files & CLIPPING/WINDING
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Wed, 20 Oct 1999 11:40:46 GMT
|
Reply-To:
|
Rui.Martins@link!saynotospam!.pt
|
Viewed:
|
623 times
|
| |
|
|
On Tue, 19 Oct 1999, Lars C. Hassing wrote:
> Rui Martins wrote in message ...
> > FIRST OF ALL
> > my sugestion is that the CLIPPING, WINDING, INVERT are strictly local
> > where they are used.
>
> I concur that WINDING is strictly local.
Great!
> It may be a struggle of words, but I wouldn't call INVERT *local* as it
> affects the behaviour all tris/quads in *subfiles*
It's local when you look at it in the .DAT where it is used.
It's effect is NOT local, when you are looking from the renderer
program's view, because it has to keep track of the current invert
state.
The INVERT meta-command only says, INVERT relative to the CURRENT invert
STATE.
A .DAT files does not know if it will be called, with an odd or even
invert state, so his infromation ofshould invert is local, but the
notion of the current GLOBAL state of invertion is GLOBAL but for the
renderer not the .DAT file.
Maybe this is a litle bit confusing, or I can't explain myself
correctly.
> And I don't see why clipping should be local. If you for some reason
> want to turn clipping off for some subfiles, you should be able to do that.
> If you are making a flag on a flag-pole, the flag-pole is solid and you
> can use clipping. But the flag may be 2D and you would want to turn
> clipping off for e.g. a reference to rect.dat.
> A "CLIPPING ON" in rect.dat should not suddenly enable clipping.
I should congratulate you, you found the only example, that I know of
that is against a local clipping.
But how often will this be done ?
BUT if this is required, when optimizing the rect.dat, just don't insert
a 0 CLIPPING ON on it.
Offcourse, someone will say, " And what about the files that use
rect.dat that would benefit from clipping the rectangle when possible ?"
For this I say:
Since this is for this (or other) special case then create a specific
S_rect.dat witch does NOT clip, or even,
since this problem only relates to paper thick surfaces, usually
simple, just include it's code in your part, and disable clipping for it.
NOTE: we should optimize for the general/common cases, not for the
specific anyway.
Rui Martins
|
|
Message is in Reply To:
 | | Re: Object Orientation & DAT files & CLIPPING/WINDING
|
| Rui Martins wrote in message ... (...) I concur that WINDING is strictly local. It may be a struggle of words, but I wouldn't call INVERT *local* as it affects the behaviour all tris/quads in *subfiles* And I don't see why clipping should be local. (...) (25 years ago, 19-Oct-99, to lugnet.cad.dev)
|
13 Messages in This Thread:
  
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
