Skip to content

multiple_text_inputs example: Navigate to next input on submission#24295

Open
ickshonpe wants to merge 2 commits into
bevyengine:mainfrom
ickshonpe:multiple_text_inputs-submit-nav
Open

multiple_text_inputs example: Navigate to next input on submission#24295
ickshonpe wants to merge 2 commits into
bevyengine:mainfrom
ickshonpe:multiple_text_inputs-submit-nav

Conversation

@ickshonpe
Copy link
Copy Markdown
Contributor

@ickshonpe ickshonpe commented May 14, 2026

Objective

In the multiple_text_inputs example, the input focus should move to the next text input after the user submits the input's contents.

Solution

  • In submit_text, after submission, use the TabNavigation system param to find the next input, and set it as the InputFocus.
  • Submit on just Enter. The Ctrl + Enter chord should be reserved for inputs that allow new lines.

@ickshonpe ickshonpe added A-UI Graphical user interfaces, styles, layouts, and widgets A-Text Rendering and layout for characters labels May 14, 2026
@github-project-automation github-project-automation Bot moved this to Needs SME Triage in UI May 14, 2026
@ickshonpe ickshonpe added C-Examples An addition or correction to our examples D-Straightforward Simple bug fixes and API improvements, docs, test and examples S-Needs-Review Needs reviewer attention (from anyone!) to move forward C-Refinement Improves output quality, without fixing a clear bug or adding new functionality. and removed A-Text Rendering and layout for characters labels May 14, 2026
@alice-i-cecile alice-i-cecile added this to the 0.19 milestone May 14, 2026
Copy link
Copy Markdown
Contributor

@amtep amtep left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm a bit worried about why it was Ctrl-Enter in the first place. Was there some undocumented reason?

@ickshonpe
Copy link
Copy Markdown
Contributor Author

I'm a bit worried about why it was Ctrl-Enter in the first place. Was there some undocumented reason?

No I think it was just that the system handling submit was copied from one of the other examples, and the key chord wasn't changed.

@kfc35 kfc35 added S-Ready-For-Final-Review This PR has been approved by the community. It's ready for a maintainer to consider merging it and removed S-Needs-Review Needs reviewer attention (from anyone!) to move forward labels May 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-UI Graphical user interfaces, styles, layouts, and widgets C-Examples An addition or correction to our examples C-Refinement Improves output quality, without fixing a clear bug or adding new functionality. D-Straightforward Simple bug fixes and API improvements, docs, test and examples S-Ready-For-Final-Review This PR has been approved by the community. It's ready for a maintainer to consider merging it

Projects

Status: Needs SME Triage

Development

Successfully merging this pull request may close these issues.

4 participants