Sign in to follow this  
NucleA

OpenGL Opengl Basic

Recommended Posts

Hey guys, am trying to set opengl to a window using Dev cpp

here is my code:


#include <windows.h>
#include <gl/gl.h>

LRESULT CALLBACK WindowHandler(HWND hwnd, UINT msg, WPARAM wParam, LPARAM lParam){
switch(msg){
case WM_CLOSE:
DestroyWindow(hwnd);
break;
case WM_DESTROY:
PostQuitMessage(0);
break;
default: return DefWindowProc(hwnd, msg, wParam, lParam);
}
}

int WINAPI WinMain(HINSTANCE hThisInstance, HINSTANCE hPrevInstance, LPSTR lpCmdLine, int nCmdShow){
WNDCLASSEX wincl;

wincl.cbSize = sizeof(WNDCLASSEX);
wincl.style = CS_OWNDC;
wincl.hIcon = LoadIcon(NULL, IDI_APPLICATION);
wincl.hCursor = LoadCursor(NULL, IDC_ARROW);
wincl.hbrBackground = (HBRUSH) GetStockObject(BLACK_BRUSH);
wincl.cbClsExtra = 0;
wincl.cbWndExtra = 0;
wincl.hInstance = hThisInstance;
wincl.lpszMenuName = NULL;
wincl.lpszClassName = "MyWindowClass";
wincl.lpfnWndProc = WindowHandler;

RegisterClassEx(&wincl);

HWND hwnd;

hwnd = CreateWindow(
"MyWindowClass",
"OpenGl",
WS_POPUPWINDOW | WS_VISIBLE,
70, 70,
700,
510,
NULL,
NULL,
hThisInstance,
NULL
);

HDC hDc;
HGLRC hRc;
PIXELFORMATDESCRIPTOR pfd;
int iFormat;

hDc = GetDC(hwnd);

ZeroMemory(&pfd, sizeof(pfd));
pfd.nSize = sizeof(pfd);
pfd.nVersion = 1;
pfd.dwFlags = PFD_DRAW_TO_WINDOW | PFD_DOUBLEBUFFER | PFD_SUPPORT_OPENGL;
pfd.iPixelType = PFD_TYPE_RGBA;
pfd.cColorBits = 24;
pfd.cDepthBits = 16;
pfd.iLayerType = PFD_MAIN_PLANE;

iFormat = ChoosePixelFormat(hDc, &pfd);
SetPixelFormat(hDc, iFormat, &pfd);

/*Create & enable rendering context*/
hRc = wglCreateContext(hDc);
wglMakeCurrent(hDc, hRc);

BOOL bQuit = false;
MSG msg;

while(!bQuit){
if(PeekMessage(&msg, NULL, 0, 0, PM_REMOVE)){
if(msg.message == WM_QUIT){
bQuit = true;
}
else{
TranslateMessage(&msg);
DispatchMessage(&msg);
}

}
else{
/*Drawing scene goes here*/
glClearColor(0.0f, 0.0f, 0.0f, 0.0f);
glClear(GL_COLOR_BUFFER_BIT);
glBegin(GL_POINTS);
glVertex2f(0.2f, 0.2f);
glEnd();
SwapBuffers(hDc);


}

}

wglMakeCurrent(NULL, NULL);
wglDeleteContext(hRc);
ReleaseDC(hwnd, hDc);

DestroyWindow(hwnd);

}



But when i compile and run the code, nothing happens, no window appear but the program itself is running on the system.

Where did i make an error in the code?? Please helpp

Thanks and have a nice day! :p

Share this post


Link to post
Share on other sites
While I'm sorry I don't know the answer to your question, I'll give you two pieces of advice, which you're free to ignore if you want to:

1) Don't use Dev C++, I believe it is quite old and I hear nothing but bad things about it. (has cryptic error messages, poor intellisense, random bugs, etc) MSVC++ 2010 Express is a better option IMO, and you'll get much more support for it if you have problems (almost everyone uses it).

2) Unless you really want to dig into the nuts and bolts of windows API, let a library take care of the windowing code and you can focus on the OpenGL, it's much simpler. I'll recommend SFML, with which you can replace your entire windowing code with:


