InputPad

Menus, the on-screen touch pad, typed cheats and the help overlay: everything the player clicks, touches or types outside the 3D world.

Location

Purpose

InputPad started as a port of the original Mobile Eggbert's InputPad class (its touch buttons) and now owns every 2D screen of the game: the main menu with its three player slots, Setup, Pause, Resume, Win and Lost, the ten demo positions, the loading and goodbye screens, the Play phase's on-screen pad, the list of active cheats, the debug panel, the hidden cheat menu and the F1 help overlay. It also parses the typed cheat words.

Each screen has an Update… method that hit-tests the mouse (or touches) and returns a small struct of "what was pressed", and a Draw… method. Layout is in the original's 640 x 480 reference space, scaled to the window; where the original's rectangles do not fit that space (the five-button Pause row, the nine-button cheat menu) they are proportionally adapted. InputPad never changes game state itself: it reports, and GalaxyEggbertGame acts.

Collaborators

Uses

• ScreenKeyboard (ScreenKeyboard.hpp): the on-screen keyboard used to name a demo; passed in through DemoSlotsExtras and UpdateDemoSlots.
• CheatConfig.hpp: kCheatsEnabled, from the CMake option GALAXY_EGGBERT_ENABLE_CHEATS (default ON).
• TextMetrics for the original's proportional font; QuadBatch for rectangles; sheets such as pad.png, text.png and the menu backgrounds.

Used by

• GalaxyEggbertGame only: phase input in GalaxyEggbertGameUpdate.cpp, drawing in GalaxyEggbertGameDraw.cpp, the demo positions in GalaxyEggbertGameDemo.cpp. The host's FocusNavigator (arrow keys and d-pad choosing a lit button) works over InputPad's static rectangles such as DemoSlotRect and DemoListRowRect.
• The help panel's open/close state is the small ControlsHelp struct in ControlInput.hpp; InputPad only draws it.

Screens it handles

Key members

A selection of the public API declared in InputPad.hpp (the header also has many static rectangle helpers such as PauseRecordRect and DemoExportRect).

How it is used

In Play the host merges the pad with the keyboard and gamepad. The mouse drives the visible pad only when CNA reports a touch screen; on a desktop without one the clicks belong to the camera. An excerpt from src/GalaxyEggbertCNA/GalaxyEggbertGameUpdate.cpp:

// Invisible desktop controls must not claim clicks intended for the camera.
if (tickInput_.touchControlsEnabled)
{
    inputPadClaimedMouse = inputPad_.UpdatePlay(
        mouse, viewport.getWidthProperty(), viewport.getHeightProperty(), padPlayInput);
}
else
{
    inputPad_.ResetTouchState();
}
{
    GalaxyEggbert::Game::InputPad::PlayInput touchInput;
    if (inputPad_.UpdatePlayTouches(touches, viewport.getWidthProperty(),
                                    viewport.getHeightProperty(), touchInput))
    {
        inputPadClaimedMouse = true;
    }
    ...
}

Later in the same tick the host calls UpdateTypedGhostCheat and applies the returned TypedCheat (ApplyTypedCheat); the effects live in the host, InteractionSystem and BlupiController, which InputPad cannot reach.

Typed cheats

As in the original, letters typed during Play go into a rolling buffer of up to 32 letters, and a cheat fires when the buffer ends with its word. The longest matching word wins, and the buffer is cleared after a word, except after quick, so that quicklollypop can still be typed. The table has 33 words (as of 2026-11-10; help and cheats are the same cheat), the original's 21 desktop words, help/cheats, the MODERN build's words (ghost, quick, zoom, debug, fps, position, honest), compass, fairplay and xnjttjpo (Speedy Blupi's word for editing a mission; here it opens the world being played in the 3D editor). The full list is on Cheats & Diagnostics.

Letters arrive in order from CNA's KeyDownEXT presses (orderedLetter), so fast typing works on every device; autoplay passes -1 and uses keyboard snapshots. While the buffer holds the start of a word, those letters are filtered out of the gameplay keys until released (weelkeys no longer turns Blupi with its final S).

Rules and invariants

• Report, do not act. InputPad has no access to the simulation; every Update… returns flags or an index and the host decides.
• Press semantics follow the original: Jump is level-triggered (held while the pointer is on it); every other button fires once, on release over the same button.
• The stick is discrete: the offset from its centre is thresholded to -1, 0 or +1 per axis.
• The Play pad is drawn and mouse-hit-tested only when CNA reports a touch screen (TouchPanel::GetCapabilities()).
• Typed cheats are accepted only in Play. With fairplay on, only fairplay is accepted; after honest, nothing until the game quits. Resume log format v7 records the ordered letters and the lock, so a replay reproduces them.
• With -DGALAXY_EGGBERT_ENABLE_CHEATS=OFF, TypedCheatWords is empty, the gesture and the cheat menu never open, and the help panel says "Cheats disabled".

Tests

VerifyGEInputPad (tools/VerifyGEInputPad.cpp, registered in CMakeLists.txt) runs without a window or graphics device, driving InputPad with synthetic MouseState, touch and keyboard values. It checks the Play stick, Jump, Action and Pause semantics, multi-touch and accelerometer controls, the Pause, Setup, Resume, Win/Lost and main-menu rectangles (including Exit, Help, Demo, Galaxy and Demos), the demo positions and Import's list (no two controls overlap), the cheat gesture and menu, typed cheat words, the active-cheat list's rectangle, the debug panel's lines, the F1 help open/close behaviour (ControlsHelp), the WASD aliases, the ScreenKeyboard and FocusNavigator.

Related pages

• Hud: the in-game information bar
• GalaxyEggbertGame: phases and the tick that calls InputPad
• ResumeLog, DemoReplay: recorded input, cheat letters and locks
• Input, Controls, Cheats & Diagnostics
• Demos & Recordings