AstrBot-Desktop/src/App.tsx

696 行
21 KiB
TypeScript

import { invoke } from "@tauri-apps/api/core";
import { listen } from "@tauri-apps/api/event";
import { getCurrentWindow } from "@tauri-apps/api/window";
import {
lazy,
Suspense,
useCallback,
useEffect,
useRef,
useState,
} from "react";
import { errorMessage } from "./lib/errorMessage";
import { ChatPanel } from "./features/chat/ChatPanel";
import { StatusBubble } from "./features/chat/StatusBubble";
const ProfileManager = lazy(() =>
import("./features/profiles/ProfileManager").then(({ ProfileManager }) => ({
default: ProfileManager,
})),
);
const PetPackImporter = lazy(() =>
import("./features/pet/PetPackImporter").then(({ PetPackImporter }) => ({
default: PetPackImporter,
})),
);
const DesktopBehaviorPage = lazy(() =>
import("./pages/SettingsPages").then(({ DesktopBehaviorPage }) => ({
default: DesktopBehaviorPage,
})),
);
const DesktopPetView = lazy(() =>
import("./features/pet/DesktopPetView").then(({ DesktopPetView }) => ({
default: DesktopPetView,
})),
);
const DiagnosticsPage = lazy(() =>
import("./pages/SettingsPages").then(({ DiagnosticsPage }) => ({
default: DiagnosticsPage,
})),
);
import { bootstrapStatusSchema, type BootstrapStatus } from "./types/bootstrap";
type PageKey = "chat" | "connections" | "desktop" | "pet" | "diagnostics";
type ChatSlot = "companion" | "operations";
type PetDisplayMode = "app-ui" | "desktop-floating";
type ThemeMode = "dark" | "light";
const initialStatus: BootstrapStatus = {
appVersion: "unknown",
platform: "unknown",
rustCore: "pending",
protocolVersion: "desktop-v1alpha1",
databaseSchemaVersion: 4,
};
const navigation: Array<{ key: PageKey; label: string; description: string }> =
[
{ key: "chat", label: "聊天", description: "陪伴与运维对话" },
{ key: "connections", label: "连接", description: "实例与槽位管理" },
{ key: "desktop", label: "桌面行为", description: "快速聊天与状态气泡" },
{ key: "pet", label: "桌宠", description: "形象与活动范围" },
{
key: "diagnostics",
label: "诊断与设置",
description: "运行状态与安全边界",
},
];
export function App() {
const params = new URLSearchParams(window.location.search);
const view = params.get("view");
const isQuickView = view === "quick";
const isBubbleView = view === "bubble";
const isPetView =
view === "pet" ||
window.location.hash === "#pet" ||
document.documentElement.dataset.astrbotPet === "true";
const quickSlot = params.get("slot");
const [page, setPage] = useState<PageKey>("chat");
const [theme, setTheme] = useState<ThemeMode>(() =>
localStorage.getItem("astrbot.theme") === "light" ? "light" : "dark",
);
const [status, setStatus] = useState(initialStatus);
const [error, setError] = useState<string | null>(null);
const [quickTarget, setQuickTarget] = useState<ChatSlot>(() =>
localStorage.getItem("astrbot.quickTarget") === "operations"
? "operations"
: "companion",
);
const [bubbleTarget, setBubbleTarget] = useState<"main" | "quick">(() =>
localStorage.getItem("astrbot.bubbleTarget") === "quick" ? "quick" : "main",
);
const [petDisplayMode, setPetDisplayMode] = useState<PetDisplayMode>(() =>
localStorage.getItem("astrbot.petDisplayMode") === "desktop-floating"
? "desktop-floating"
: "app-ui",
);
const refreshStatus = useCallback(async () => {
try {
const result = await invoke<unknown>("bootstrap_status");
setStatus(bootstrapStatusSchema.parse(result));
setError(null);
} catch (reason) {
setError(errorMessage(reason));
}
}, []);
useEffect(() => {
document.documentElement.dataset.theme = theme;
localStorage.setItem("astrbot.theme", theme);
}, [theme]);
useEffect(() => {
void refreshStatus();
}, [refreshStatus]);
useEffect(() => {
if (isBubbleView || isPetView || isQuickView) return;
const command =
petDisplayMode === "desktop-floating"
? "open_pet_window"
: "close_pet_window";
void invoke(command).catch((reason) => {
setError(errorMessage(reason));
});
}, [isBubbleView, isPetView, isQuickView, petDisplayMode]);
if (isBubbleView) return <StatusBubble />;
if (isPetView) return <DesktopPetView />;
if (isQuickView) {
return (
<main className="quick-app-shell">
<ChatPanel
fixedSlot={
quickSlot === "operations"
? "operations"
: quickSlot === "companion"
? "companion"
: undefined
}
/>
</main>
);
}
return (
<main className="app-shell">
<WindowChrome
theme={theme}
onToggleTheme={() =>
setTheme((current) => (current === "dark" ? "light" : "dark"))
}
fix(tauri): grant the window controls the permissions they call The minimize, maximize and close buttons did nothing. They were wired correctly; the ACL rejected them. core:default resolves to core:window:default, which grants only read-only queries — is-maximized is in it, which is why the maximize icon tracked state correctly, but minimize, toggle-maximize, close and start-dragging are not. Both windows are decorations: false, so with close denied the main window could not be closed at all except through the tray. Add two capabilities rather than widening the shared one: the main window gets the four controls it draws, and the pet window gets dragging alone, since it is moved by dragging its body and must not be able to close or resize itself. Every one of these calls was a bare void expression, so the rejection was swallowed and looked identical to an unwired button. Route them through a helper that reports the failure in the shell error banner. This is the second time a missing capability has surfaced as a silent no-op — the pet window previously had no entry at all. Add tests that read the shipped capability files and assert each permission the UI calls is granted to the window that calls it. Also translate the TypeError the Tauri shim throws outside the application into a sentence a user can act on. The dev server is reachable at 127.0.0.1:1420, so opening it in a browser and hitting save produced "Cannot read properties of undefined (reading 'invoke')". Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-27 01:19:42 +08:00
onError={setError}
/>
<div className="app-shell-body">
<aside className="app-sidebar">
<div className="brand-lockup">
<div className="brand-mark">A</div>
<div>
<strong>AstrBot Desktop</strong>
<span>Companion workspace</span>
</div>
</div>
<nav className="primary-nav" aria-label="主导航">
{navigation.map((item) => (
<button
key={item.key}
type="button"
className={page === item.key ? "nav-item active" : "nav-item"}
onClick={() => setPage(item.key)}
>
<span className="nav-item-icon">{navIcon(item.key)}</span>
<span>
<strong>{item.label}</strong>
<small>{item.description}</small>
</span>
</button>
))}
</nav>
<div className="sidebar-footer">
<span className="connection-dot" />
<span>本地客户端已启动</span>
</div>
</aside>
<section
className={
page === "chat" ? "app-content app-content-chat" : "app-content"
}
>
{page === "chat" ? null : <PageHeader page={page} />}
{error ? (
<p className="error-banner" role="alert">
IPC 暂不可用:{error}
</p>
) : null}
<Suspense fallback={<PageLoading />}>
{page === "chat" ? <ChatPage /> : null}
{page === "connections" ? <ProfileManager /> : null}
{page === "desktop" ? (
<DesktopBehaviorPage
bubbleTarget={bubbleTarget}
quickTarget={quickTarget}
onBubbleTargetChange={(value) => {
setBubbleTarget(value);
localStorage.setItem("astrbot.bubbleTarget", value);
}}
onQuickTargetChange={(value) => {
setQuickTarget(value);
localStorage.setItem("astrbot.quickTarget", value);
}}
onOpenQuickChat={() =>
void invoke("open_quick_chat_window", { slot: quickTarget })
}
/>
) : null}
{page === "pet" ? (
<PetPage
displayMode={petDisplayMode}
onDisplayModeChange={(value) => {
setPetDisplayMode(value);
localStorage.setItem("astrbot.petDisplayMode", value);
}}
/>
) : null}
{page === "diagnostics" ? (
<DiagnosticsPage
status={status}
onRefresh={() => void refreshStatus()}
/>
) : null}
</Suspense>
</section>
</div>
{petDisplayMode === "app-ui" ? (
<Suspense fallback={null}>
<InAppPetOverlay />
</Suspense>
) : null}
</main>
);
}
function WindowChrome({
theme,
onToggleTheme,
fix(tauri): grant the window controls the permissions they call The minimize, maximize and close buttons did nothing. They were wired correctly; the ACL rejected them. core:default resolves to core:window:default, which grants only read-only queries — is-maximized is in it, which is why the maximize icon tracked state correctly, but minimize, toggle-maximize, close and start-dragging are not. Both windows are decorations: false, so with close denied the main window could not be closed at all except through the tray. Add two capabilities rather than widening the shared one: the main window gets the four controls it draws, and the pet window gets dragging alone, since it is moved by dragging its body and must not be able to close or resize itself. Every one of these calls was a bare void expression, so the rejection was swallowed and looked identical to an unwired button. Route them through a helper that reports the failure in the shell error banner. This is the second time a missing capability has surfaced as a silent no-op — the pet window previously had no entry at all. Add tests that read the shipped capability files and assert each permission the UI calls is granted to the window that calls it. Also translate the TypeError the Tauri shim throws outside the application into a sentence a user can act on. The dev server is reachable at 127.0.0.1:1420, so opening it in a browser and hitting save produced "Cannot read properties of undefined (reading 'invoke')". Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-27 01:19:42 +08:00
onError,
}: {
theme: ThemeMode;
onToggleTheme: () => void;
fix(tauri): grant the window controls the permissions they call The minimize, maximize and close buttons did nothing. They were wired correctly; the ACL rejected them. core:default resolves to core:window:default, which grants only read-only queries — is-maximized is in it, which is why the maximize icon tracked state correctly, but minimize, toggle-maximize, close and start-dragging are not. Both windows are decorations: false, so with close denied the main window could not be closed at all except through the tray. Add two capabilities rather than widening the shared one: the main window gets the four controls it draws, and the pet window gets dragging alone, since it is moved by dragging its body and must not be able to close or resize itself. Every one of these calls was a bare void expression, so the rejection was swallowed and looked identical to an unwired button. Route them through a helper that reports the failure in the shell error banner. This is the second time a missing capability has surfaced as a silent no-op — the pet window previously had no entry at all. Add tests that read the shipped capability files and assert each permission the UI calls is granted to the window that calls it. Also translate the TypeError the Tauri shim throws outside the application into a sentence a user can act on. The dev server is reachable at 127.0.0.1:1420, so opening it in a browser and hitting save produced "Cannot read properties of undefined (reading 'invoke')". Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-27 01:19:42 +08:00
onError: (message: string) => void;
}) {
const [currentWindow, setCurrentWindow] = useState<ReturnType<
typeof getCurrentWindow
> | null>(null);
const [maximized, setMaximized] = useState(false);
useEffect(() => {
try {
const windowHandle = getCurrentWindow();
setCurrentWindow(windowHandle);
void windowHandle.isMaximized().then(setMaximized);
} catch {
return;
}
}, []);
fix(tauri): grant the window controls the permissions they call The minimize, maximize and close buttons did nothing. They were wired correctly; the ACL rejected them. core:default resolves to core:window:default, which grants only read-only queries — is-maximized is in it, which is why the maximize icon tracked state correctly, but minimize, toggle-maximize, close and start-dragging are not. Both windows are decorations: false, so with close denied the main window could not be closed at all except through the tray. Add two capabilities rather than widening the shared one: the main window gets the four controls it draws, and the pet window gets dragging alone, since it is moved by dragging its body and must not be able to close or resize itself. Every one of these calls was a bare void expression, so the rejection was swallowed and looked identical to an unwired button. Route them through a helper that reports the failure in the shell error banner. This is the second time a missing capability has surfaced as a silent no-op — the pet window previously had no entry at all. Add tests that read the shipped capability files and assert each permission the UI calls is granted to the window that calls it. Also translate the TypeError the Tauri shim throws outside the application into a sentence a user can act on. The dev server is reachable at 127.0.0.1:1420, so opening it in a browser and hitting save produced "Cannot read properties of undefined (reading 'invoke')". Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-27 01:19:42 +08:00
/// Every one of these is an ACL-gated IPC call. They used to be bare
/// `void ...()` expressions, so when the capability set was missing the
/// window permissions the rejection was swallowed and the buttons simply did
/// nothing, with no way to tell that from an unwired handler.
const runWindowAction = async (action: () => Promise<void>) => {
if (!currentWindow) return;
fix(tauri): grant the window controls the permissions they call The minimize, maximize and close buttons did nothing. They were wired correctly; the ACL rejected them. core:default resolves to core:window:default, which grants only read-only queries — is-maximized is in it, which is why the maximize icon tracked state correctly, but minimize, toggle-maximize, close and start-dragging are not. Both windows are decorations: false, so with close denied the main window could not be closed at all except through the tray. Add two capabilities rather than widening the shared one: the main window gets the four controls it draws, and the pet window gets dragging alone, since it is moved by dragging its body and must not be able to close or resize itself. Every one of these calls was a bare void expression, so the rejection was swallowed and looked identical to an unwired button. Route them through a helper that reports the failure in the shell error banner. This is the second time a missing capability has surfaced as a silent no-op — the pet window previously had no entry at all. Add tests that read the shipped capability files and assert each permission the UI calls is granted to the window that calls it. Also translate the TypeError the Tauri shim throws outside the application into a sentence a user can act on. The dev server is reachable at 127.0.0.1:1420, so opening it in a browser and hitting save produced "Cannot read properties of undefined (reading 'invoke')". Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-27 01:19:42 +08:00
try {
await action();
} catch (reason) {
onError(errorMessage(reason));
}
};
fix(tauri): grant the window controls the permissions they call The minimize, maximize and close buttons did nothing. They were wired correctly; the ACL rejected them. core:default resolves to core:window:default, which grants only read-only queries — is-maximized is in it, which is why the maximize icon tracked state correctly, but minimize, toggle-maximize, close and start-dragging are not. Both windows are decorations: false, so with close denied the main window could not be closed at all except through the tray. Add two capabilities rather than widening the shared one: the main window gets the four controls it draws, and the pet window gets dragging alone, since it is moved by dragging its body and must not be able to close or resize itself. Every one of these calls was a bare void expression, so the rejection was swallowed and looked identical to an unwired button. Route them through a helper that reports the failure in the shell error banner. This is the second time a missing capability has surfaced as a silent no-op — the pet window previously had no entry at all. Add tests that read the shipped capability files and assert each permission the UI calls is granted to the window that calls it. Also translate the TypeError the Tauri shim throws outside the application into a sentence a user can act on. The dev server is reachable at 127.0.0.1:1420, so opening it in a browser and hitting save produced "Cannot read properties of undefined (reading 'invoke')". Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-27 01:19:42 +08:00
const toggleMaximize = () =>
runWindowAction(async () => {
await currentWindow!.toggleMaximize();
setMaximized(await currentWindow!.isMaximized());
});
return (
<header
className="window-chrome"
data-tauri-drag-region
onDoubleClick={() => void toggleMaximize()}
onMouseDown={(event) => {
if (
event.button === 0 &&
!(event.target as HTMLElement).closest(
'[data-tauri-drag-region="false"]',
)
) {
fix(tauri): grant the window controls the permissions they call The minimize, maximize and close buttons did nothing. They were wired correctly; the ACL rejected them. core:default resolves to core:window:default, which grants only read-only queries — is-maximized is in it, which is why the maximize icon tracked state correctly, but minimize, toggle-maximize, close and start-dragging are not. Both windows are decorations: false, so with close denied the main window could not be closed at all except through the tray. Add two capabilities rather than widening the shared one: the main window gets the four controls it draws, and the pet window gets dragging alone, since it is moved by dragging its body and must not be able to close or resize itself. Every one of these calls was a bare void expression, so the rejection was swallowed and looked identical to an unwired button. Route them through a helper that reports the failure in the shell error banner. This is the second time a missing capability has surfaced as a silent no-op — the pet window previously had no entry at all. Add tests that read the shipped capability files and assert each permission the UI calls is granted to the window that calls it. Also translate the TypeError the Tauri shim throws outside the application into a sentence a user can act on. The dev server is reachable at 127.0.0.1:1420, so opening it in a browser and hitting save produced "Cannot read properties of undefined (reading 'invoke')". Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-27 01:19:42 +08:00
void runWindowAction(() => currentWindow!.startDragging());
}
}}
>
<span className="window-chrome-title">AstrBot Desktop</span>
<div className="window-chrome-actions" data-tauri-drag-region="false">
<button
aria-label={
theme === "dark" ? "Switch to light theme" : "Switch to dark theme"
}
className="window-theme-toggle"
onClick={onToggleTheme}
onMouseDown={(event) => event.stopPropagation()}
type="button"
>
{theme === "dark" ? "Light" : "Dark"}
</button>
<div className="window-controls" data-tauri-drag-region="false">
<button
aria-label="Minimize window"
className="window-control"
fix(tauri): grant the window controls the permissions they call The minimize, maximize and close buttons did nothing. They were wired correctly; the ACL rejected them. core:default resolves to core:window:default, which grants only read-only queries — is-maximized is in it, which is why the maximize icon tracked state correctly, but minimize, toggle-maximize, close and start-dragging are not. Both windows are decorations: false, so with close denied the main window could not be closed at all except through the tray. Add two capabilities rather than widening the shared one: the main window gets the four controls it draws, and the pet window gets dragging alone, since it is moved by dragging its body and must not be able to close or resize itself. Every one of these calls was a bare void expression, so the rejection was swallowed and looked identical to an unwired button. Route them through a helper that reports the failure in the shell error banner. This is the second time a missing capability has surfaced as a silent no-op — the pet window previously had no entry at all. Add tests that read the shipped capability files and assert each permission the UI calls is granted to the window that calls it. Also translate the TypeError the Tauri shim throws outside the application into a sentence a user can act on. The dev server is reachable at 127.0.0.1:1420, so opening it in a browser and hitting save produced "Cannot read properties of undefined (reading 'invoke')". Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-27 01:19:42 +08:00
onClick={() =>
void runWindowAction(() => currentWindow!.minimize())
}
onMouseDown={(event) => event.stopPropagation()}
type="button"
>
<span
className="window-glyph window-glyph-minimize"
aria-hidden="true"
/>
</button>
<button
aria-label={maximized ? "Restore window" : "Maximize window"}
className="window-control"
onClick={() => void toggleMaximize()}
onMouseDown={(event) => event.stopPropagation()}
type="button"
>
<span
className={`window-glyph window-glyph-maximize${maximized ? " is-restored" : ""}`}
aria-hidden="true"
/>
</button>
<button
aria-label="Close window"
className="window-control window-control-close"
fix(tauri): grant the window controls the permissions they call The minimize, maximize and close buttons did nothing. They were wired correctly; the ACL rejected them. core:default resolves to core:window:default, which grants only read-only queries — is-maximized is in it, which is why the maximize icon tracked state correctly, but minimize, toggle-maximize, close and start-dragging are not. Both windows are decorations: false, so with close denied the main window could not be closed at all except through the tray. Add two capabilities rather than widening the shared one: the main window gets the four controls it draws, and the pet window gets dragging alone, since it is moved by dragging its body and must not be able to close or resize itself. Every one of these calls was a bare void expression, so the rejection was swallowed and looked identical to an unwired button. Route them through a helper that reports the failure in the shell error banner. This is the second time a missing capability has surfaced as a silent no-op — the pet window previously had no entry at all. Add tests that read the shipped capability files and assert each permission the UI calls is granted to the window that calls it. Also translate the TypeError the Tauri shim throws outside the application into a sentence a user can act on. The dev server is reachable at 127.0.0.1:1420, so opening it in a browser and hitting save produced "Cannot read properties of undefined (reading 'invoke')". Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-27 01:19:42 +08:00
onClick={() => void runWindowAction(() => currentWindow!.close())}
onMouseDown={(event) => event.stopPropagation()}
type="button"
>
<span
className="window-glyph window-glyph-close"
aria-hidden="true"
/>
</button>
</div>
</div>
</header>
);
}
function InAppPetOverlay() {
const [visible, setVisible] = useState(true);
const [position, setPosition] = useState(() => {
try {
const saved = JSON.parse(
localStorage.getItem("astrbot.petPosition") ?? "null",
);
return saved && typeof saved.x === "number" && typeof saved.y === "number"
? saved
: { x: window.innerWidth >= 720 ? 280 : 24, y: 96 };
} catch {
return { x: window.innerWidth >= 720 ? 280 : 24, y: 96 };
}
});
const dragRef = useRef<{
pointerId: number;
offsetX: number;
offsetY: number;
} | null>(null);
const clampPosition = useCallback((x: number, y: number) => {
const safeLeft = window.innerWidth >= 720 ? 248 : 0;
const maxX = Math.max(safeLeft, window.innerWidth - 188);
return {
x: Math.max(safeLeft, Math.min(x, maxX)),
y: Math.max(0, Math.min(y, window.innerHeight - 226)),
};
}, []);
const savePosition = (x: number, y: number) => {
const next = clampPosition(x, y);
setPosition(next);
localStorage.setItem("astrbot.petPosition", JSON.stringify(next));
};
useEffect(() => {
const normalizePosition = () => {
const next = clampPosition(position.x, position.y);
if (next.x === position.x && next.y === position.y) return;
setPosition(next);
localStorage.setItem("astrbot.petPosition", JSON.stringify(next));
};
normalizePosition();
window.addEventListener("resize", normalizePosition);
return () => window.removeEventListener("resize", normalizePosition);
}, [clampPosition, position.x, position.y]);
useEffect(() => {
2026-07-27 00:23:42 +08:00
let active = true;
let unlisten: (() => void) | undefined;
2026-07-27 00:23:42 +08:00
void listen("pet-hide-requested", () => setVisible(false))
.then((cleanup) => {
if (active) {
unlisten = cleanup;
} else {
cleanup();
}
})
.catch(() => undefined);
return () => {
active = false;
unlisten?.();
unlisten = undefined;
};
}, []);
return visible ? (
<div
className="app-pet-overlay"
style={{ left: position.x, top: position.y }}
onContextMenu={(event) => {
event.preventDefault();
void invoke("show_pet_context_menu");
}}
onPointerDown={(event) => {
if (event.button !== 0) return;
event.currentTarget.setPointerCapture(event.pointerId);
dragRef.current = {
pointerId: event.pointerId,
offsetX: event.clientX - position.x,
offsetY: event.clientY - position.y,
};
}}
onPointerMove={(event) => {
if (dragRef.current?.pointerId !== event.pointerId) return;
savePosition(
event.clientX - dragRef.current.offsetX,
event.clientY - dragRef.current.offsetY,
);
}}
onPointerUp={(event) => {
if (dragRef.current?.pointerId === event.pointerId)
dragRef.current = null;
}}
onPointerCancel={() => {
dragRef.current = null;
}}
>
<DesktopPetView embedded />
</div>
) : null;
}
function navIcon(page: PageKey) {
return {
chat: "⌁",
connections: "◎",
desktop: "◈",
pet: "✦",
diagnostics: "⚙",
}[page];
}
function PageLoading() {
return (
<p className="loading-state" role="status" aria-live="polite">
加载中…
</p>
);
}
function PageHeader({ page }: { page: PageKey }) {
const current = navigation.find((item) => item.key === page) ?? navigation[0];
return (
<header className="page-header">
<div>
<p className="eyebrow">AstrBot Desktop</p>
<h1>{current.label}</h1>
<p className="subtitle">
{current.description},所有本机能力都经过客户端权限边界。
</p>
</div>
<div className="header-status-pill">
<span className="connection-dot" />
双槽位架构
</div>
</header>
);
}
function ChatPage() {
return (
<div className="chat-page">
<ChatPanel />
</div>
);
}
function PetPage({
displayMode,
onDisplayModeChange,
}: {
displayMode: PetDisplayMode;
onDisplayModeChange: (value: PetDisplayMode) => void;
}) {
const [monitors, setMonitors] = useState<
Array<{
name?: string;
width: number;
height: number;
scaleFactor: number;
isPrimary: boolean;
}>
>([]);
const [monitorIndex, setMonitorIndex] = useState(0);
const [positionMode, setPositionMode] = useState("edge");
const [alwaysOnTop, setAlwaysOnTop] = useState(true);
const [gameMode, setGameMode] = useState(false);
useEffect(() => {
void invoke<unknown>("list_monitor_geometries")
.then((value) => setMonitors(value as typeof monitors))
.catch(() => setMonitors([]));
}, []);
const applyPetPreferences = (
next: Partial<{
positionMode: string;
monitorIndex: number;
alwaysOnTop: boolean;
gameMode: boolean;
}> = {},
) => {
const preferences = {
positionMode: next.positionMode ?? positionMode,
monitorIndex: next.monitorIndex ?? monitorIndex,
alwaysOnTop: next.alwaysOnTop ?? alwaysOnTop,
gameMode: next.gameMode ?? gameMode,
};
void invoke("set_pet_window_preferences", { preferences }).catch(
() => undefined,
);
};
return (
<div className="page-stack">
<PetPackImporter />
{displayMode === "app-ui" ? (
<section className="pet-inline-preview" aria-label="应用内桌宠预览">
<div>
<span className="section-kicker">App UI</span>
<h2>应用内活动桌宠</h2>
<p>桌宠已叠加在主界面上,可直接拖动;关闭后可重新打开应用。</p>
</div>
</section>
) : null}
<section className="settings-grid">
<SettingCard
title="显示范围"
description="应用内活动桌宠不创建桌面浮窗,避免透明窗口白框。"
>
<select
value={displayMode}
onChange={(event) =>
onDisplayModeChange(event.target.value as PetDisplayMode)
}
>
<option value="app-ui">仅应用 UI 内</option>
<option value="desktop-floating">桌面浮动</option>
</select>
</SettingCard>
<SettingCard
title="活动策略"
description="为后续游戏模式和多显示器行为预留配置入口。"
>
<select defaultValue="smart">
<option value="smart">智能选择显示器</option>
<option value="primary">固定主屏</option>
<option value="secondary">优先副屏</option>
</select>
</SettingCard>
<SettingCard
title="运行桌宠"
description="应用内桌宠可在主界面中自由移动,不再创建白色桌面浮窗。"
>
{displayMode === "desktop-floating" ? (
<button type="button" onClick={() => onDisplayModeChange("app-ui")}>
改用应用内活动桌宠
</button>
) : (
<span className="form-note">应用内活动桌宠已显示,可直接拖动</span>
)}
</SettingCard>
<SettingCard
title="显示器与位置"
description="桌面版只会把桌宠放在屏幕安全边缘,不会覆盖游戏中心区域。"
>
<select
value={monitorIndex}
onChange={(event) => {
const next = Number(event.target.value);
setMonitorIndex(next);
applyPetPreferences({ monitorIndex: next });
}}
disabled={monitors.length === 0}
>
{monitors.map((monitor, index) => (
<option
value={index}
key={`${monitor.name ?? "monitor"}-${index}`}
>
{monitor.name ?? `显示器 ${index + 1}`}{" "}
{monitor.isPrimary ? "(主屏)" : ""}
</option>
))}
</select>
<select
value={positionMode}
onChange={(event) => {
const next = event.target.value;
setPositionMode(next);
applyPetPreferences({ positionMode: next });
}}
>
<option value="free">自由位置</option>
<option value="edge">安全边缘</option>
<option value="monitor">指定显示器</option>
</select>
</SettingCard>
<SettingCard
title="桌面行为"
description="置顶和游戏模式都可以随时关闭;权限或显示器不可用时自动回退。"
>
<label className="toggle-row">
<input
type="checkbox"
checked={alwaysOnTop}
onChange={(event) => {
const next = event.target.checked;
setAlwaysOnTop(next);
applyPetPreferences({ alwaysOnTop: next });
}}
/>
始终置顶
</label>
<label className="toggle-row">
<input
type="checkbox"
checked={gameMode}
onChange={(event) => {
const next = event.target.checked;
setGameMode(next);
applyPetPreferences({ gameMode: next });
}}
/>
游戏模式(安全边缘)
</label>
</SettingCard>
</section>
</div>
);
}
function SettingCard({
title,
description,
children,
}: {
title: string;
description: string;
children: React.ReactNode;
}) {
return (
<section className="setting-card">
<div>
<span className="section-kicker">Settings</span>
<h2>{title}</h2>
<p>{description}</p>
</div>
<div className="setting-card-controls">{children}</div>
</section>
);
}