Race Timing System: Opening the application and updating

Opening the application and updating

The HTML pages now embed their styling and interface utilities. Opening a page directly from Finder/Explorer displays a polished local-file view with startup instructions. It is not a running timing session: controls remain disabled until you open the receiver-served application. Run Launch Timing.command (Mac) or Launch Timing.bat (Windows), keep the terminal open, and use the browser window it opens. Default local address: http://127.0.0.1:8765/.

When a receiver is unavailable or provides an older interface, the page shows recovery guidance rather than an endless loading state. A port conflict also gives actionable guidance. If an older receiver is already using port 8765, close it when no race is being timed and launch this version, or use an explicit different port. This update does not stop an existing receiver automatically.

To retain a timing session, keep your existing race_config.json and race_timing.sqlite3 database together. Back up the session before updating. Replace application files in your existing session folder, leaving the configuration/database in place, or start this version with explicit --config and --db paths pointing to that session. Do not overwrite real configuration with the supplied example configuration. The embedded pages do not create fake race results or claim a reader is connected.