• Advertisement

Archived

This topic is now archived and is closed to further replies.

OpenGL OpenGL window stays in taskbar problem

This topic is 5603 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

I use some part of Nehe OpenGL code for my apps. I have just one smll problem. Sometimes (not allways) when I quit the app via the ESC key the program quits ok, but the window title stays on the taskbar. When i click on it, it dissapears. Its onlya a small problem but it gets frustrating when I have 20+ small boxes on the task bar. This only happens with fullscreen. I use Win98se. It also happens with the NeHe tutorials. Does anybody know how to fix this. Hmm maybe somebody can give me a link to some other openGL basecode that does not do this?

Share this post


Link to post
Share on other sites
Advertisement
I'm not sure if it has to do with ending the program while the screen resolution is being restored.

Maybe a small delay before the program actually ends is enough for the program to get rid of the taskbar icon cleanly?

[edited by - Waverider on October 16, 2002 11:02:35 AM]

Share this post


Link to post
Share on other sites
It doesnt happen with the resolution changing, I have the desktop and my programm exactly the same 1024x768x32. Hmm but thats a good idea Ill try to do something with that. Any other Ideas.

Does anybody know of some other OpenGL basecode????

Share this post


Link to post
Share on other sites
SDL apps using fullscreen OpenGL do the same, as does QuakeII, on my system anyway (Win98). It never happened with the my own code. I''m pretty sure it has to do with when the window is destroyed. I''ve not looked at any sources to verify it yet since it really doesn''t bother me (just click the thing each time you close the app), but when and if I find a fix for it I will post it here.

Share this post


Link to post
Share on other sites
I think Indentified the problem. It probably has the 10 lines of code when fullscreen is set up and the 1 line when the original settings are restored. Maybe there should be a delay after the resolution restore, before releasing the DC and RC. Gotta check it out.

Aldacron, could you send me the code or give me a link to the code that does not do this, so I can possibly track down what makes the difference?

Btw. I found out that all of the OpenGL downloads that I have do have this little problem.

My EMAIL: petrw@email.cz

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
quote:
I found out that all of the OpenGL downloads that I have do have this little problem


If ALL your opengl downloads do this, including professional games, then perhaps it is a driver issue. Have you updated drivers recently? Using an older video card?

Share this post


Link to post
Share on other sites
EDIT: Grrr, stoopid me double posted, sorry.



[edited by - yakuza on October 17, 2002 10:07:10 AM]

[edited by - yakuza on October 17, 2002 10:07:33 AM]

Share this post


Link to post
Share on other sites
The professional apps do not do this. Hmm but my graphic card is getting also old GF 4 MX 440 64MB. I think im gonna have to get a new one and put this in my 486. I have MSI drivers 2 month old.

Btw this also happens on my other PC, It also happend to someone else on this forum.

But i dont think this is a driver issue, Its about windows code!

Share this post


Link to post
Share on other sites
I have found the cause !!!

And I have fixed IT I am the KIIINNGGGG !!!

Problems dissapear when u remove this line from CreateGLWindow() in the NeHe code:

// dwExStyle = WS_EX_APPWINDOW

Its under the fullscreen section.

Share this post


Link to post
Share on other sites
quote:
Original post by Psycho-Coder
Hmm but my graphic card is getting also old GF 4 MX 440 64MB. I think im gonna have to get a new one and put this in my 486.


i sincerely hope that was a joke

-eldee
;another space monkey;
[ Forced Evolution Studios ]


::evolve::

''In C we had to code our own bugs. In C++ we can inherit them.''

Share this post


Link to post
Share on other sites
But it causes this warning:

warning C4700: local variable ''dwExStyle'' used without having been initialized
Linking...

How is it possible to pass a non init var to a func and it still works better than ever: I dont know but I hepe somebody in the forum will bring up an explanation.

All of this fuss about a little window stayng in the taskbar )))))

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
i had that problem also, i fixed it by minimizing the window before exiting the program.

Share this post


