Weird error - SFML2.0

[Azaral]

So, I'm getting this weird error. I have a loop that runs the program and I exit the loop by setting a bool to false when escape is pressed. However, when I move my mouse to a general location, located near the upper left hand corner of the screen the program will exit on its' own. It doesn't throw any error message in release or in debug mode. If I take out the key checking part, it does not occur.

I'm using SFML 2.0 , using visual studio 2010 express, windows 7 OS

[Laurent]

Read the event tutorial carefully, especially the red paragraph.

[eXpl0it3r]

I'm to 99% sure, that you're doing the checking wrong, i.e. you only check what the key is pressed, but not if it's actually pressed.
But without the code we can't help you further and what Laurent said.

[Azaral]

Yes, you were correct. I was just checking what key was pressed instead of first checking if a key was pressed at all. I changed it and now it works fine. Thanks you!

[Azaral]

As an aside, I iterated through all possible mouse position and anytime the mouse x value was equal to 58 is when the exit occurred.

[zsbzsb]

As an aside, I iterated through all possible mouse position and anytime the mouse x value was equal to 58 is when the exit occurred.

It is not always going to be "58". If could be anything, when you don't check the event type first it leads to undefined behavior. That undefined behavior will vary depending on the compiler/os and other variables. That's why its best to avoid undefined behavior.

[Cornstalks]

It is not always going to be "58". If could be anything, when you don't check the event type first it leads to undefined behavior. That undefined behavior will vary depending on the compiler/os and other variables. That's why its best to avoid undefined behavior.

I don't know if I'd word that so strongly ("leads to undefined behavior"). If you actually read the C++ standard, it doesn't say it (accessing "inactive" members of a union) leads to undefined behavior (it also doesn't explicitly say it doesn't lead to undefined behavior).

But yes, it's certainly problematic