Crate zng_view_api

source
Expand description

The View Process API.

Zng isolates all render and windowing related code to a different process (the view-process), this crate provides the API that must be implemented to create a view-process backend, plus the Controller that can be used from an app-process to spawn and communicate with a view-process.

§VERSION

The VERSION of this crate must match exactly in both App-Process and View-Process, otherwise a runtime panic error is generated.

§Same Process Patch

Dynamically loaded same process implementers must propagate a StaticPatch, otherwise the view will not connect.

§Crate

This crate is part of the zng project.

§Cargo Features

This crate provides 2 feature flags, 1 enabled by default.

§"ipc"

Enables creation of separate or pre-build view.

Only enables in cfg(not(any(target_os = "android", target_arch = "wasm32", target_os = "ios"))) builds.

Enabled by default.

§"var"

Implement IntoVar<T> for API types.

Modules§

Structs§

  • Identifier for a specific analog axis on some device.
  • Border side line style and color.
  • View Process controller, used in the App Process.
  • Device ID in channel.
  • Identifier for a drag drop operation.
  • Offset and color in a gradient.
  • View process is online.
  • Identifies a reference frame.
  • Packaged API request.
  • Packaged API response.
  • Dynamic view-process “same process” implementations must patch the static variables used by the view-api. This patch also propagates the tracing and log contexts.
  • Configuration for starting a view-process.
  • View-process generation, starts at one and changes every respawn, it is never zero.
  • The View-Process disconnected or has not finished initializing, try again after the inited event.

Enums§

Constants§

  • The App Process and View Process must be build using the same exact version and this is validated during run-time, causing a panic if the versions don’t match.

Traits§

  • The view-process API.