main(){
sf::Window App(sf::VideoMode(800,600,32));
App.SetActive();

bool quit = false;
while(!quit) {
glClearColor(0.0f, 0.0f, 0.0f, 0.0f);
glClear(GL_COLOR_BUFFER_BIT);
glBegin(GL_POINTS);
glVertex2f(0.2f, 0.2f);
glEnd();
App.Display();
}
return;
}



Plus it has lots of other useful utilities you may find yourself needing along the way (support for image loading, audio, input handling, etc). It's a nice piece of software.

Share this post


Link to post
Share on other sites
The reason am using opengl is that in the future i will need to develop multi threaded applications(like autocad) where there are several windows and view points. Also opengl is cross platform, thats my choice..:p

Share this post


Link to post
Share on other sites
I didn't say you should not use OpenGL, you can use OpenGL with SFML to replace the platform specific windowing code.

SFML handles multiple windows and is also cross platform, but that's the last I'll say about that :)

Share this post


Link to post
Share on other sites
Hello,

Be sure to clear WNDCLASSEX if you are not going to be setting all of the data members in it (you are messing hIconSm). Invalid values can cause RegisterClassEx to fail. Also, because you are using the *Ex routines, I would recommend using CreateWindowEx over CreateWindow.

Share this post


Link to post
Share on other sites
Quote:
Original post by NucleA
Thanks very much. But i want to learn it the low level way since i have learned assembly and am a student at a university!


SFML/SDL mainly lets you avoid the platform specific details (Win32/X11/etc) , if you intend to target multiple platforms its quite a good idea to use it, (The alternative is to rewrite a reasonably large chunk of code for each platform you wish to support), assembly has absolutely nothing to do with the Win32 API btw and most good universities tend to focus on the concepts rather than platform specific details.

In the code you posted 5 of the code lines are cross platform, the rest are windows specific and would have to be rewritten for Linux and Mac.

Share this post


Link to post
Share on other sites
"2) Unless you really want to dig into the nuts and bolts of windows API, let a library take care of the windowing code and you can focus on the OpenGL, it's much simpler."

Or you can take what karwosts said to the extreme and use Basic4gl:
http://basic4gl.net/

