# OpenGL OpenGL VS2005 MFC View Offset

## Recommended Posts

I have a Visual C++-OpenGL project that has a "shifted view" in Vista but not in XP. I have discovered that if I implement OpenGL in a Win32 Project the view is correct, and if I use a MFC Application that the view is shifted vertically down by about 20 pixels. I am using Visual Studio 2005, the program I noticed the problem on was originally compiled in VS 6.0. Hopefully the screen shots show up below. OpenGL seems to be working, I get a red square with an (altered) gray background in both cases. In the MFC case, there is a ~20 pixel band where the view is not drawn (it shows up white). The white band is of constant height no matter what the window size. The vertical height of the square is 1 unit, so the distance from the origin (lower-left corner of the square) to the top of the gray area seems to be correct. But, the distance in the -y direction is shorter than 1. I thought it might be a problem with glViewport(0,0,cx,cy) in my OnSize function at first. The values of cx and cy passed to OnSize are the same as those from a call to GetClientRect. I think I have a pretty standard starting implementation, I set glViewport and glOrtho in OnSize, initialize the pixelformat in OnCreate, and do my drawing in OnDraw. Anyone have any idea why MFC would be special in Vista, or what to turn off in MFC to try to eliminate the problem? Visual C++ Win32 Project version: (correctly sizes the view) Visual C++ MFC Application version: (note the white band at the top of the client area)

##### Share on other sites
What happens if you try removing the status bar at the bottom, or the toolbar at the top? I'm guessing that one of them is causing that gap for some reason.

##### Share on other sites
Removing the status and/or toolbar doesn't affect the band. The viewport does get bigger with the extra space from the removed items but the view is still off. Do you mean to remove them from the code?

Here is a shot with the status bar and toolbar removed in a smaller window. It's almost as if the view is wrapped around from the bottom.

## Create an account

Register a new account

• ## Partner Spotlight

• ### Forum Statistics

• Total Topics
627665
• Total Posts
2978523
• ### Similar Content

• Both functions are available since 3.0, and I'm currently using glMapBuffer(), which works fine.
But, I was wondering if anyone has experienced advantage in using glMapBufferRange(), which allows to specify the range of the mapped buffer. Could this be only a safety measure or does it improve performance?
Note: I'm not asking about glBufferSubData()/glBufferData. Those two are irrelevant in this case.
• By xhcao
Before using void glBindImageTexture(    GLuint unit, GLuint texture, GLint level, GLboolean layered, GLint layer, GLenum access, GLenum format), does need to make sure that texture is completeness.
• By cebugdev
hi guys,
are there any books, link online or any other resources that discusses on how to build special effects such as magic, lightning, etc. in OpenGL? i mean, yeah most of them are using particles but im looking for resources specifically on how to manipulate the particles to look like an effect that can be use for games,. i did fire particle before, and I want to learn how to do the other 'magic' as well.
Like are there one book or link(cant find in google) that atleast featured how to make different particle effects in OpenGL (or DirectX)? If there is no one stop shop for it, maybe ill just look for some tips on how to make a particle engine that is flexible enough to enable me to design different effects/magic
let me know if you guys have recommendations.
• By dud3
How do we rotate the camera around x axis 360 degrees, without having the strange effect as in my video below?
Mine behaves exactly the same way spherical coordinates would, I'm using euler angles.
Tried googling, but couldn't find a proper answer, guessing I don't know what exactly to google for, googled 'rotate 360 around x axis', got no proper answers.

References:
Code: https://pastebin.com/Hcshj3FQ
The video shows the difference between blender and my rotation:

• By Defend
I've had a Google around for this but haven't yet found some solid advice. There is a lot of "it depends", but I'm not sure on what.
My question is what's a good rule of thumb to follow when it comes to creating/using VBOs & VAOs? As in, when should I use multiple or when should I not? My understanding so far is that if I need a new VBO, then I need a new VAO. So when it comes to rendering multiple objects I can either:
* make lots of VAO/VBO pairs and flip through them to render different objects, or
* make one big VBO and jump around its memory to render different objects.
I also understand that if I need to render objects with different vertex attributes, then a new VAO is necessary in this case.
If that "it depends" really is quite variable, what's best for a beginner with OpenGL, assuming that better approaches can be learnt later with better understanding?

• 10
• 10
• 12
• 22
• 13