this.Bug==Bug.Report(Fixed); “If we are all in agreement on the decision - then I propose we postpone further discussion of this matter until our next meeting to give ourselves time to develop disagreement and perhaps gain some understanding of what the decision is all about.”-Alfred P. Sloan

I just set up MediaWiki for the AwasuWiki and while it's not 100% what I was looking for, it was the only one that I tried that worked straight away :-) 0 bottles of beer on the wall, 0 bottles of beer, you take 1 down, pass it around, 4294967295 bottles of beer on the wall. Awasu 2.2.1 [^]: A free RSS/Atom feed reader with support for Code Project.

Tom Archer wrote: Awesome! Let me know how it goes. Will do. Tom Archer wrote: If everything goes well for us, we'll finally be closing next week. Cool. So, what kinda place did ya get? Jeremy Falcon

I agree - the outcome will be the same. But there is still the legal cost to the defense process that companies are going to try and mitigate. I'm willing to bet that companies have determined (correctly or not) that it costs less to maintain a 'defense' patent portfolio than it does to provide an affirmative defense of prior art everytime some jackass company-of-patent-lawyers tries to grab some of your cash via the utterly broken patent system. -- Russell Morris "So, broccoli, mother says you're good for me... but I'm afraid I'm no good for you!" - Stewy

Oh Noooooooooooo!!!!!!!!!!! Regards, Brian Dela :-)

Yeap, that may be the solution. Unfortunately, I'm getting used to it, and to have something telling me when a mail is received.

Yuck. Unfortunately, in my case, this guy was just plain stupid. He had been a programmer for 25+ years, and nobody ever had the cojones to tell him he wasn't any good at it. Or maybe they did, and he simply didn't get the message. The one good thing was, he was finally laid off, and ended up working for one of our competitors ( :laugh: tee hee :laugh: ). Software Zen: delete this;

I've been using MFC for the past 6 years, and I never had problems either. However, if you take a while to test the same code without using MFC you'll find some differences. I even had to programm MFC like classes, to compile a MFC program without MFC, so I know how they are implemented. To allow window classes inheritance you require virtual fuctions and some extra code, which make's the code more complex. For example, in a callback function, it's much easier to return 0 if the message is not processed, that to run some code to call derived message maps. This doesn't mean MFC isn't properly implemented, just that this "layering" has a cost, and it's not a bad idea to determine it.