0f)) { mVertical = zero. 0f; } else { mVertical = lVertical; } } else { mHorizontal = zero. 0f; mVertical = zero. 0f; } go back precise; } } Let's end by way of creating a mild amendment to the sport itself. eventually, edit DroidBlaster. cpp and replace InputService at every one iteration:#include "DroidBlaster. hpp" #include "Log. hpp" namespace dbs { ... packt::status DroidBlaster::onStep() { mTimeService->update(); mBackground. update(); mShip. update(); if (mInputService->update() ! = packt::STATUS_OK) { go back packt::STATUS_KO; } if (mGraphicsService->update() ! = packt::STATUS_OK) { go back packt::STATUS_KO; } go back packt::STATUS_OK; } ... } What simply occurred? we now have prolonged our enter procedure to deal with the keyboard, D-Pad, and trackball occasions. D-Pad may be regarded as a keyboard extension and is processed a similar method. certainly, D-Pad and keyboard occasions are transported within the similar constitution (AInputEvent) and dealt with by means of an analogous API (prefixed with AKeyEvent). the next desk lists the most key occasion tools: AKeyEvent_getAction() point out if button is down (AKEY_EVENT_ACTION_DOWN) or published (AKEY_EVENT_ACTION_UP). observe that a number of key activities may be emitted in batch (AKEY_EVENT_ACTION_MULTIPLE). AKeyEvent_getKeyCode() To retrieve the particular button being pressed (defined in android/keycodes. h), for instance, AKEYCODE_DPAD_LEFT for the left button. AKeyEvent_getFlags() Key occasions should be linked to a number of flags that supply a variety of details at the occasion like AKEY_EVENT_LONG_PRESS, AKEY_EVENT_FLAG_SOFT_KEYBOARD for occasion originated from an emulated keyboard. AKeyEvent_getScanCode() is the same to a key code other than that this is often the uncooked key identity, based and varied from machine to equipment. AKeyEvent_getMetaState() Meta states are flags that point out if a few modifier keys like Alt or Shift are pressed at the same time (for instance, AMETA_SHIFT_ON, AMETA_NONE, and so on). AKeyEvent_getRepeatCount() shows what number instances the button occasion happened, often should you depart button down. AKeyEvent_getDownTime() to understand whilst a button used to be pressed. even though a few of them (especially optical ones) behave like a D-Pad, trackballs usually are not utilizing an analogous API. truly, trackballs are dealt with throughout the AMotionEvent API (like contact events). after all, a few info supplied for contact occasions isn't really consistently to be had on trackballs. crucial services to examine are: AMotionEvent_getAction() to grasp if an occasion represents a stream motion (as against a press action). AMotionEvent_getX() AMotionEvent_getY() To get trackball circulate. AKeyEvent_getDownTime() to grasp if trackball is pressed (like D-Pad motion button). presently, so much trackballs use an all-or-nothing strain to point the click occasion. anything difficult with trackballs, that will not be noticeable at the start, is that no occasion up is generated to point that trackball has complete relocating. furthermore, trackball occasions are generated as a chain (as a burst) which makes it tougher to become aware of while move is completed.