Link to post
Share on other sites
GeForce 4 is kinda old???? Granted, the MX version is nowhere near as good as the Ti, but still it is damn near the top of gaming cards atm...



God was my co-pilot but we crashed in the mountains and I had to eat him...
Landsknecht

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
PLEASE set dwExStyle to 0:

dwExStyle = 0;

Instead of commenting out the line, replace the WS_EX_OVERLAPPEDWINDOW with a zero. You''ve just been lucky that it hasn''t been anything important in dwExStyle when it''s not initialized. Dangerous stuff

Share this post


Link to post
Share on other sites
Hmm i was wondering about that think too, and it does cause some minor problems, but when u set it to zero, guess what it does the same as on the WS_EX_OVERLAPPEDWINDOW setting, maybe thi window is a little different but when its fullscreen u dont see it.

1 mere Q: how do yoi minimize the window?

Share this post


Link to post
Share on other sites
By adding this code before the release of DC and RC will fix the problem:


  
ANIMATIONINFO info;
info.cbSize = sizeof(info);
SystemParametersInfo(SPI_GETANIMATION,sizeof(info),&info,0);
int animationWasOn = info.iMinAnimate;

if(animationWasOn) // if window anim on disable it

{
info.iMinAnimate = false;
SystemParametersInfo(SPI_SETANIMATION, sizeof(info), &info, 0);
}

ShowWindow(hWnd, SW_MINIMIZE); // cool this prevents a bug


if(animationWasOn) // enable it back again

{
info.iMinAnimate = true;
SystemParametersInfo(SPI_SETANIMATION, sizeof(info), &info,0);
}


It minimizes the window, disabling and enabling window animation if necesarry (if on)!

Share this post


