Skip to content

feat(): Support 1920x1200 and 2048x1536#155

Merged
asturur merged 2 commits into
mainfrom
more-res
May 25, 2026
Merged

feat(): Support 1920x1200 and 2048x1536#155
asturur merged 2 commits into
mainfrom
more-res

Conversation

@asturur
Copy link
Copy Markdown
Member

@asturur asturur commented May 25, 2026

Summary

Really just add the resolutions in the list, seems to go fine

close #155

Summary by CodeRabbit

  • New Features
    • Added 2048x1536 resolution option to MiSTer display settings for expanded configuration support.

Review Change Stack

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 25, 2026

📝 Walkthrough

Walkthrough

The PR extends the MiSTer resolution picker list with a new 2048x1536 entry and updates the macOS launch script to set two environment variables (ZAPAROO_CORE_ENDPOINT and ZAPAROO_CRT_PREVIEW_SCALE) before starting the frontend, while removing the --crt command-line argument from the frontend invocation.

Changes

Configuration and Launch Updates

Layer / File(s) Summary
MiSTer resolution picker extension
rust/frontend/src/models/settings.rs
MISTER_RESOLUTIONS list is extended to include the 2048x1536 resolution for MiSTer builds.
macOS script runtime configuration and launch
scripts/run-macos-mister-core.sh
Environment variables ZAPAROO_CORE_ENDPOINT and ZAPAROO_CRT_PREVIEW_SCALE are exported to configure the runtime; frontend is invoked without the --crt argument.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 A new resolution joins the fray,
While environment whispers find their way,
The script now speaks in softer tones,
No more --crt upon the stones!
✨ Small tweaks, but oh so bright!

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name Status Explanation Resolution
Title check ⚠️ Warning The title mentions supporting two resolutions (1920x1200 and 2048x1536), but the raw summary shows only 2048x1536 was added to the list; the title appears misaligned with actual changes. Verify which resolutions were actually added and update the title to match the actual implementation, or ensure both resolutions were added as intended.
Description check ⚠️ Warning The PR description lacks detail and is missing several required sections from the template including Motivation, Screenshots/recordings, Test plan, and Checklist items. Add a more complete description following the template: include explicit Motivation/issue link, Test plan details documenting how changes were verified, and confirm all Checklist items were completed.
✅ Passed checks (3 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch more-res

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@scripts/run-macos-mister-core.sh`:
- Around line 19-21: The ZAPAROO_CRT_PREVIEW_SCALE export is ineffective because
the CRT-native path is disabled by removing the --crt flag; restore passing the
--crt flag to the FRONTEND invocation (or add logic to append --crt when
ZAPAROO_CRT_PREVIEW_SCALE is set) so that the scale env var is actually
consumed; update the exec line that invokes "${FRONTEND}" to include the --crt
option (or conditionalize based on ZAPAROO_CRT_PREVIEW_SCALE) to re-enable the
CRT-native path.
- Line 18: The script currently hardcodes ZAPAROO_CORE_ENDPOINT to a private LAN
IP which breaks other environments; change it so the variable is overrideable by
checking for an existing environment value and falling back to a sensible
default (e.g., ws://localhost:7497/api/v0.1) using shell parameter expansion
instead of the fixed IP, and update the comment near the ZAPAROO_CORE_ENDPOINT
declaration to note that callers can override it via the environment.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: da96923d-5721-4c0e-97ad-b9c644c6209f

📥 Commits

Reviewing files that changed from the base of the PR and between 60d3ad4 and d0d61a1.

📒 Files selected for processing (2)
  • rust/frontend/src/models/settings.rs
  • scripts/run-macos-mister-core.sh

@@ -17,5 +17,5 @@ fi

export ZAPAROO_CORE_ENDPOINT="ws://192.168.1.176:7497/api/v0.1"
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Avoid committing a machine-specific core endpoint in the shared runner script.

Line 18 hardcodes a private LAN IP, which will fail for most environments. Make it overrideable with a default so the script works out-of-the-box and still supports local customization.

Suggested fix
-export ZAPAROO_CORE_ENDPOINT="ws://192.168.1.176:7497/api/v0.1"
+: "${ZAPAROO_CORE_ENDPOINT:=ws://127.0.0.1:7497/api/v0.1}"
+export ZAPAROO_CORE_ENDPOINT
 export ZAPAROO_CRT_PREVIEW_SCALE=3
 exec "${FRONTEND}"
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
export ZAPAROO_CORE_ENDPOINT="ws://192.168.1.176:7497/api/v0.1"
: "${ZAPAROO_CORE_ENDPOINT:=ws://127.0.0.1:7497/api/v0.1}"
export ZAPAROO_CORE_ENDPOINT
export ZAPAROO_CRT_PREVIEW_SCALE=3
exec "${FRONTEND}"
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@scripts/run-macos-mister-core.sh` at line 18, The script currently hardcodes
ZAPAROO_CORE_ENDPOINT to a private LAN IP which breaks other environments;
change it so the variable is overrideable by checking for an existing
environment value and falling back to a sensible default (e.g.,
ws://localhost:7497/api/v0.1) using shell parameter expansion instead of the
fixed IP, and update the comment near the ZAPAROO_CORE_ENDPOINT declaration to
note that callers can override it via the environment.

Comment on lines 19 to 21
export ZAPAROO_CRT_PREVIEW_SCALE=3
exec "${FRONTEND}" --crt
exec "${FRONTEND}"
# exec "${FRONTEND}" --crt
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

ZAPAROO_CRT_PREVIEW_SCALE is ineffective without --crt, causing a behavior regression.

On Line 20, removing --crt disables the CRT-native path; in that path, Line 19’s ZAPAROO_CRT_PREVIEW_SCALE is actually consumed. This makes the new scale export a no-op and changes startup behavior.

Suggested fix
 export ZAPAROO_CORE_ENDPOINT="ws://192.168.1.176:7497/api/v0.1"
 export ZAPAROO_CRT_PREVIEW_SCALE=3
-exec "${FRONTEND}"
+exec "${FRONTEND}" --crt
 # exec "${FRONTEND}" --crt
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
export ZAPAROO_CRT_PREVIEW_SCALE=3
exec "${FRONTEND}" --crt
exec "${FRONTEND}"
# exec "${FRONTEND}" --crt
export ZAPAROO_CRT_PREVIEW_SCALE=3
exec "${FRONTEND}" --crt
# exec "${FRONTEND}" --crt
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@scripts/run-macos-mister-core.sh` around lines 19 - 21, The
ZAPAROO_CRT_PREVIEW_SCALE export is ineffective because the CRT-native path is
disabled by removing the --crt flag; restore passing the --crt flag to the
FRONTEND invocation (or add logic to append --crt when ZAPAROO_CRT_PREVIEW_SCALE
is set) so that the scale env var is actually consumed; update the exec line
that invokes "${FRONTEND}" to include the --crt option (or conditionalize based
on ZAPAROO_CRT_PREVIEW_SCALE) to re-enable the CRT-native path.

@asturur asturur merged commit 03e75ae into main May 25, 2026
6 checks passed
@asturur asturur deleted the more-res branch May 25, 2026 18:15
@github-actions github-actions Bot locked and limited conversation to collaborators May 25, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant