ntk 5.1.0 → 5.2.0

package/lib/window.js

@@ -918,6 +918,30 @@ export default class Window extends Drawable {
     if (idx !== -1) f.rafCbs.splice(idx, 1);
   }
 
+  /**
+   * Whether the fence for the last frame is still unanswered — the server has
+   * not yet confirmed it consumed everything that frame drew.
+   *
+   * The one bit of frame-clock state worth publishing, because it is the
+   * difference between the two ways a toolkit can answer a discrete input.
+   * Drawing the response inside the event handler costs a frame less latency:
+   * the blit goes out with the handler's own requests (see the `_present()`
+   * at the end of the event dispatch) instead of waiting for the next paced
+   * frame. Drawing it while a frame is in flight costs a frame's *work* for
+   * nothing: the present is deferred until the ack and coalesces with the
+   * one already pending, so only the last paint is ever seen. So `false`
+   * means "draw it now", `true` means "leave it to the frame clock" — which
+   * is how a burst of discrete events (a spun wheel) paints its first notch
+   * immediately and folds the rest into one catch-up frame.
+   *
+   * Always `false` under `frameSync: false`: no fence is ever sent, so there
+   * is nothing to wait for, and a caller gating on this gets the unpaced
+   * behaviour that option asks for.
+   */
+  frameInFlight() {
+    return this._frame.inFlight;
+  }
+
   _present() {
     if (!this._backing) return;
     if (this._frame.inFlight) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ntk",
-  "version": "5.1.0",
+  "version": "5.2.0",
   "description": "Desktop UI toolkit for X11 with canvas-like 2d and OpenGL rendering",
   "author": "Andrey Sidorov <sidorares@yandex.ru>",
   "license": "MIT",