Skip to content

A first-run tour of the game screen, as desktop Mudlet's UI tour - #169

Open
vadi2 wants to merge 1 commit into
mainfrom
ccr-14671218-tf96z6-help-3
Open

vadi2 wants to merge 1 commit into
mainfrom
ccr-14671218-tf96z6-help-3

Conversation

@vadi2

@vadi2 vadi2 commented Nov 17, 2026 •

Copy link
Copy Markdown
Member

Brief overview of PR changes/additions

The first time the game screen shows, a short tour walks through it with a card for each step. The steps follow desktop Mudlet's UI tour (TUiTour.cpp) in its order: a welcome, the console, the input line, the scripts button, the settings button, and a last step that says where to find the tour again. While a step shows, its control is lit through the dimmed screen. The buttons are Skip tour, Back, Next and Finish, as on desktop, and the phone's Back closes the tour. The tour is marked shown as soon as it starts, under a new gameTourShown key in the ui preferences. About's Help section gets "Take a UI tour" to show it again. Controls are marked by what they are (Modifier.tourTarget), so the tour still finds them when the title bar changes. While MainActivity explains an engine Android stopped, or the notification permission, the tour waits until that dialog is answered or hidden.

Motivation for adding to Mudlet

Plan lane 18, "Help and first steps". A new player gets a minute's guide to the game screen, as on desktop. With TalkBack, only the card is read while the tour shows, and each step is read once.

Other info (issues closed, discussion etc)

  • GameTourTest covers: shown once, Skip, Back, About's re-show through Finish, what TalkBack hears, where the card goes, and the wait for the engine-stopped explanation. GameTourPseudoLocaleTest checks each step's layout in en-XA and ar-XB.
  • The tour shows to every player, and scripts are not told about it. docs/divergences.md, "The UI tour", says why.

🤖 Generated with Claude Code

https://claude.ai/code/session_016ujaeFyaqXXDx8xjoThE6J

@vadi2
vadi2 force-pushed the ccr-14671218-tf96z6-help-3 branch 5 times, most recently from 29d4523 to 177df45 Compare November 18, 2026 02:20
The first time the game screen shows, a card per step walks through it
in desktop's order: a welcome, the console, the input line, the scripts
button, the settings button and a last step saying where to find the
tour again, each control lit through a dimmed screen. Skip tour, Back,
Next and Finish as on desktop; Back on the phone closes it. It is
marked shown as it starts, under a new key in the ui preferences, and
About's Help has "Take a UI tour" to show it again. TalkBack reads the
card alone while it shows, and each step once. Controls are marked by
what they are, so the tour follows them wherever the title bar puts
them. While MainActivity explains the notification permission or an
engine Android stopped, the tour waits until that is answered or hidden.
GameTourPseudoLocaleTest checks each step in en-XA and ar-XB.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016ujaeFyaqXXDx8xjoThE6J
@vadi2
vadi2 force-pushed the ccr-14671218-tf96z6-help-3 branch from 177df45 to 89bd944 Compare November 18, 2026 02:57

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants