texture-bridge

Plugin texture-bridge from marketplace electron-texture-bridge in naporin0624/electron-texture-bridge. Commands read from the repo's manifest — 4 days ago.

Skills (8)

• choosing-texture-bridge-api

  Use when deciding which @napolab/texture-bridge API tier to use for a feature — simple vs core, Syphon/Spout output vs in-app preview/monitor, forwardSharedTexture vs forwardFrames — when reviewing an integration plan that uses the library, or when unsure whether a texture-bridge function, method, o

• delivering-imported-textures

  Use when delivering a GPU texture to a renderer from the Electron main process — about to call `sharedTexture.importSharedTexture` / `sendSharedTexture` / `release()` by hand, deciding where `release()` belongs, wrapping delivery in try/finally or neverthrow tees to guarantee exactly-once release, w

• diagnosing-dead-frame-forwards

  Use when forwarded frames stop arriving — a preview or monitor window that goes black or shows a "no signal" placeholder, a multiviewer deck frozen on its last frame, previews that die during a long session or for only some targets while Syphon/Spout output keeps working, a forwardFrames registratio

• handling-texture-bridge-failures

  Use when adding error handling, telemetry, or crash-safety to code that uses @napolab/texture-bridge — deciding whether a call needs a try/catch or a Result.fromThrowable wrapper, reviewing the failure handling of a texture-bridge integration, defining error classes for bridge or receiver operations

• managing-frame-forward-lifecycle

  Use when registering or tearing down `TextureBridge.forwardFrames` targets — a monitor/multiviewer window the user can close and reopen, decks connected and disconnected repeatedly, a bridge disposed while forwards are still registered — or when about to add "destroyed"/"closed" listener bookkeeping

• migrating-to-forward-frames

  Use when replacing an existing Electron preview/monitor implementation with @napolab/texture-bridge zero-copy forwarding — capturePage polling, paint-event bitmap IPC, toBitmap/toPNG transfers, or a Syphon loopback feeding an in-app window — or when upgrading to the release that ships forwardFrames

• receiving-shared-textures

  Use when implementing the receiving side of @napolab/texture-bridge shared-texture frames in an Electron renderer — consuming forwardFrames/forwardSharedTexture output, displaying createSharedTextureReceiver frames, building a multiviewer/preview grid, or debugging leaked VideoFrames, black canvases

• setting-up-texture-bridge

  Use when installing or bootstrapping @napolab/texture-bridge in an Electron app — adding Syphon/Spout output, wiring an offscreen window with useSharedTexture, configuring electron-vite for the native addon, or debugging black/garbled output right after setup.

Similar plugins