Thanks for playing flare :)

To help making flare better (and avoiding such segmentation faults), would you mind helpingto find out what exactly broke?

To help the developers you need to have a "debug" build.

This can be done by (assuming you compile flare yourself, as you wrote ./flare as first command)

cmake . -DCMAKE_BUILD_TYPE="Debug"

make

# now start flare using a debugger

gdb ./flare

# when gdb is started, type

run

# When it crashes, type: (the window will still stay open, so you notice the crash by everything freezing)

backtrace full

# lots of text should appear, this will be helpful for developers, thanks a lot :)

quit

I've opened an issue for this here: https://github.com/clintbellanger/flare-engine/issues/72

@Stefan

He shouldn't have to do all that, because I already know where the crash is happening. See this commit: https://github.com/dorkster/flare-engine/commit/cd7a9bcc2bd89be6faaa0905...

dorkster's sent in a patch for this. It's part of the v0.17.1 bugfix release.

For now we've just prevented the crash -- but binding those mouse buttons is a bit trickier (I think, with SDL). We'll look into it.

Any recommendations for a good 5(+?) button mouse for testing? I could stand to replace the crappy mouse I have now on my PC.