Timeline for Understanding VAO and VBO
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 21, 2024 at 21:04 | comment | added | Christoph Rackwitz | "states" (plural) implies that you're talking about an assortment of values ("red/green/blue/yellow, awake/asleep, wearing socks or not, ..." those are "values"), whereas "the state" is the current value of a scalar/struct/array/whatever (think "the smurf is blue, awake, wearing socks") | |
| Oct 23, 2020 at 21:29 | comment | added | user8469759 | What do you do you mean with "They're not states, they're state", probably something stupid I know... | |
| Oct 23, 2020 at 18:14 | comment | added | Nicol Bolas | @user8469759: Binding the object to the context means that state that references those locations will get their data from the object. And they're not "states"; they're state. As I analogized, they're like member variables for objects. | |
| Oct 23, 2020 at 17:31 | comment | added | user8469759 | First of all why is the "binding" relevant (namely why is having the object state the same as the context important?) and second if I bind the object to have the same state as the context I guess this is important but why would I want to modify the state only within the object? I guess this actually comes down to what the meaning of these states are. | |
| Oct 23, 2020 at 17:30 | comment | added | user8469759 | I'm reading through your second link and slowly it's becoming a bit clearer. However the bit "* ... allows OpenGL operations that access certain state to find that state within the bound object. So if you call a function that modifies certain state that is from a bound object, that function will modify the state within the object."* isn't totally clear. | |
| Oct 22, 2020 at 18:05 | history | answered | Nicol Bolas | CC BY-SA 4.0 |