Printable View
hehehe, good code,
just one thing...
I accidently hit end instead of the little x button on the form, now my highlite color is green, and its for the whole system.... hehe, I would appreciate it if someone would tell me the normal color... you know that ugly blue...... :)
thanks.
ok Never mind, I set it to normal using the display properties.....
When dealing with API's, it's a good idea to end the program using the standard method rather than clicking the end button.
Especially when subclassing...I accidentally killed it once and VB got itself utterly confused and I lost about 5 minutes work. Considering I type like a maniac that's a lot of work.
I may hit the end button when using damn near every API I know how, but when I am subclassing I do not forget and hit the end button :rolleyes:
That's 1 extra thing to distribute though; better keep it simple. Remember, App's are suppose to suit the users, not us.
your right, but that sucks...
we are the ones that are slaving over this radiation generating machine, and getting very little or no pay, and yet the end user gets all the ease of use........
Grrrrrrr.....
that makes me mad, and a lot of times the program works well, but the user just screws it up... I know.. I have done it a few times :o
yep, but you can use the control anyway, it's much more safer to develope with that. Then before distribution you just replace the ocx with the standard module :)
it would be better to use a class module.
because then you can just Declare the class module as the name of the control you removed.
you dont have to have it in a module right??
thats only the procedure that replaces the normal one, right?
The only important thing is to make sure that when the program hits a breakpoint or an error, that the WindowProc has been set back to the default, or it is not in the current thread. *sorry*
Dennis, the prob is that you can't have Addresof pointing at a procedure in a class, what i did (i did a subclassing control) was that i made an ocx with a standard module that had this procedure, and the usercontrol automatically started subclassing the form you placed it on pointing the addressof the sub in the module. Then it unsubclasses in terminate usercontrol event, which occurs if you end your app with the end button. A classmodule could be used as well but you would have to pass the arguments manually