Has anyone ever had this happen to them or knows a simple reason why this might be happening : I''m making a 3D thing using directx (ddraw, d3d, d3dx, dinput), and for some reason, i have no idea why, it decided that sometimes after it finishes and the program quits it''ll leave the button of the app in the taskbar. When I go to click on it, it magically disappears. It only happens sometimes, less often than not. Am I missing something trivial in my code, like forgetting to free memory, or would it be something more complex? - IO Fission Tearing 'em apart for no particular reason...

The same thing happens to me when I play other DX games too (proffesional and non-proffesional), but I suppose it''s Windows'' fault I wouldn''t bother fixing it if I were you.

/. Muzzafarath
Mad House Software

Make sure you are using this to shutdown the program

PostQuitMessage(0);

And inside of your WinProc function do a case for quit like

    case WM_QUIT:      DeallocateAllMemoryThatHasBeenAllocated();      break;    

the PostQuitMessage(0); function will run this case in your WinProc then will destroy the window and application


"Now go away or I shall taunt you a second time"
- Monty Python and the Holy Grail

I think it''s windows'' bug - quake 2 also someimes leaves a few buttons without titles on the taskbar which disappear when I click on them on my computer.

Visit our homepage: www.rarebyte.de.st

GA

Almost all games that use glide or ogl have this problem.
I think its an attempt by microsoft to stop people from using ogl or glide.

OneEyeLessThanNone

But then it could be the fact that windows is still a very buggy piece of software.

I do believe that Microsoft had posted somewhere that it is mearly a cosmetic error with windows and they feel no urgent rush to fix it.

40

www.databyss.com
www.omlettesoft.com

"Don''t meddle in the affairs of wizards, for they are subtle and quick to anger."

I''ve noticed that it usually happens to me when I goto the case WM_CLOSE to quit rather than WM_DESTROY. Try moving your calls under WM_CLOSE TO WM_DESTROY and see if it works.

Not sure about you folks, but when that little button stays there on the taskbar I know that I have done something wrong. I am using windows 98 (not sure what version).

In my old game i would quit by doing PostQuitMessage(0);
Unfortunately, this was bypassing my calls to DD_Shutdown() and other such important memory deallocating functions and so I got a little icon on the taskbar.

In my latest game, I have done everything properly (read: slightly better) and now I quit by deallocating DirectX surfaces etc before calling PostQuitMessage(0);

Just wanted to know that not *everything* can be blamed on Microsoft - we as programmers still have some responsibilities ourselves!


wise_guy

I agree with wise_Guy, I had the same thing in the taskbar before...then I discovered that I wasn''t "delete[]"ing my look up tables. Now it''s fixed.



When life hands you lemons, throw them at God's head.

Thanx for the input. I''m leaning toward it being Microsoft''s problem, cause try as I might I can''t find anyplace where it might not be deallocating memory properly. Iread somewhere that DDraw''s gotta be shutdown before the window is, which is just before you get a WM_DESTROY (or so I''ve gathered), so I can''t do much about swapping which message kills ddraw.
I recently moved a whole bunch of routines into seperate files, could that have anything to do with it (I doubt it, but just in case ) ?


PS to wise_guy: G''day Aussie!


- IO Fission

Tearing 'em apart for no particular reason...