Sign in to follow this  
RorqualPilot

OpenGL GameGUI

Recommended Posts

I have made myself a decent foundation for making my 2D Game. Now it comes to some basic UI. I have tried several: Tusk 2 Too basic, could not integrate due to some unresolved externals and does not provide any foundations for adding new widgets. CEGui Overkill for my purpose, hard to integrate to my mind, too much exceptions, hard to understand. guichan Forums only filled with pharmacy-spam, seems to be inactive. Any others out there for OpenGL? Or would it better to build myself some GUI? I need not much stuff: - Basic Inventory, Items are dragged from the Game into the UI. - Some Buttons - Messageboxes I have managed to make a message-box, but placing caption, Ok/Cancel-Buttons to it etc seems to be quite much effort with drawing all the stuff into the box. Here is some example how I draw the box which contains the message without caption:
    GLfloat color[4];
    GLint matrixMode;
    glGetIntegerv(GL_MATRIX_MODE, &matrixMode);

    glMatrixMode(GL_MODELVIEW);
    glPushMatrix();
    glLoadIdentity();
    glTranslatef(this->getPosX(), this->getPosY(), m_zorder);

    glGetFloatv(GL_CURRENT_COLOR, color);
    glColor3f(.7f, 0.0f, 0.0f);

    glEnableClientState(GL_VERTEX_ARRAY);  
    glVertexPointer(3, GL_FLOAT, 0, &m_box_vertices[0]);
    glDrawArrays(GL_QUADS, 0, 4);
    glDisableClientState(GL_VERTEX_ARRAY);

    glColor3fv(color);

    m_font->renderObject(m_text.c_str(), this->getPosX() + 25, this->getPosY() + 40 );

    glPopMatrix();
    glMatrixMode(matrixMode);
Wrong approach or well done? Thanks for your input. regards

Share this post


Link to post
Share on other sites
Well all this is just rendering and actually is just one small part of GUI.

First you should write yourself a GUIRenderer which will save you a lot time replicating code and fixing bugs in every file. That renderer should be able to draw Rectangles, Images and Text to the screen when you just pass in the cordinates and the SizeOfRectangle/Image/Text. When you have that Renderer you can start building your ui.

First of all start with a empty Widget. It will be the base class for all GUI elements.
here some example code.

http://sudi.pastebin.com/f79c1132e

just a quick thought...its missing a lot but should give you a idea

Share this post


Link to post
Share on other sites
A game GUI that simple is quicker to implement for your own, that learning to use a library.

other thread

Start with rendering: you have to see what you are doing, make the basic struct, that has the info for drawing, add other elements to it when needed.

Make the widgets function first, I mean toggles toggling, radios radioing, sliders sliding, and the "engine" of the GUI.

After you have done these, comes the hard part: how to associate game variables to the GUI? You can hard code it, it's just enough for a game GUI, but not enough for an editor GUI of course.

I hope that helps.

Share this post


Link to post
Share on other sites
If your rendering an inventory screen then its most likely going to be more unique than any GUI System out there has to offer. What I'm doing for my game GUI is I'm building my own. It's not that hard either. It just takes a lot of typing, but you could get it implemented in a day or so, depending on how advanced / unique it is. If you don't want to or don't have the time to build a GUI system from scratch I found QT widgets in the past. It supposedly good but I've never used it so I'm so sure.

I found this page which shows tons of different GUI Toolkit s that you can use. Just find the right one... http://www.atai.org/guitool/

However, my experience with GUI systems are that if you want your game to be completely unique you need to make your own GUI library. You can get really creative with it too. So my recommendation is to just make a GUI library from scratch. It shouldn't take too long either. Here's some class Ideas

