View Single Post
  #2  
Old 01-30-2010, 02:03
Wirestealth Wirestealth is offline
Friend
 
Join Date: Jan 2010
Posts: 6
Rept. Given: 0
Rept. Rcvd 0 Times in 0 Posts
Thanks Given: 0
Thanks Rcvd at 0 Times in 0 Posts
Wirestealth Reputation: 0
Thanks for suggesions but I'm a little anal...

Heya mates, thanks a bunch.

@DARKER: Sorry, I should have mentioned that I have been using Olly as well with no love (still new to it though so I'm sure I just need to learn how best to use it for VB-based apps). I have used Olly for regular C++ apps with success (those in the Lena151 tutorials anyway :P).

@dion: I'm a little anal mate, and the only reason I am going through this using a freeware target is for the learning. Thus, my anal retentiveness doesn't even want the momentary 'blink' that I understand would happen.

I may look into setting the form visibility property to false and then calling the _Click event at the end of the load routine. I would inline this functionality after the load was called (as I don't believe the window has actually been shown yet). In your opinion, do you see any 'gotchas' with either inlining a call to MSVB6VM.dll to set a forms visibility to false or dig deeper into to the actual CreateWindow call parameters and remove the window style WS_VISIBLE (or make a call to ShowWindow to hide it)? Assuming this approach is viable I would then add the _Click event call to the end of the load routine.

Thanks for your replies
Reply With Quote