fix(zaparoo): stabilize frontend framebuffer scaling - #15
Conversation
Defer launcher startup until EDID selection completes, accept pre-Qt framebuffer scaling deterministically, and reassert the live framebuffer geometry without clearing Qt's painted frame.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (2)
Included review availability: 2 reviews are currently available. Based on recent review activity, included reviews refill at 3 per hour. 📝 WalkthroughWalkthroughThe PR adds ChangesHDMI startup and framebuffer recovery
Estimated code review effort: 3 (Moderate) | ~20 minutes Merge Risk: ⚪ Minimal · up to The framebuffer scaling and frontend lifecycle changes are merge-ready after normal checks and review; no actionable merge-blocking risk remains. Sequence Diagram(s)sequenceDiagram
participant Menu
participant Launcher
participant Video
participant Frontend
Menu->>Launcher: queue alt_launcher_init()
Launcher->>Video: enable framebuffer
Launcher->>Frontend: spawn frontend
Launcher->>Video: reassert HDMI scanout
Launcher->>Video: retry video initialization after EDID delay
Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
Comment |
Summary
Verification
./docker-build.shPaired frontend change: ZaparooProject/zaparoo-frontend#377
Ref ZaparooProject/zaparoo-frontend#171
Summary by CodeRabbit