Viewerframe Mode Refresh Fixed Today

To view live camera feeds using the ViewerFrame?Mode=Refresh

Troubleshooting

• Frame not responding: verify postMessage origin and that the frame script is loaded and listening.
• Infinite reload loop: check debounce logic and whether the refresh itself triggers the mode change.
• Visual glitches after refresh: ensure CSS variables and theme classes are reapplied on re-render.
• Cross-origin errors: confirm Access-Control headers and correct target origin.

Parameter B: mode_refresh_behavior

• sync (Synchronous): The UI freezes until the refresh completes. Use for critical data accuracy.
• async (Asynchronous): The refresh happens in a background thread. Use for live sports or gaming where dropped frames are acceptable to avoid UI lag.

Phase 1: The Unload (Pre-Refresh)

When a mode change is requested (e.g., from EDIT to PLAYBACK), the system must first destroy the current state. viewerframe mode refresh

3.2 Double Buffering with Viewport Lock

• Front buffer = ViewerFrame (displayed)
• Back buffer = next complete frame
• On refresh: copy only dirty rects from back to front (blit operation), not whole buffer.

Comments