dc7b83666a
It is intuitive to try to scroll the conversation history using the mouse in the TUI, but prior to this change, we only supported scrolling via keyboard events. This PR enables mouse capture upon initialization (and disables it on exit) such that we get `ScrollUp` and `ScrollDown` events in `codex-rs/tui/src/app.rs`. I initially mapped each event to scrolling by one line, but that felt sluggish. I decided to introduce `ScrollEventHelper` so we could debounce scroll events and measure the number of scroll events in a 100ms window to determine the "magnitude" of the scroll event. I put in a basic heuristic to start, but perhaps someone more motivated can play with it over time. `ScrollEventHelper` takes care of handling the atomic fields and thread management to ensure an `AppEvent::Scroll` event is pumped back through the event loop at the appropriate time with the accumulated delta.
25 lines
626 B
Rust
25 lines
626 B
Rust
use codex_core::protocol::Event;
|
|
use crossterm::event::KeyEvent;
|
|
|
|
pub(crate) enum AppEvent {
|
|
CodexEvent(Event),
|
|
|
|
Redraw,
|
|
|
|
KeyEvent(KeyEvent),
|
|
|
|
/// Scroll event with a value representing the "scroll delta" as the net
|
|
/// scroll up/down events within a short time window.
|
|
Scroll(i32),
|
|
|
|
/// Request to exit the application gracefully.
|
|
ExitRequest,
|
|
|
|
/// Forward an `Op` to the Agent. Using an `AppEvent` for this avoids
|
|
/// bubbling channels through layers of widgets.
|
|
CodexOp(codex_core::protocol::Op),
|
|
|
|
/// Latest formatted log line emitted by `tracing`.
|
|
LatestLog(String),
|
|
}
|