Planet Chili

No, that just means your program didn't load all the debugging information.

What you are seeing is a phenomenon known as keyboard ghosting.

Those functions are user-defined (chilli wrote them). If you want to understand the code you can look over it and (I believe) chili goes over the framework in a couple of the videos.

Think that's because compiler thinks you're declaring a function.

I would avoid using c++ and winapi for doing UI stuff if at all possible. Go c# with .net if targetting windows. If targeting all platforms, see if you can find a framework that would suit your fancy.

if statements check to see if what is in the () evaluates to true. Operators such as == < > <= >= ! all return boolean values. If you simply put a variable inside the such as if(var) then it checks to see if var == true.

In summary
if(var) same as if(var == true)
if(!var) same as if(var == false)

There shouldn't be a reason why you would need two mutexes there. Unless those locks are used in other blocks of async code. The only thing I can think of is it might add enough delay to 'solve' a race condition.

Well, I am not chilli but... if you ever want to fool around with writing construct/destruct functions similar to new/delete you gotta. (or perhaps overloading....)

Glad I was able to help out. I have been out of c++ for some time now due to family/work/school reasons and I am trying to retain it.

Ok, I looked through your first post a little bit more thoroughly and think I see the problem. I don't have a lot of time right now and if this doesn't help ill look at the code tomorrow morning if possible. Try friending those global operators in the class. This should give them access to the class...

What compiler errors are you getting? It is also helpful to post the code you are having difficulties with as it helps to resolve the problem a lot faster. That bottom code block is a little redundant as well. It would be simpler to do one of the following return x>= rhs.x && y>= rhs.y; or perhaps.....