Hello,

What is the use case for accessing the renderbuffers? It is probably left out 
since access to them was not seen important. (given that it is the texture that 
matters for the 2D UI development scenarios Qt has traditionally been targeting)

The getters should probably be added nonetheless. In the meantime you can use 
glGetFramebufferAttachmentParameteriv.

As for the "missing" support for MRT and such, keep in mind that this does not 
exist in GLES2, which is the baseline for Qt, and that Qt is not a 3D engine 
wrapping every single bit of OpenGL. Improvements are welcome of course.

Cheers,
Laszlo


________________________________________
From: development-bounces+laszlo.agocs=digia....@qt-project.org 
[development-bounces+laszlo.agocs=digia....@qt-project.org] on behalf of Sean 
Harmer [sean.har...@kdab.com]
Sent: Friday, May 16, 2014 10:02 AM
To: development@qt-project.org
Subject: Re: [Development] Access to depth and stencil buffers in       
QOpenGLFramebufferObject

On Friday 16 May 2014 00:31:01 Taylor Braun-Jones wrote:
> Hi all,
>
> I'm working on a VTK-in-FBO solution for integrating VTK into Qt Quick 2
> and trying to understand why QOpenGLFramebufferObject provides methods:
>
> GLuint QOpenGLFramebufferObject::handle() const
> GLuint QOpenGLFramebufferObject::texture() const
>
> But not similar methods like:
>
> GLuint QOpenGLFramebufferObject::depthBuffer() const
> GLuint QOpenGLFramebufferObject::stencilBuffer() const
>
> Was this this an oversight or intentional? If intentional, what's the
> rationale?

I think it is an oversight. There is more missing from this class. It's on my
list to look into but I've not been able to find the time just yet. I.e. being
able to specify multiple color attachments for use with deferred rendering
etc.

Cheers,

Sean
--
Dr Sean Harmer | sean.har...@kdab.com | Managing Director UK
Klarälvdalens Datakonsult AB, a KDAB Group company
Tel. Sweden (HQ) +46-563-540090, USA +1-866-777-KDAB(5322)
KDAB - Qt Experts - Platform-independent software solutions
_______________________________________________
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
_______________________________________________
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Reply via email to