Sign in to follow this  
sakares

OpenGL Opengl placement of statements

Recommended Posts

HELP!!!! I am used to ALLEGRO and i dont know where to place statements like l=l+1 and so on. here is my code. the line in question is marked by <----HERE-- #include <windows.h> #include <gl\gl.h> #include <gl\glut.h> #include <gl\glu.h> /* GLU extention library */ void init(void); void display(void); void keyboard(unsigned char, int, int); void resize(int, int); void drawcube(int, int, int); int is_depth; /* depth testing flag */ int l; int main (int argc, char **argv) { glutInit(&argc, argv); glutInitDisplayMode(GLUT_DOUBLE | GLUT_RGB); glutInitWindowSize(600, 600); glutInitWindowPosition(40, 40); glutCreateWindow("The Cube World"); init(); glutDisplayFunc(display); glutKeyboardFunc(keyboard); l=-3; /* this time we're going to keep the aspect ratio constant by trapping the window resizes */ glutReshapeFunc(resize); glutMainLoop(); return 0; } void init(void) { glClearColor(0.0, 0.0, 0.0, 0.0); glEnable(GL_DEPTH_TEST); is_depth = 1; glMatrixMode(GL_MODELVIEW); } void display(void) { if (is_depth) glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT); else glClear(GL_COLOR_BUFFER_BIT); /* draw the floor */ glBegin(GL_QUADS); glColor3f(0.2f, 0.2f, 0.2f); glVertex3f(-100.0, 0.0, -100.0); glColor3f(0.4f, 0.4f, 0.4f); glVertex3f(-100.0, 0.0, 100.0); glColor3f(0.6f, 0.6f, 0.6f); glVertex3f(100.0, 0.0, 100.0); glColor3f(0.8f, 0.8f, 0.8f); glVertex3f(100.0, 0.0, -100.0); glEnd(); /* draw 12 cubes with different colors */ //drawcube(75, 57, 2); //drawcube(-65, -12, 3); //drawcube(50, -50, 1); //drawcube(-56, 17, 2); //drawcube(67, 12, 3); //drawcube(-87, 32, 1); //drawcube(-26, 75, 2); //drawcube(57, 82, 3); drawcube(l, 12, 1); //drawcube(46, 35, 2); //drawcube(37, -2, 3); glutSwapBuffers(); } void keyboard(unsigned char key, int x, int y) {l=l+1; /////////////////////////////<-----------------HERE---- /* This time the controls are: "a": move left "d": move right "w": move forward "s": move back "t": toggle depth-testing */ switch (key) { case 'a': case 'A': glTranslatef(5.0, 0.0, 0.0); break; case 'd': case 'D': glTranslatef(-5.0, 0.0, 0.0); break; case 'w': case 'W': glTranslatef(0.0, 0.0, 5.0); break; case 's': case 'S': glTranslatef(0.0, 0.0, -5.0); break; case 'u': case 'U': glRotatef(3.0, 0.0, 1.0, 0.0); /* rotate up */ break; case 'y': case 'Y': glRotatef(-3.0, 0.0, 1.0, 0.0); /* rotate up */ break; case 't': case 'T': if (is_depth) { is_depth = 0; glDisable(GL_DEPTH_TEST); } else { is_depth = 1; glEnable(GL_DEPTH_TEST); } } display(); } void resize(int width, int height) { if (height == 0) height = 1; glMatrixMode(GL_PROJECTION); glLoadIdentity(); /* note we divide our width by our height to get the aspect ratio */ gluPerspective(45.0, width / height, 1.0, 400.0); /* set initial position */ glTranslatef(0.0, -5.0, -150.0); glMatrixMode(GL_MODELVIEW); } void drawcube(int x_offset, int z_offset, int color) { /* this function draws a cube centerd at (x_offset, z_offset) x and z _big are the back and rightmost points, x and z _small are the front and leftmost points */ float x_big = (float)x_offset + 5; float z_big = (float)z_offset + 5; float x_small = (float)x_offset - 5; float z_small = (float)z_offset - 5; switch(color) { case 1: glColor3f(1.0,0.0,0.0); break; case 2: glColor3f(0.0,1.0,0.0); break; case 3: glColor3f(0.0,0.0,1.0); break; } glBegin(GL_QUADS); glVertex3f(x_small,10.0,z_big); /* front */ glVertex3f(x_small,0.0,z_big); glVertex3f(x_big,0.0,z_big); glVertex3f(x_big,10.0,z_big); glVertex3f(x_big,10.0,z_small); /* back */ glVertex3f(x_big,0.0,z_small); glVertex3f(x_small,0.0,z_small); glVertex3f(x_small,10.0,z_small); glVertex3f(x_big,10.0,z_big); /* right */ glVertex3f(x_big,0.0,z_big); glVertex3f(x_big,0.0,z_small); glVertex3f(x_big,10.0,z_small); glVertex3f(x_small,10.0,z_small); /* left */ glVertex3f(x_small,0.0,z_small); glVertex3f(x_small,0.0,z_big); glVertex3f(x_small,10.0,z_big); glVertex3f(x_small,10.0,z_big); /* top */ glVertex3f(x_big,10.0,z_big); glVertex3f(x_big,10.0,z_small); glVertex3f(x_small,10.0,z_small); glVertex3f(x_small,0.0,z_small); /* bottom */ glVertex3f(x_big,0.0,z_small); glVertex3f(x_big,0.0,z_big); glVertex3f(x_small,0.0,z_big); glEnd(); } it works but i have to press a button to make it work. I want it to just move across the screen automatically I tried moving it outside of the keyboard loop, but then I get an error like its not supposed to be there. It has to work if placed in the right position in the code, right????? but i dont know where opengl wants me to put it. please help someone.

