Help with an object oriented window class

Started by
16 comments, last by elendil67 21 years, 4 months ago
About the sig, just use the Width= and Height= values of your image.
Here: <img src="http://www.gras-wien.gruene.at/pics/napster.gif" border=0 width=100 height=135> =

Edit: oops, i broke it :s




[edited by - Evil Bill on December 1, 2002 7:51:11 PM]
Member of the Unban Mindwipe Society (UMWS)
Advertisement
Forget the sig... do you guys no whats wrong??? Yes, I am using system icons. Thanks so far for your help
When you go homeTell them of us, and say:For your tomorrow,We gave our today.
text is better than pictures
quote:Original post by elendil67
do you guys no whats wrong?

Of course not, you''ve given us nothing with which to diagnose your problem. What is the exact error ("a runtime error" is not exact)? What are the values of the various parameters when the error occurs?

Ask a good question if you want good answers.
WndProc problem?
"after many years of singularity, i'm still searching on the event horizon"
quote:Original post by Evil Bill
Does it work if you set the WndProc to DefWindowProc? (I know you said its not, but thats all i can see could cause the problem)...


Edit: "Forget the sig..." I wish we could



[edited by - Evil Bill on December 3, 2002 10:27:55 AM]
Member of the Unban Mindwipe Society (UMWS)
listen to Evil Bill and Oluseyi and everyone else.

* post the error message. you should be using a call to FormatMessage with GetLastError to get a meaningful error message rather than your generic and useless error message. see the MSDN docs on FormatMessage for an example.
* post the code of the calling function.
* post the code to your static WndProc. why are you type casting your WndProc to a WNDPROC?
* post the code to your class non-static WndProc.

are you using a singleton class instance or not? if not, post the code that attempts to get your class instance pointer to your static WndProc because your not using the "standard" method for doing so.

there''s a lot that goes on behind the scenes when creating a window. and not all of it happens in the CreateWindow/Ex function. there are window messages that are queued up and handled, particularly WM_NCCREATE and WM_CREATE, which also could be part of the problem.
Well I can't answer the question either, but the signature drama playing out here is irresistable.

Might I recommend:

Reduced Communism

I'm no Photoshop god, but still.

[edited by - Reaptide on December 3, 2002 1:06:33 PM]

This topic is closed to new replies.

Advertisement