@dsa-t Do you have an example of how would it be used that I could, perhaps, incorporate in a sample and use for testing it myself? I.e. what would be the function that you could load like this without checking for the current backend first in any case?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.![]()
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.![]()
For example, it should make it easier to initialize GLAD (like https://gitlab.kitware.com/vtk/vtk/-/blob/04661f4bcdf84195a75e4e91a542b9e6e8bd8e37/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx#L788) without having to load the functions separately.
I don't have a wx sample yet.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.![]()
According to SDL wiki this function can't be static in wxGLContext under Windows as the available extensions are context-specific. Is it ok for your planned use of it or should we make it static and let people decide themselves if they want to follow the documentation and make a context current before calling it or not?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.![]()
Non-static is fine for me.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.![]()
Now I wonder if this should be in wxGLContext or in wxGLCanvas. I'd say that the former makes more sense, but we already have a clearly related IsExtensionSupported() in the latter (albeit as static), so maybe we should put this there too for consistency? But then it would need to take wxGLContext as argument, which is probably not what people expect?
Sorry for all the questions, but it's genuinely difficult to decide on the API when I still don't really know how it's going to be used.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.![]()
I think it's fine to implement in wxGLContext then.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.![]()
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.![]()