Subject:
|
Re: Object Orientation & DAT files & CLIPPING/WINDING
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Tue, 19 Oct 1999 15:07:23 GMT
|
Viewed:
|
604 times
|
| |
|
|
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.
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. 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.
> > Each DAT-file has to establish its own WINDING.
>
> It can have its own winding, INTERNALLY, but to rest of the world its as
> if it has CCW WINDING all over it.
> remember you can't see inside.
Right, you can't see inside it. And the world doesn't care if it has
"CCW WINDING"! Only the orientation counts.
> On Mon, 18 Oct 1999, Steve Bliss wrote:
> > My goal with WINDING UNKNOWN is to have a statement which can temporarily
> > disable clipping[3], without overwriting the existing clipping state.
> > This is because the clipping state is passed in from super-files, so the
> > current file should avoid making hard-assignment of the clip-state.
> >
> > An alternative to WINDING UNKNOWN would be to define the operation of 0
> > CLIPPING ON|OFF such that disabling clipping in a super-file overrides
> > local CLIPPING ON statements.
>
> NO, the clipping state is not passed from file to file. It's LOCAL.
I believe WINDING UNKNOWN has its justification for temporarily disabling
clipping. And clipping state must be passed on! So disabling clipping in
a super-file overrides local CLIPPING ON statements.
Disabling clipping in a super-file should effectively turn off clipping for
the whole sub-tree.
/Lars
|
|
Message has 1 Reply:
 | | Re: Object Orientation & DAT files & CLIPPING/WINDING
|
| (...) Great! (...) 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 (...) (25 years ago, 20-Oct-99, to lugnet.cad.dev)
|
Message is in Reply To:
| | Re: Object Orientation & DAT files & CLIPPING/WINDING
|
| FIRST OF ALL my sugestion is that the CLIPPING, WINDING, INVERT are strictly local where they are used. CLIPPING is strictly local WINDING is strictly local INVERT is strictly local INVERT only means see referenced file as inverted. if INVERT is (...) (25 years ago, 18-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
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
