| 79 | | \ext The Material has two interfaces to return a State that represents |
|---|
| 80 | | it. OSG::Material::makeState() creates a new OSG::State and returns it. |
|---|
| 81 | | This is ok for rare use, but for every frame this is going to be too |
|---|
| 82 | | expensive. For these cases OSG::Material::rebuildState() and |
|---|
| 83 | | OSG::Material::getState() are used, which modify and return an |
|---|
| 84 | | internal copy of the State. |
|---|
| 85 | | |
|---|
| 86 | | The other method to implement is OSG::Material::isTransparent(), to |
|---|
| 87 | | identify transparent materials to be rendered after the opaque ones. |
|---|
| | 79 | \ext |
|---|
| | 80 | The Material has two interfaces to return a State that represents it. |
|---|
| | 81 | OSG::Material::makeState() creates a new OSG::State and returns it. This is |
|---|
| | 82 | ok for rare use, but for every frame this is going to be too expensive. For |
|---|
| | 83 | these cases OSG::Material::rebuildState() and OSG::Material::getState() are |
|---|
| | 84 | used, which modify and return an internal copy of the State. |
|---|
| | 85 | |
|---|
| | 86 | The other method to implement is OSG::Material::isTransparent(), to identify |
|---|
| | 87 | transparent materials to be rendered after the opaque ones. |
|---|