Window
Panel (with a texture)
Textbox
Button
ImageButton
Slider
ScrollBar (if text is too long and doesn't fit on the window)
ToolTip
Image
etc.
Just Get Creative!

Share this post


Link to post
Share on other sites
I agree with the others who have suggested that coding your own GUI is generally the best solution -- it also tends to be very fun and rewarding, because when dealing with all the complexity of a 3d engine, the GUI is comparatively easy and the results come quickly.

This probably goes without saying, but you want to abstract the GUI renderer. Past that, it's all up to you -- it depends on what you need in terms of features. Like others have mentioned, it's good to have a basic "widget" or "element" class from which to derive all other things, also pretty typical are the concepts of containers and controls, etc.

I don't think anyone's yet talked about containers and controls, so I'll go a bit more into it. Basically, containers are objects that hold any number of controls, and can be parents or children of other containers. A control is a simple object that reports a single element of input back to the container holding it -- this would be something like a checkbox, slider, etc. A container, if it has a parent container, reports back the sum of the inputs of all its controls back to its parent container when it ceases to exist.

This allows for a system where one window may have a number of buttons and sliders and input boxes, and when this window is finished, it can report back the sum of all these individual options back to its parent window, which in turn may have other individual boxes and buttons AND additional children containers that will report groups of control states.

You may not need anything so complicated for your GUI, but this is the genereal theory of "windowing."

Share this post


Link to post
Share on other sites
I suggest to go the general way:
Let every widgets/windows/tabs have their own drawing/clicking/moving/etc functions, more precisely pointers to functions, so you can expand you GUI, without the need to rewrite it. You can use generalized functions of course:
the same functions to draw pushbuttons/toggles/radio buttons/whatever, and same functions for these, but you can have unique functions too.

I hope that made sense...

Yup, windowing isn't so hard either, as cmc5788 mentioned, you have to use some kind of parent-child relations between window-window, window-widget, even widget-widget (if you want to enable/disable a group of widgets, depending on a toggle, for example).

I use parents to define these relations, since I don't have too much stuff, so I can loop through everything to get parent IDs, of course you can have child vectors too.

So some conclusion: it's not hard, but probably hard work: I suggest extensive/intensive use of paper and pen.

Share this post


Link to post
Share on other sites
Thanks for all your suggestions. I will try to make one myself. :)
Tried Agar too, that looks pretty nice and I could integrate it first, but ended with very much memory-leaks.
I have already done some "menu-widgets" and now I will try to get all this into some hirachy where I can implement some automatism for rendering.
Thanks again.
o/

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
      628328
    • Total Posts
      2982099
  • Similar Content

    • 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.
    • By Abecederia
      So I've recently started learning some GLSL and now I'm toying with a POM shader. I'm trying to optimize it and notice that it starts having issues at high texture sizes, especially with self-shadowing.
      Now I know POM is expensive either way, but would pulling the heightmap out of the normalmap alpha channel and in it's own 8bit texture make doing all those dozens of texture fetches more cheap? Or is everything in the cache aligned to 32bit anyway? I haven't implemented texture compression yet, I think that would help? But regardless, should there be a performance boost from decoupling the heightmap? I could also keep it in a lower resolution than the normalmap if that would improve performance.
      Any help is much appreciated, please keep in mind I'm somewhat of a newbie. Thanks!
    • By test opty
      Hi,
      I'm trying to learn OpenGL through a website and have proceeded until this page of it. The output is a simple triangle. The problem is the complexity.
      I have read that page several times and tried to analyse the code but I haven't understood the code properly and completely yet. This is the code:
       
      #include <glad/glad.h> #include <GLFW/glfw3.h> #include <C:\Users\Abbasi\Desktop\std_lib_facilities_4.h> using namespace std; //****************************************************************************** void framebuffer_size_callback(GLFWwindow* window, int width, int height); void processInput(GLFWwindow *window); // settings const unsigned int SCR_WIDTH = 800; const unsigned int SCR_HEIGHT = 600; const char *vertexShaderSource = "#version 330 core\n" "layout (location = 0) in vec3 aPos;\n" "void main()\n" "{\n" " gl_Position = vec4(aPos.x, aPos.y, aPos.z, 1.0);\n" "}\0"; const char *fragmentShaderSource = "#version 330 core\n" "out vec4 FragColor;\n" "void main()\n" "{\n" " FragColor = vec4(1.0f, 0.5f, 0.2f, 1.0f);\n" "}\n\0"; //******************************* int main() { // glfw: initialize and configure // ------------------------------ glfwInit(); glfwWindowHint(GLFW_CONTEXT_VERSION_MAJOR, 3); glfwWindowHint(GLFW_CONTEXT_VERSION_MINOR, 3); glfwWindowHint(GLFW_OPENGL_PROFILE, GLFW_OPENGL_CORE_PROFILE); // glfw window creation GLFWwindow* window = glfwCreateWindow(SCR_WIDTH, SCR_HEIGHT, "My First Triangle", nullptr, nullptr); if (window == nullptr) { cout << "Failed to create GLFW window" << endl; glfwTerminate(); return -1; } glfwMakeContextCurrent(window); glfwSetFramebufferSizeCallback(window, framebuffer_size_callback); // glad: load all OpenGL function pointers if (!gladLoadGLLoader((GLADloadproc)glfwGetProcAddress)) { cout << "Failed to initialize GLAD" << endl; return -1; } // build and compile our shader program // vertex shader int vertexShader = glCreateShader(GL_VERTEX_SHADER); glShaderSource(vertexShader, 1, &vertexShaderSource, nullptr); glCompileShader(vertexShader); // check for shader compile errors int success; char infoLog[512]; glGetShaderiv(vertexShader, GL_COMPILE_STATUS, &success); if (!success) { glGetShaderInfoLog(vertexShader, 512, nullptr, infoLog); cout << "ERROR::SHADER::VERTEX::COMPILATION_FAILED\n" << infoLog << endl; } // fragment shader int fragmentShader = glCreateShader(GL_FRAGMENT_SHADER); glShaderSource(fragmentShader, 1, &fragmentShaderSource, nullptr); glCompileShader(fragmentShader); // check for shader compile errors glGetShaderiv(fragmentShader, GL_COMPILE_STATUS, &success); if (!success) { glGetShaderInfoLog(fragmentShader, 512, nullptr, infoLog); cout << "ERROR::SHADER::FRAGMENT::COMPILATION_FAILED\n" << infoLog << endl; } // link shaders int shaderProgram = glCreateProgram(); glAttachShader(shaderProgram, vertexShader); glAttachShader(shaderProgram, fragmentShader); glLinkProgram(shaderProgram); // check for linking errors glGetProgramiv(shaderProgram, GL_LINK_STATUS, &success); if (!success) { glGetProgramInfoLog(shaderProgram, 512, nullptr, infoLog); cout << "ERROR::SHADER::PROGRAM::LINKING_FAILED\n" << infoLog << endl; } glDeleteShader(vertexShader); glDeleteShader(fragmentShader); // set up vertex data (and buffer(s)) and configure vertex attributes float vertices[] = { -0.5f, -0.5f, 0.0f, // left 0.5f, -0.5f, 0.0f, // right 0.0f, 0.5f, 0.0f // top }; unsigned int VBO, VAO; glGenVertexArrays(1, &VAO); glGenBuffers(1, &VBO); // bind the Vertex Array Object first, then bind and set vertex buffer(s), //and then configure vertex attributes(s). glBindVertexArray(VAO); glBindBuffer(GL_ARRAY_BUFFER, VBO); glBufferData(GL_ARRAY_BUFFER, sizeof(vertices), vertices, GL_STATIC_DRAW); glVertexAttribPointer(0, 3, GL_FLOAT, GL_FALSE, 3 * sizeof(float), (void*)0); glEnableVertexAttribArray(0); // note that this is allowed, the call to glVertexAttribPointer registered VBO // as the vertex attribute's bound vertex buffer object so afterwards we can safely unbind glBindBuffer(GL_ARRAY_BUFFER, 0); // You can unbind the VAO afterwards so other VAO calls won't accidentally // modify this VAO, but this rarely happens. Modifying other // VAOs requires a call to glBindVertexArray anyways so we generally don't unbind // VAOs (nor VBOs) when it's not directly necessary. glBindVertexArray(0); // uncomment this call to draw in wireframe polygons. //glPolygonMode(GL_FRONT_AND_BACK, GL_LINE); // render loop while (!glfwWindowShouldClose(window)) { // input // ----- processInput(window); // render // ------ glClearColor(0.2f, 0.3f, 0.3f, 1.0f); glClear(GL_COLOR_BUFFER_BIT); // draw our first triangle glUseProgram(shaderProgram); glBindVertexArray(VAO); // seeing as we only have a single VAO there's no need to // bind it every time, but we'll do so to keep things a bit more organized glDrawArrays(GL_TRIANGLES, 0, 3); // glBindVertexArray(0); // no need to unbind it every time // glfw: swap buffers and poll IO events (keys pressed/released, mouse moved etc.) glfwSwapBuffers(window); glfwPollEvents(); } // optional: de-allocate all resources once they've outlived their purpose: glDeleteVertexArrays(1, &VAO); glDeleteBuffers(1, &VBO); // glfw: terminate, clearing all previously allocated GLFW resources. glfwTerminate(); return 0; } //************************************************** // process all input: query GLFW whether relevant keys are pressed/released // this frame and react accordingly void processInput(GLFWwindow *window) { if (glfwGetKey(window, GLFW_KEY_ESCAPE) == GLFW_PRESS) glfwSetWindowShouldClose(window, true); } //******************************************************************** // glfw: whenever the window size changed (by OS or user resize) this callback function executes void framebuffer_size_callback(GLFWwindow* window, int width, int height) { // make sure the viewport matches the new window dimensions; note that width and // height will be significantly larger than specified on retina displays. glViewport(0, 0, width, height); } As you see, about 200 lines of complicated code only for a simple triangle. 
      I don't know what parts are necessary for that output. And also, what the correct order of instructions for such an output or programs is, generally. That start point is too complex for a beginner of OpenGL like me and I don't know how to make the issue solved. What are your ideas please? What is the way to figure both the code and the whole program out correctly please?
      I wish I'd read a reference that would teach me OpenGL through a step-by-step method. 
  • Popular Now