Although it runs off a VM, its pretty sweet when it comes to just trying something out/experimenting without getting into the specifics of c++... Thats just about as close to "Opengl Basic" as I can think of.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Announcements

  • Forum Statistics

    • Total Topics
      628402
    • Total Posts
      2982469
  • Similar Content

    • By test opty
      Hi all,
       
      I'm starting OpenGL using a tut on the Web. But at this point I would like to know the primitives needed for creating a window using OpenGL. So on Windows and using MS VS 2017, what is the simplest code required to render a window with the title of "First Rectangle", please?
       
       
    • By DejayHextrix
      Hi, New here. 
      I need some help. My fiance and I like to play this mobile game online that goes by real time. Her and I are always working but when we have free time we like to play this game. We don't always got time throughout the day to Queue Buildings, troops, Upgrades....etc.... 
      I was told to look into DLL Injection and OpenGL/DirectX Hooking. Is this true? Is this what I need to learn? 
      How do I read the Android files, or modify the files, or get the in-game tags/variables for the game I want? 
      Any assistance on this would be most appreciated. I been everywhere and seems no one knows or is to lazy to help me out. It would be nice to have assistance for once. I don't know what I need to learn. 
      So links of topics I need to learn within the comment section would be SOOOOO.....Helpful. Anything to just get me started. 
      Thanks, 
      Dejay Hextrix 
    • By mellinoe
      Hi all,
      First time poster here, although I've been reading posts here for quite a while. This place has been invaluable for learning graphics programming -- thanks for a great resource!
      Right now, I'm working on a graphics abstraction layer for .NET which supports D3D11, Vulkan, and OpenGL at the moment. I have implemented most of my planned features already, and things are working well. Some remaining features that I am planning are Compute Shaders, and some flavor of read-write shader resources. At the moment, my shaders can just get simple read-only access to a uniform (or constant) buffer, a texture, or a sampler. Unfortunately, I'm having a tough time grasping the distinctions between all of the different kinds of read-write resources that are available. In D3D alone, there seem to be 5 or 6 different kinds of resources with similar but different characteristics. On top of that, I get the impression that some of them are more or less "obsoleted" by the newer kinds, and don't have much of a place in modern code. There seem to be a few pivots:
      The data source/destination (buffer or texture) Read-write or read-only Structured or unstructured (?) Ordered vs unordered (?) These are just my observations based on a lot of MSDN and OpenGL doc reading. For my library, I'm not interested in exposing every possibility to the user -- just trying to find a good "middle-ground" that can be represented cleanly across API's which is good enough for common scenarios.
      Can anyone give a sort of "overview" of the different options, and perhaps compare/contrast the concepts between Direct3D, OpenGL, and Vulkan? I'd also be very interested in hearing how other folks have abstracted these concepts in their libraries.
    • By aejt
      I recently started getting into graphics programming (2nd try, first try was many years ago) and I'm working on a 3d rendering engine which I hope to be able to make a 3D game with sooner or later. I have plenty of C++ experience, but not a lot when it comes to graphics, and while it's definitely going much better this time, I'm having trouble figuring out how assets are usually handled by engines.
      I'm not having trouble with handling the GPU resources, but more so with how the resources should be defined and used in the system (materials, models, etc).
      This is my plan now, I've implemented most of it except for the XML parts and factories and those are the ones I'm not sure of at all:
      I have these classes:
      For GPU resources:
      Geometry: holds and manages everything needed to render a geometry: VAO, VBO, EBO. Texture: holds and manages a texture which is loaded into the GPU. Shader: holds and manages a shader which is loaded into the GPU. For assets relying on GPU resources:
      Material: holds a shader resource, multiple texture resources, as well as uniform settings. Mesh: holds a geometry and a material. Model: holds multiple meshes, possibly in a tree structure to more easily support skinning later on? For handling GPU resources:
      ResourceCache<T>: T can be any resource loaded into the GPU. It owns these resources and only hands out handles to them on request (currently string identifiers are used when requesting handles, but all resources are stored in a vector and each handle only contains resource's index in that vector) Resource<T>: The handles given out from ResourceCache. The handles are reference counted and to get the underlying resource you simply deference like with pointers (*handle).  
      And my plan is to define everything into these XML documents to abstract away files:
      Resources.xml for ref-counted GPU resources (geometry, shaders, textures) Resources are assigned names/ids and resource files, and possibly some attributes (what vertex attributes does this geometry have? what vertex attributes does this shader expect? what uniforms does this shader use? and so on) Are reference counted using ResourceCache<T> Assets.xml for assets using the GPU resources (materials, meshes, models) Assets are not reference counted, but they hold handles to ref-counted resources. References the resources defined in Resources.xml by names/ids. The XMLs are loaded into some structure in memory which is then used for loading the resources/assets using factory classes:
      Factory classes for resources:
      For example, a texture factory could contain the texture definitions from the XML containing data about textures in the game, as well as a cache containing all loaded textures. This means it has mappings from each name/id to a file and when asked to load a texture with a name/id, it can look up its path and use a "BinaryLoader" to either load the file and create the resource directly, or asynchronously load the file's data into a queue which then can be read from later to create the resources synchronously in the GL context. These factories only return handles.
      Factory classes for assets:
      Much like for resources, these classes contain the definitions for the assets they can load. For example, with the definition the MaterialFactory will know which shader, textures and possibly uniform a certain material has, and with the help of TextureFactory and ShaderFactory, it can retrieve handles to the resources it needs (Shader + Textures), setup itself from XML data (uniform values), and return a created instance of requested material. These factories return actual instances, not handles (but the instances contain handles).
       
       
      Is this a good or commonly used approach? Is this going to bite me in the ass later on? Are there other more preferable approaches? Is this outside of the scope of a 3d renderer and should be on the engine side? I'd love to receive and kind of advice or suggestions!
      Thanks!
    • By nedondev
      I 'm learning how to create game by using opengl with c/c++ coding, so here is my fist game. In video description also have game contain in Dropbox. May be I will make it better in future.
      Thanks.
  • Popular Now