Skip to content

Per-screen panorama text: full independent styling per panel#73

Merged
flocom merged 3 commits into
mainfrom
claude/brave-carson-wh3ztq
Jun 12, 2026
Merged

Per-screen panorama text: full independent styling per panel#73
flocom merged 3 commits into
mainfrom
claude/brave-carson-wh3ztq

Conversation

@flocom

@flocom flocom commented Jun 12, 2026

Copy link
Copy Markdown
Owner

What

When "Text per screen" is enabled on a panoramic screenshot, each panel now has its own complete, independent text settings — not just distinct text content, but full styling: headline + subheadline content, font, size, color, weight, italic, underline/strikethrough, text background, position, vertical offset, and line height.

The Text tab gains a Screen 1 / Screen 2 / … selector at the top. Pick a screen, then every control in the tab edits that screen.

How

  • Data model: the screenshot's text container gains panelTexts[] — one full text object per panel — created on enable by cloning current settings and migrating any legacy per-panel content (panelHeadlines/panelSubheadlines).
  • Editing vs rendering split: getText() / setTextSetting() redirect to the active panel when per-screen mode is on, so the existing Text-tab controls "just work". The renderer instead reads the container via the new getContainerText() and draws each panel from its own object (makePanelTxt).
  • Language: panels follow the current global language selection for both editing and rendering.
  • Backward compatible: projects using the old per-panel content model still render via a fallback path and migrate seamlessly on first interaction.
  • Persistence: panelTexts is plain JSON and round-trips through the MCP server unchanged; the update_screenshot tool description was updated.

Test

Serve locally, set a screenshot's Span screens to 2, enable "Text per screen", then give Screen 1 and Screen 2 different headlines, colors, sizes and positions — each panel renders independently, and export slices them correctly.

Note: verified by syntax check + code review only (no browser automation available in this environment); manual UI verification recommended before relying on it.

https://claude.ai/code/session_01MdKQ535A9VpJfHff3Yv5xk


Generated by Claude Code

claude added 3 commits June 12, 2026 09:03
…copy

renderPerScreenTextUI captured screenshot.text once, but getText()
reassigns screenshot.text to a fresh object on every render, so the
toggle/field handlers were mutating an orphaned object the renderer no
longer read — typed panel text never appeared and the toggle reverted.
Each handler now re-fetches the live object via getTextSettings().

Also store/read per-screen subheadlines under the subheadline language
key (matching makePanelTxt) instead of the headline language, so they
survive when the two languages differ.

https://claude.ai/code/session_01MdKQ535A9VpJfHff3Yv5xk
When "Text per screen" is on, each panorama panel now owns a complete
text object (panelTexts[]) — headline, subheadline AND all styling
(font, size, color, weight, position, offset, line height, text
background). The Text tab gains a Screen 1/2/… selector at the top; the
whole tab edits the selected panel.

- getText()/setTextSetting redirect to the active panel when per-screen
  mode is active; the renderer reads the container via getContainerText()
  and draws each panel from its own object (makePanelTxt).
- Panels follow the current language selection (edit + render).
- Enabling seeds panelTexts from current settings and migrates legacy
  panelHeadlines/panelSubheadlines content; old projects still render
  via a fallback path.
- panelTexts round-trips through the MCP server unchanged; tool docs
  updated.

https://claude.ai/code/session_01MdKQ535A9VpJfHff3Yv5xk
@flocom
flocom merged commit cd69cd0 into main Jun 12, 2026
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