最近正在使用Qt的QOpenGLWidget来学习opengl，前期进展十分顺利，直到我遇到了framebuffer这一章节
framebuffer的大致使用方式如下：
// 第一处理阶段(Pass)
glBindFramebuffer(GL_FRAMEBUFFER, framebuffer);
glClearColor(0.1f, 0.1f, 0.1f, 1.0f);
glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT); // 我们现在不使用模板缓冲
glEnable(GL_DEPTH_TEST);
DrawScene();
// 第二处理阶段
glBindFramebuffer(GL_FRAMEBUFFER, 0); // 返回默认
glClearColor(1.0f, 1.0f, 1.0f, 1.0f);
glClear(GL_COLOR_BUFFER_BIT);
screenShader.use();
glBindVertexArray(quadVAO);
glDisable(GL_DEPTH_TEST);
glBindTexture(GL_TEXTURE_2D, textureColorbuffer);
glDrawArrays(GL_TRIANGLES, 0, 6);
程序很简单，但是当我运行之后，发现屏幕全白，即对应glClearColor(1.0f, 1.0f, 1.0f, 1.0f)，为了验证我这个猜想，我进行了以下步骤：
- 屏幕全白是不是真的对应到glClearColor这个函数。修改清屏颜色，发现运行后的屏幕颜色确实和其一一对应。
- 有没有真的把三角形绘制上去。把
glDrawArrays(GL_TRIANGLES, 0, 6)删除后，发现并不影响屏幕全白这一结果，因此问题应该出现在glClearColor(1.0f, 1.0f, 1.0f, 1.0f)之前。 - 删除第二处理阶段的这几行函数，发现屏幕变黑，对应
glClearColor(0.1f, 0.1f, 0.1f, 1.0f)，再把glBindFramebuffer(GL_FRAMEBUFFER, framebuffer)注释掉，让物体不绘制在帧缓冲内，而是直接绘制到当前屏幕上，嘿，没问题！
那……问题应该是出现在帧缓冲绑定上？我们是否真的绑定到了帧缓冲区呢？
*搜索一波：
OpenGL Qt : problem using framebuffers for bloom effect
OpenGL does not render to screen by calling glBindFramebuffer(GL_FRAMEBUFFER,0)
Easiest way for offscreen rendering with QOpenGLWidget
果真是缓冲区绑定的问题！当我们执行glBindFramebuffer(GL_FRAMEBUFFER, 0)时，我们并没有返回到Qt默认的帧缓冲，应该先调用QOpenGLContext::defaultFramebufferObject()这个函数得到Qt默认的帧缓冲，
Call this to get the default framebuffer object for the current surface.
On some platforms (for instance, iOS) the default framebuffer object depends on the surface being rendered to, and might be different from 0. Thus, instead of calling glBindFramebuffer(0), you should call glBindFramebuffer(ctx->defaultFramebufferObject()) if you want your application to work across different Qt platforms.
If you use the glBindFramebuffer() in QOpenGLFunctions you do not have to worry about this, as it automatically binds the current context‘s defaultFramebufferObject() when 0 is passed.
Note: Widgets that render via framebuffer objects, like QOpenGLWidget and QQuickWidget, will override the value returned from this function when painting is active, because at that time the correct "default" framebuffer is the widget‘s associated backing framebuffer, not the platform-specific one belonging to the top-level window‘s surface. This ensures the expected behavior for this function and other classes relying on it (for example, QOpenGLFramebufferObject::bindDefault() or QOpenGLFramebufferObject::release()).
See also QOpenGLFramebufferObject.
即需要这么改：glBindFramebuffer(GL_FRAMEBUFFER, defaultFramebufferObject());
修改完之后，终于把这个问题解决啦！
我使用QOpenGLWidget学习opengl的代码放在github上了，欢迎访问~ miyanyan/learnopengl-qt