Repository navigation
Conversation
vadi2
force-pushed
the
ccr-14671218-tf96z6-help-3
branch
5 times, most recently
from
November 18, 2026 02:20
29d4523 to
177df45
Compare
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
force-pushed
the
ccr-14671218-tf96z6-help-3
branch
from
November 18, 2026 02:57
177df45 to
89bd944
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 newgameTourShownkey in theuipreferences. 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)
GameTourTestcovers: 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.GameTourPseudoLocaleTestchecks each step's layout in en-XA and ar-XB.docs/divergences.md, "The UI tour", says why.🤖 Generated with Claude Code
https://claude.ai/code/session_016ujaeFyaqXXDx8xjoThE6J