subclassing does screw up your APP if you dont unsubclass it. but when you end it wont unsubclass, and when you debug it wont handle the messages. so you should check the option to ask you if you want to save every time.
Remember, if someone's post was not helpful, you can always rate their post negatively .
Originally posted by BuggyProgrammer subclassing does screw up your APP if you dont unsubclass it. but when you end it wont unsubclass, and when you debug it wont handle the messages. so you should check the option to ask you if you want to save every time.
You're right. What is this "save" option you speak of?
Originally posted by BuggyProgrammer or in a picture:
Uhm, I'm really stupid. How bout you come all the way over here to East Timor and show me how to do it? I don't know how to use a mouse, let alone menus.
khalik
I didn't understand completely what you just said. Can you elaborate?
I have a 4KB "working" (pun unintended) example of the crashing example. I'll post it.
sorry mendhak... not sure about subclassing.. but it all the time happen when i work with treeview (when loading huge data)
and working with sheridans (3rd party controls) i was also looking for a solutions... i thought it may be a memory problem....
this will happen when i end the program from design mode.
Reply With Quote
.
