[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Public WebGL] Specifying the behavior of bindXXX when passed a deleted resource
Actually I'm not sure what should happen here and AFAICT it's not clear from the ES spec.
The ES spec doesn't say what happens if you call useProgram on a program marked for deletion but not actually deleted but it is clear you can still use the object for things like GetProgramiv as that's how you query if it's marked for deletion.
If they decided to make other resources behave like shaders and programs (ie, you must call glGenXXX to create an id and glBindXXX stops creating resources and delete behaves the same), then there's all kinds of interesting questions
If you can useProgram a program marked for deletion but not deleted then you should be able to bindTexture a texture marked for deletion but not deleted.
Similarly you should be able to call getTexParameter on a texture marked for deletion just like you can call getProgramParameter on a program marked for deletion
Other queries and binds would also seem to work.
I don't think that would be a problem. In that case bindXXX and useProgram would only fail on objects actually deleted, not objects just marked for deletion. I know Chrome would have no problem with that as we already don't actually call glDeleteXXX on anything unless all its references are gone since there are driver bugs otherwise. I'm pretty sure Firefox does the same.
I've asked for some input from the OpenGL WG.