Camel

och. forgot two things

Thing no. 7.

A paragui but also Visual C++ vs gcc issue I think.
A few of these similar gcc compiler errors fixed by e.g.
(MSG_CALLBACK_OBJ)btnStartGame_Click
changes to:
(MSG_CALLBACK_OBJ)&MenuController::btnStartGame_Click

MenuController.cpp:283: error: argument of type `bool (MenuController::)(int,
PG_Widget*, long unsigned int, void*)' does not match `bool
(PG_EventObject::*)(int, PG_Widget*, long unsigned int, void*)'

btnStartGame->SetEventObject(MSG_BUTTONCLICK, this, (MSG_CALLBACK_OBJ)btnStartGame_Click);

~/src/Camel/src> grep MSG_CALLBACK /usr/include/paragui/*
/usr/include/paragui/paragui_types.h:typedef bool (*MSG_CALLBACK)(int id, PG_Widget* widget, unsigned long data, void *clientdata);
/usr/include/paragui/paragui_types.h:typedef bool (PG_EventObject::*MSG_CALLBACK_OBJ)(int id, PG_Widget* widget, unsigned long data, void* clientdata);

#define PARAGUI_CALLBACK(funcname) \
bool funcname (int id, PG_Widget* widget, unsigned long data, void *clientdata)
CHANGE TO THIS:
btnStartGame->SetEventObject(MSG_BUTTONCLICK, this, (MSG_CALLBACK_OBJ)&MenuController::btnStartGame_Click);

Thing no. 8.

There is profiling code in there that is windows specific.
TODO: port this
Compiling without the profiling flags set is fine on linux.