flighthook

Shared type definitions for the flighthook launch monitor bridge. Used by both the application crate (flighthook-app) and the UI crate (flighthook-ui).

Configuration types

Types for the TOML config file and unit-aware value handling.

Bus event types

All inter-component communication flows through a single broadcast<FlighthookMessage> channel.

Message envelope

Event variants (FlighthookEvent)

All variants are flat struct variants with named fields (no wrapper types).

Shot data

Actor status

Commands and outcomes

API types

REST request/response types shared between the web server and the UI.

WebSocket client (client feature)

A synchronous WebSocket client for connecting to a running flighthook server. Behind the client feature flag (adds tungstenite). Not included by default so UI/WASM builds are unaffected.

[dependencies]
flighthook = { version = "0.0.6", features = ["client"] }

Blocking

use flighthook::{FlighthookClient, ShotAggregator};

let mut client = FlighthookClient::connect("ws://localhost:3030/api/ws", "my-app")?;
let mut shots = ShotAggregator::new();

loop {
    let msg = client.recv()?;
    if let Some(shot) = shots.feed(&msg) {
        println!("shot #{}: {:?}", shot.shot_number, shot.ball.launch_speed);
    }
}

Non-Blocking (Game Loop)

use flighthook::{FlighthookClient, ShotAggregator};

let mut client = FlighthookClient::connect("ws://localhost:3030/api/ws", "my-sim")?;
client.set_nonblocking(true)?;
let mut shots = ShotAggregator::new();

loop {
    // Drain all pending messages
    while let Ok(Some(msg)) = client.try_recv() {
        if let Some(shot) = shots.feed(&msg) {
            println!("shot #{}: {:?}", shot.shot_number, shot.ball.launch_speed);
        }
    }
    // ... render frame, physics tick, etc.
}

Game state types