 | | Re: Two questions on primitives —Philippe Hurbain
|
| | | (...) The INVERTNEXT directive takes care of this problem. Quoted from BFC proposal: "INVERTNEXT This option inverts a subfile. It may only be used immediately before a subfile command line, and it only influences the immediately following subfile (...) (23 years ago, 28-Mar-02, to lugnet.cad.dat.parts, lugnet.cad.dat.parts.primitives)
|
| | | |
| | | | | Re: Two questions on primitives —Orion Pobursky
|
| | | | (...) I'm concerned that if we release those primitives that can be used as both inside and outside surfaces as BFC complient, we'll have to go back to all the other pieces that use them to insert the INVERTNEXT directive (where appropriate). (...) (23 years ago, 29-Mar-02, to lugnet.cad.dat.parts, lugnet.cad.dat.parts.primitives)
|
| | | | |
| | | | | | Re: Two questions on primitives —Tony Hafner
|
| | | | (...) Is this a real issue? Parts can't be truly BFC compliant until all of their subparts are BFC compliant. So yes, you'll have to insert those INVERTNEXT commands. But the part wasn't BFC compliant before, and this is just another part of (...) (23 years ago, 29-Mar-02, to lugnet.cad.dat.parts, lugnet.cad.dat.parts.primitives, lugnet.cad.dev)
|
| | | | |
| | | | | | Re: Two questions on primitives —Steve Bliss
|
| | | | (...) You've got it. When existing part files are made BFC-compliant, they have to be checked through completely. The main changes are fixing polygon wrapping and adding INVERTNEXT statements. Until a file is labeled BFC-compliant, renderers (...) (23 years ago, 30-Mar-02, to lugnet.cad.dat.parts, lugnet.cad.dat.parts.primitives, lugnet.cad.dev)
|
| | | | |
| | | | | | Re: Two questions on primitives —Orion Pobursky
|
| | | | | Thanks guys. You cleared up my only question with BFC -Orion (23 years ago, 30-Mar-02, to lugnet.cad.dat.parts, lugnet.cad.dat.parts.primitives, lugnet.cad.dev)
|
| | | | | |
| | | | | | | Re: Two questions on primitives —Steve Bliss
|
| | | | | | (...) One other thing,[1] the primitives which are most commonly used with the INVERTNEXT flag/statement are the *-*cyli.dat files. All of these files (the regular cylinder primitives) have BFC'ed versions posted on the Parts Tracker. -- Steve 1) (...) (23 years ago, 31-Mar-02, to lugnet.cad.dat.parts, lugnet.cad.dat.parts.primitives, lugnet.cad.dev)
|
| | | | | | |
| | | | | | What about BFC-ing studs? (was: Two questions on primitives) —Tony Hafner
|
| | | | (...) Okay... if this is the case, then what's the status on bringing the less-primitive primitives into BFC certification? Take studs for example. Studs strike me as a great candidate for getting BFC'd because of the potentially huge payoff. Of (...) (23 years ago, 2-Apr-02, to lugnet.cad.dat.parts, lugnet.cad.dat.parts.primitives, lugnet.cad.dev)
|
| | | | |
| | | | | | Re: What about BFC-ing studs? (was: Two questions on primitives) —Steve Bliss
|
| | | | (...) Sorry, I got distracted. I'll get back to BFC'ing and submitting those primitives. [snip] (...) You're working on an incorrect assumption here. Reflecting a subfile (ie, negating the multipliers for one dimension) will not invert the subfile. (...) (23 years ago, 3-Apr-02, to lugnet.cad.dat.parts, lugnet.cad.dat.parts.primitives, lugnet.cad.dev)
|
| | | | |
