MantisBT - VTK
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0010196VTK(No Category)public2010-01-28 21:212016-08-12 09:55
ReporterFrançois Bertel 
Assigned ToKitware Robot 
PrioritynormalSeverityfeatureReproducibilityN/A
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Project
Type
Summary0010196: Improve fine-tuning of OpenGL/Mesa RenderWindow
DescriptionRight now, there is no way for a user to force the creation of the default OpenGL framebuffer [1] of an OpenGL renderer window with a particular set of criteria (number of bits in the depth buffer, in the color buffer, ...)

It could be done by adding some preference profile object. For example, this profile could have a minimum number of bits for a depth buffer, a minimum number of bits for the colorbuffer. In parallel, each item of the preference list should have a boolean value saying if the item is required or if it is up to the system to pick any.

For the illustration purpose of the discussion, let's call vtkFrameBufferProfile
a class composed of two pointers. The first one to a vtkFrameBufferProfileValues object
and the second one to a vtkFrameBufferProfileMask object.

class vtkFrameBufferProfile
{
public:
vtkFrameBufferProfileValues *GetValues();
vtkFrameBufferProfileMask *GetMask();
}

For example, with:

vtkFrameBufferProfile *p=vtkFrameBufferProfile::New();
p->GetValues()->SetDepthBufferBits(24);
p->GetMask()->SetDepthBufferBits(true);
p->GetMask()->SetColorBufferBits(false);

the user is asking for a minimum of 24 bits in the depth buffer but does not care about how many bits are used for the colorbuffer.
The system will create a framebuffer with at least 24bits in its depth buffer and with any kind of colorbuffer, regardless of the colorbufferbits preference value.
 
To build the list of preferences, we can use references [2],[3] and [4].


[1] "default" framebuffer, as defined in the OpenGL 3.2 Compatibility Profile Specification, section 2.1, page 6 as the window system-provided framebuffer http://www.opengl.org/registry/doc/glspec32.compatibility.20091207.pdf [^]
[2] GLX 1.4 http://www.opengl.org/documentation/specs/glx/glx1.4.pdf [^]
[3] WGL pixel format: http://www.opengl.org/registry/specs/ARB/wgl_pixel_format.txt [^]
[4] NSOpenGLPixelFormat: Mac OS X http://developer.apple.com/mac/library/documentation/Cocoa/Reference/ApplicationKit/Classes/NSOpenGLPixelFormat_Class/Reference/Reference.html [^]
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-01-28 21:21François BertelNew Issue
2010-01-28 21:22François BertelStatusbacklog => tabled
2010-01-28 21:22François BertelAssigned To => François Bertel
2010-09-07 13:43François BertelAssigned ToFrançois Bertel =>
2011-06-16 13:11Zack GalbreathCategory => (No Category)
2016-08-12 09:55Kitware RobotNote Added: 0037138
2016-08-12 09:55Kitware RobotStatusexpired => closed
2016-08-12 09:55Kitware RobotResolutionopen => moved
2016-08-12 09:55Kitware RobotAssigned To => Kitware Robot

Notes
(0037138)
Kitware Robot   
2016-08-12 09:55   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current VTK Issues page linked in the banner at the top of this page.