I don't use Windows much at home anymore. When I did, I used AVG. Most of the time it was more than enough. One of the things I did like about it was I didn't find it to be a huge resource hog like some others. Lately, I stumbled upon Comodo AntiVirus. I don't know how good or bad it is, but I figured I'd throw another option out there for you to investigate.

Yeah, I'm going to chock it up to what my teachers told me in high school - "You (as in I) need to slow down." damn teachers! :laugh:

Like2Byte wrote: but I don't know where to start. Like2Byte wrote: Anyone help? Sure I always enjoy helping the Google impaired. Knock yourself out[^]

Didn't know the OPT was used for that! Thank you!! :P I was able to get it to work - after I deleted all my breakpoints. I'll now next what to do ahead of schedule. Cheers!! :-D

Ah, I see what we did. We were trying to invoke methods on the vars without being inside a form-method. (I'm not a VB.NET developer. Can you tell!?) :P Thank you very much for your help!!

See also http://support.microsoft.com/kb/222905[^]

I think not, but repost this in suggestions and bug reports to get official attention from the admins. Today's lesson is brought to you by the word "niggardly". Remember kids, don't attribute to racism what can be explained by Scandinavian language roots. -- Robert Royall

I've had nothing but a positive experience mixing managed/unmanaged code. The largest overhead is the .NET framework, depending on how much of it you use. A good place to start is compiling your MFC code with the /clr switch. The only cpp modules that need to be compiled with /clr are the ones that have managed code. You can also control what gets compiled managed/unmanaged at the function level using the #pragma managed/ #pragma unmanaged directives. You'll of course want to understand managed programming and understand C++/CLI, which is esentially a different language than C++. .NET Programming Guide[^] Mark Mark Salsbery Microsoft MVP - Visual C++ :java:

Looking at this page about variadic macros[^], it should be __VA_ARGS__? You won't find it in any header file, though, because it's something built into the pre-processor.

Most excellent! Every article I looked for on MSDN (via search) popped up vista related articles. Thank you very much!! :)

A memory leak like pointers but see Memory(-Leak) and Exception Trace (CRT and COM Leaks)[^]. ;)

Cool thanks for the update! I know I've had a similar problem in the past - I think I gave up and re-created the project from scratch. It hasn't happened since VS 2003 for me thankfully :) Cheers, Mark Mark Salsbery Microsoft MVP - Visual C++ :java:

Mark Salsbery wrote: that's the hard way to code! No, that's the new age way to code. Having your head in the sand, or other equally dark places, is fine as long as you keep typing! led mike

led mike wrote: Have you seen Graus's new article[^]? This is what we have come to! Yes! I've linked to it before :) Mark Salsbery Microsoft MVP - Visual C++ :java:

Note that there is an important difference between the two ways Mark gave you to get the mouse position. The position associated with the window message may be different than the one you get from GetCursorPos() -- the former is the one at the time the message was sent, the latter is the mouse's position at the time of the call.  If your application is very busy, the two values can be very different. You likely want the position associated with the message: GetCurrentMessage() -> pt Peace! -=- James Please rate this message - let me know if I helped or not! * * * If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong! Remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road! See DeleteFXPFiles

http://www.codeproject.com/KB/macros/resorg.aspx[^]

C++ has try-catch blocks, usually goto is not needed. :) If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile. This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke