My idea to fix issue #631 is to have a list for vaos (like how textures are handled) that is updated each frame and a new vao is created when a valid one doesn't exist. Therefore, this fixes the problem by creating a vao for each context that doesn't already have one. However, I can see the potential problem that a vao handle that is valid in one context for the correct nvg vao could also be correct in a different context for a different vao. However, to solve this problem would require a major overhaul to the nanovg api. We'd need a way for users to separate shared context state from per-context state and such. Let me know your thoughts and I am open to any ideas.
My idea to fix issue #631 is to have a list for vaos (like how textures are handled) that is updated each frame and a new vao is created when a valid one doesn't exist. Therefore, this fixes the problem by creating a vao for each context that doesn't already have one. However, I can see the potential problem that a vao handle that is valid in one context for the correct nvg vao could also be correct in a different context for a different vao. However, to solve this problem would require a major overhaul to the nanovg api. We'd need a way for users to separate shared context state from per-context state and such. Let me know your thoughts and I am open to any ideas.