Request: guidance on vb nag screen

[DARKER]

the target actually loads the About form (frmAbout) which in turn loads the main form (frmMain) after you click OK on the About form. You then are in the app and can open the About form again through the standard Help|About menu.

You can try at the end of frmAbout Form_Load event jump to cmdOK Click event code. Result is that at the beginning NAG just blink and program run normally. frmAbout stay loaded in memory (Form_Load is not firing) so if you call it from About menu it should works.

[Wirestealth]

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

[Wirestealth]

Sorry as my last post had @DION and @DARKER mixed up.

@DARKER: Well I totally overthought this. I thought I would try your suggestion and see how bad the flicker was from frmAbout...well, and I should have thought of this from regular VB programming) since I jump to the OK button click event before I return from the load of frmAbout the form has yet to be made visible on screen and so the message queue gets the frmAbout.Hide added to it and apparently is processed before it is even made visible so that is all that was needed!

Thanks for the suggestion as I was totally making it more difficult than need be. I should have learned from the Tuts that you try the easiest approach first and work from there :P.