react-x11 2.15.3 → 2.16.0

package/src/types/tray.d.ts

@@ -7,8 +7,12 @@ import type { DesktopBackend, TrayFeatures } from './capabilities.js';
 
 export interface TrayClickEvent {
   button: 'left' | 'right' | 'middle';
-  /** Where the click was, in global top-left screen coordinates — the anchor
-   * for a popup of your own. */
+  /** Where the click was: global top-left screen coordinates in **logical
+   * pixels**, the unit a `<popup>`'s `x`/`y` and `anchor={{ rect }}` take —
+   * the anchor for a popup of your own. The freedesktop protocol names no
+   * unit for its point and hosts differ, so there it is read against the
+   * monitors and the pointer; docs/desktop.md "The tray" says where that
+   * cannot tell. */
   x: number;
   y: number;
   /** The item's rect. `0` on the freedesktop rung, whose protocol has none —
@@ -73,6 +77,14 @@ export interface TrayState {
    * flips it back.
    */
   available: boolean;
+  /**
+   * Whether `available` is an answer yet: true on the first frame on macOS,
+   * where the status item is made there and then, and for `null` options;
+   * on the freedesktop tray, once the host has taken or refused the item. An
+   * app whose whole UI is its tray renders nothing until this, instead of a
+   * fallback window that flashes on every start.
+   */
+  settled: boolean;
   /** Which mechanism took it, or null. */
   backend: DesktopBackend | null;
   /** What that mechanism can do. Empty until `available` settles. */