Re: The memory could not be "read". Application Crash??
From: Michael Culley (mculley_at_NOSPAMoptushome.com.au)
Date: 10/06/04
- Next message: Rick Rothstein: "Re: Looking for an addin to force my projects to 800x600"
- Previous message: Michael Culley: "Re: Aaarrrggghhh -- that ugly flicker!"
- In reply to: [SolarAngel]: "Re: The memory could not be "read". Application Crash??"
- Next in thread: Ian: "Re: The memory could not be "read". Application Crash??"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 6 Oct 2004 13:57:24 +1000
"[SolarAngel]" <not-for-mail> wrote in message
news:u4TX$X1qEHA.3896@TK2MSFTNGP15.phx.gbl...
> !!!!!!!!
> Be sure to add in your subclassing test for WM_DESTROY
> and destroy there subclassing if somehow you haven't already!
> !!!!!!!!
This is not necessary. It is a good idea but it's not going to cause any
problems except maybe using up an element in an array in vb. As the window
has been destroyed your WndProc will never get a message again from that
window and will never try to call CallWndProc with an invalid value. Trust
me, I've actually tried to get VB to crash by not unsubclassing and
couldn't.
-- Michael Culley
- Next message: Rick Rothstein: "Re: Looking for an addin to force my projects to 800x600"
- Previous message: Michael Culley: "Re: Aaarrrggghhh -- that ugly flicker!"
- In reply to: [SolarAngel]: "Re: The memory could not be "read". Application Crash??"
- Next in thread: Ian: "Re: The memory could not be "read". Application Crash??"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
