jaredandClaude Opus 5
4d0cfaa194
Build Lotus Chat Desktop / prepare (push) Successful in 3s
Build Lotus Chat Desktop / build-windows (push) Canceled after 0s
Build Lotus Chat Desktop / build-linux (push) Canceled after 0s
Build Lotus Chat Desktop / build-arch (push) Canceled after 0s
Build Lotus Chat Desktop / update-manifest (push) Canceled after 0s
PTT and deafen are DOM key handlers in cinny and only fire while the Lotus
window has focus — alt-tab into a fullscreen game and the voice controls
stop working.
New native/hotkeys.rs (Windows): `set_global_hotkeys(bindings)` starts a
thread that samples GetAsyncKeyState for the configured W3C key codes every
~8 ms while a call is joined and emits a `lotus-global-hotkey` DOM event
{id, state, ctrl, alt, meta} on each press/release transition; an empty
list stops it. Deliberately NOT RegisterHotKey / a global-shortcut plugin:
those consume the key system-wide (a bare Space PTT would stop every other
app typing spaces). `global_hotkeys_supported` reports false off Windows,
where the commands are no-ops (Linux X11 could poll XQueryKeymap later;
Wayland has no non-consuming path). HotkeyPoll state is managed
unconditionally in setup. Cargo: Win32_UI_Input_KeyboardAndMouse feature.
Cross-checked against windows 0.61 for x86_64-pc-windows-msvc; Linux
cargo check clean.
Web side: cinny 00584d78 (useCallHotkeys + Settings → Calls toggle).
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PPmy3tPq869XDW4njjVaKA
49 lines
1.8 KiB
Rust
49 lines
1.8 KiB
Rust
//! Native desktop feature modules (Lotus Chat).
|
|
//!
|
|
//! Each feature lives in its own submodule exposing `#[tauri::command]`(s) and,
|
|
//! when it needs to register listeners/state, a `setup(&AppHandle)`. lib.rs adds
|
|
//! the commands to `generate_handler!` and calls `native::setup()` once during
|
|
//! app setup. Windows-only pieces are guarded with `#[cfg(target_os = "windows")]`
|
|
//! and compile-verified in CI (Gitea `windows` runner / GitHub `windows-latest`).
|
|
|
|
use tauri::{AppHandle, Manager};
|
|
|
|
pub mod aumid;
|
|
pub mod chrome;
|
|
pub mod focus_assist;
|
|
pub mod hotkeys;
|
|
pub mod jumplist;
|
|
pub mod network;
|
|
pub mod power;
|
|
pub mod smtc;
|
|
pub mod thumbbar;
|
|
pub mod toast;
|
|
|
|
/// Dispatch a DOM `CustomEvent` to the web client (mirrors `forward_deeplink` in
|
|
/// lib.rs) so native modules can push data to the frontend without pulling in
|
|
/// `@tauri-apps/api` on the web side. `detail_json` MUST be valid JSON (use
|
|
/// `serde_json::to_string`). `event` is a static, trusted name.
|
|
#[allow(dead_code)]
|
|
pub fn emit_to_web(app: &AppHandle, event: &str, detail_json: &str) {
|
|
if let Some(window) = app.get_webview_window("main") {
|
|
let _ = window.eval(&format!(
|
|
"window.dispatchEvent(new CustomEvent('{event}',{{detail:{detail_json}}}))"
|
|
));
|
|
}
|
|
}
|
|
|
|
/// Called once from lib.rs `.setup()`. Feature modules that need to register OS
|
|
/// listeners or managed state get initialized here. (jumplist/chrome are
|
|
/// command-only and need no setup.)
|
|
pub fn setup(app: &AppHandle) -> tauri::Result<()> {
|
|
// Register the AUMID + Start-Menu shortcut FIRST so the WinRT rich toast can
|
|
// create its notifier (before any notification path fires). Best-effort.
|
|
aumid::ensure_app_user_model_id(app);
|
|
power::setup(app)?;
|
|
thumbbar::setup(app)?;
|
|
smtc::setup(app)?;
|
|
network::setup(app)?;
|
|
focus_assist::setup(app)?;
|
|
Ok(())
|
|
}
|