Share this post


Link to post
Share on other sites
you mean like just before the key loop. something like

for(l<100)
{l=l+1;}

if that is what you mean then i have already tried this and i get an error message...."expected unqualified id"
so I don't know what to do or where to turn. I mean Opengl should be able to handle a for loop right???

Share this post


Link to post
Share on other sites
Quote:
Original post by sakares
you mean like just before the key loop. something like

for(l<100)
{l=l+1;}

if that is what you mean then i have already tried this and i get an error message...."expected unqualified id"
so I don't know what to do or where to turn. I mean Opengl should be able to handle a for loop right???


First of all, OpenGL doesn't 'handle' for loops. OpenGL is simply a set of functions that let you talk to your graphics hardware. Second, you may want to look into the proper syntax for a for loop. Third, if you do get that for loop properly set up, the object isn't going to move smoothly (its going to jump, and disappear before you see anything). This is because your program will stop until the for loop is completed, and effectively just increment l by 100.

I'm not even sure why you would need a for loop in this instance. Probably the quickest and easiest (although, not necessarily the 'best') thing to do is simply most the l=l+1 statement to the top of your display function. As I recall, GLUT allows you to set up an idle function callback. Creating one of those, as CodeMunkie suggested, and putting the code there, is probably a better way to go.

And, although the code may work, there are certainly a number of things that should be done. Among other things, you really should have a call to glLoadIdentity at the start of your display function. However, this means you'll need to make some changes to your keyboard handling. The transformations will have to be stored in some variables, and the transformations moved into the display function.

Share this post


Link to post
Share on other sites
funny I was taken literally about opengl handling a for loop...anyway, i think this is great advice and thank you for it, although I odnt know what you mean by proper syntax, my syntax for for loops has been fine in all my other c++ application, but I am no expert. anyway I moved my l=l+1 to the top of the display function an it works but i need to press a key still for my cube to move across the screen. I htink the secret may lay in this callback function, I have not been able to find an example of this would you be able to or would anyone for this matter be able to provide me an example of this and what its purpose is???

Share this post


Link to post
Share on other sites
Look up glutTimerFunc. It is very similar to the way you set up your glutDisplayFunc and glutKeyboardFunc, but it also takes in a timeout parameter that determines how often the function is called.

Share this post


Link to post
Share on other sites
Man you guys are being so nice to me helping me out I really appreciate it. i looked up the gluttimer thing and got this.

void glutTimerFunc(unsigned int msecs, void (*func)(int value), value);

how to use it this is another question. ummmm... is it a really complicated thing or would someone be able to put it in the right place for me. I just need to see things in the right place and then I can figure them out from there. so basically when I figure this out and figure out how to display variables such as l on the screen i will be set.

and which things need to be filled in??? msec i assume that I put the time that i want to elapse between loops and *func what is this??? int value also????
anyway any more help would be appreciated.

Share this post


Link to post
Share on other sites
There's dozens of ways to display text on the screen. None are very easy. And I get the impression that you need to slow down. Your original question shows that you need to spend more time learning C++, rather than hopping into OpenGL. Getting a good foundation is very important, and is difficult to do if you get ahead of yourself. Write some Allegro programs totally from scratch. Don't copy a single line from any program (be it yours or a tutorial). This will help you solve problems like your first one on your own. I understand that you're excited and want to do as much as possible, but you will be able to do far more if you take it easy and make sure to get a strong understanding, rather than the bare minimum understanding, of base information.

Well, that's my take on it. Use it as you want.

Oh, and Allegro can handle OpenGL for you. This would let you learn just OpenGL instead of GLut along with OpenGL.

Share this post


Link to post
Share on other sites
actually i am pretty comfortable with c++ and have written several programs in allegro 2d games and such, its just the opengl syntax is quite different to me.but to anyone that can help me out with this it would be greatly appreciated.

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
      628391
    • Total Posts
      2982419
  • 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