From aa958504affbe59cc02100bd4035e4548468217b Mon Sep 17 00:00:00 2001
From: whitequark <whitequark@whitequark.org>
Date: Tue, 11 Oct 2016 13:56:41 +0000
Subject: [PATCH] GTK: use 3DConnexion button 0 instead of SI_APP_FIT_BUTTON.

The libspnav library doesn't even define SI_APP_FIT_BUTTON, which
appears to be Windows-specific functionality, perhaps a physical
button remapped with some logic. Just use 0 instead, since that
seems always safe.
---
 src/platform/gtkmain.cpp | 7 ++-----
 1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/src/platform/gtkmain.cpp b/src/platform/gtkmain.cpp
index a0f9e82..1560e28 100644
--- a/src/platform/gtkmain.cpp
+++ b/src/platform/gtkmain.cpp
@@ -54,10 +54,7 @@
 #include "config.h"
 
 #ifdef HAVE_SPACEWARE
-#   include <spnav.h>
-#   ifndef SI_APP_FIT_BUTTON
-#       define SI_APP_FIT_BUTTON 31
-#   endif
+#include <spnav.h>
 #endif
 
 namespace SolveSpace {
@@ -1576,7 +1573,7 @@ static GdkFilterReturn GdkSpnavFilter(GdkXEvent *gxevent, GdkEvent *, gpointer)
             break;
 
         case SPNAV_EVENT_BUTTON:
-            if(!sev.button.press && sev.button.bnum == SI_APP_FIT_BUTTON) {
+            if(!sev.button.press && sev.button.bnum == 0) {
                 SS.GW.SpaceNavigatorButtonUp();
             }
             break;