Link to post
Share on other sites

  • Advertisement
  • Advertisement
  • Popular Tags

  • Advertisement
  • Popular Now

  • Similar Content

    • By LifeArtist
      Good Evening,
      I want to make a 2D game which involves displaying some debug information. Especially for collision, enemy sights and so on ...
      First of I was thinking about all those shapes which I need will need for debugging purposes: circles, rectangles, lines, polygons.
      I am really stucked right now because of the fundamental question:
      Where do I store my vertices positions for each line (object)? Currently I am not using a model matrix because I am using orthographic projection and set the final position within the VBO. That means that if I add a new line I would have to expand the "points" array and re-upload (recall glBufferData) it every time. The other method would be to use a model matrix and a fixed vbo for a line but it would be also messy to exactly create a line from (0,0) to (100,20) calculating the rotation and scale to make it fit.
      If I proceed with option 1 "updating the array each frame" I was thinking of having 4 draw calls every frame for the lines vao, polygons vao and so on. 
      In addition to that I am planning to use some sort of ECS based architecture. So the other question would be:
      Should I treat those debug objects as entities/components?
      For me it would make sense to treat them as entities but that's creates a new issue with the previous array approach because it would have for example a transform and render component. A special render component for debug objects (no texture etc) ... For me the transform component is also just a matrix but how would I then define a line?
      Treating them as components would'nt be a good idea in my eyes because then I would always need an entity. Well entity is just an id !? So maybe its a component?
      Regards,
      LifeArtist
    • By QQemka
      Hello. I am coding a small thingy in my spare time. All i want to achieve is to load a heightmap (as the lowest possible walking terrain), some static meshes (elements of the environment) and a dynamic character (meaning i can move, collide with heightmap/static meshes and hold a varying item in a hand ). Got a bunch of questions, or rather problems i can't find solution to myself. Nearly all are deal with graphics/gpu, not the coding part. My c++ is on high enough level.
      Let's go:
      Heightmap - i obviously want it to be textured, size is hardcoded to 256x256 squares. I can't have one huge texture stretched over entire terrain cause every pixel would be enormous. Thats why i decided to use 2 specified textures. First will be a tileset consisting of 16 square tiles (u v range from 0 to 0.25 for first tile and so on) and second a 256x256 buffer with 0-15 value representing index of the tile from tileset for every heigtmap square. Problem is, how do i blend the edges nicely and make some computationally cheap changes so its not obvious there are only 16 tiles? Is it possible to generate such terrain with some existing program?
      Collisions - i want to use bounding sphere and aabb. But should i store them for a model or entity instance? Meaning i have 20 same trees spawned using the same tree model, but every entity got its own transformation (position, scale etc). Storing collision component per instance grats faster access + is precalculated and transformed (takes additional memory, but who cares?), so i stick with this, right? What should i do if object is dynamically rotated? The aabb is no longer aligned and calculating per vertex min/max everytime object rotates/scales is pretty expensive, right?
      Drawing aabb - problem similar to above (storing aabb data per instance or model). This time in my opinion per model is enough since every instance also does not have own vertex buffer but uses the shared one (so 20 trees share reference to one tree model). So rendering aabb is about taking the model's aabb, transforming with instance matrix and voila. What about aabb vertex buffer (this is more of a cosmetic question, just curious, bumped onto it in time of writing this). Is it better to make it as 8 points and index buffer (12 lines), or only 2 vertices with min/max x/y/z and having the shaders dynamically generate 6 other vertices and draw the box? Or maybe there should be just ONE 1x1x1 cube box template moved/scaled per entity?
      What if one model got a diffuse texture and a normal map, and other has only diffuse? Should i pass some bool flag to shader with that info, or just assume that my game supports only diffuse maps without fancy stuff?
      There were several more but i forgot/solved them at time of writing
      Thanks in advance
    • By RenanRR
      Hi All,
      I'm reading the tutorials from learnOpengl site (nice site) and I'm having a question on the camera (https://learnopengl.com/Getting-started/Camera).
      I always saw the camera being manipulated with the lookat, but in tutorial I saw the camera being changed through the MVP arrays, which do not seem to be camera, but rather the scene that changes:
      Vertex Shader:
      #version 330 core layout (location = 0) in vec3 aPos; layout (location = 1) in vec2 aTexCoord; out vec2 TexCoord; uniform mat4 model; uniform mat4 view; uniform mat4 projection; void main() { gl_Position = projection * view * model * vec4(aPos, 1.0f); TexCoord = vec2(aTexCoord.x, aTexCoord.y); } then, the matrix manipulated:
      ..... glm::mat4 projection = glm::perspective(glm::radians(fov), (float)SCR_WIDTH / (float)SCR_HEIGHT, 0.1f, 100.0f); ourShader.setMat4("projection", projection); .... glm::mat4 view = glm::lookAt(cameraPos, cameraPos + cameraFront, cameraUp); ourShader.setMat4("view", view); .... model = glm::rotate(model, glm::radians(angle), glm::vec3(1.0f, 0.3f, 0.5f)); ourShader.setMat4("model", model);  
      So, some doubts:
      - Why use it like that?
      - Is it okay to manipulate the camera that way?
      -in this way, are not the vertex's positions that changes instead of the camera?
      - I need to pass MVP to all shaders of object in my scenes ?
       
      What it seems, is that the camera stands still and the scenery that changes...
      it's right?
       
       
      Thank you
       
    • By dpadam450
      Sampling a floating point texture where the alpha channel holds 4-bytes of packed data into the float. I don't know how to cast the raw memory to treat it as an integer so I can perform bit-shifting operations.

      int rgbValue = int(textureSample.w);//4 bytes of data packed as color
      // algorithm might not be correct and endianness might need switching.
      vec3 extractedData = vec3(  rgbValue & 0xFF000000,  (rgbValue << 8) & 0xFF000000, (rgbValue << 16) & 0xFF000000);
      extractedData /= 255.0f;
    • By Devashish Khandelwal
      While writing a simple renderer using OpenGL, I faced an issue with the glGetUniformLocation function. For some reason, the location is coming to be -1.
      Anyone has any idea .. what should I do?
  • Advertisement