ANDROID: Do not limit situations where fast is enabled
authorCraig Robbins <kde.psych@gmail.com>
Fri, 15 May 2015 03:20:53 +0000 (13:20 +1000)
committerCraig Robbins <kde.psych@gmail.com>
Fri, 15 May 2015 03:22:07 +0000 (13:22 +1000)
Before this commit autofast for Android was ignored if the user was sneaking, digging or building. There is no reason for this and it impedes movement control

src/game.cpp

index 74ae211bf836615592e1c8d714204362396b71a7..e27ec37dd2d0d1ebfd1557d5093a2cc96845292d 100644 (file)
@@ -2997,17 +2997,10 @@ void Game::updatePlayerControl(const CameraOrientation &cam)
 
 #ifdef ANDROID
        /* For Android, invert the meaning of holding down the fast button (i.e.
-        * holding down the fast button -- if there is one -- means walk), unless
-        * performing an action, sneaking or jumping.
+        * holding down the fast button -- if there is one -- means walk)
         */
-       const u32 autofast_exludebits =
-                         (1U << 4) | (1U << 6)     // jump, sneak
-                       | (1U << 7) | (1U << 8);    // left state, right state
-
-       if ((keypress_bits & autofast_exludebits) == 0) {
-               control.aux1 = control.aux1 ^ true;
-               keypress_bits ^= ((u32)(1U << 5));
-       }
+       control.aux1 = control.aux1 ^ true;
+       keypress_bits ^= ((u32)(1U << 5));
 #endif
 
        client->setPlayerControl(control);