 | | 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)
|
| |
| | 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)
|
| |
| | Re: Object Orientation & DAT files & CLIPPING/WINDING
|
|
(...) <snipped stuff about INVERT> I think we're disagreeing about the meaning of 'strictly local'. As you describe the operation of INVERT, it is *not* local. The state of inversion is passed down the file-reference tree. This is not a local (...) (25 years ago, 19-Oct-99, to lugnet.cad.dev)
|
| |
| | Re: Object Orientation & DAT files & CLIPPING/WINDING
|
|
(...) Yes it is. (...) The reference of the current GLOBAL state is passed down the file-reference tree, YES. (...) Correct. (...) NOT the FILE, but the RENDERING PROGRAM ! (...) Agreed. (...) By default would be CCW. (...) YES and NO. The internal (...) (25 years ago, 20-Oct-99, to lugnet.cad.dev)
|
| |
| | 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)
|
