Struct ExtractPlugin 

pub struct ExtractPlugin<T>(PhantomData<fn() -> T>);

Installs extraction for one exact evaluated frame payload type.

For example, a frame containing Vec<T> needs ExtractPlugin<Vec<T>>; installing ExtractPlugin<T> alone does not visit that batch. Recursive Extract implementations handle the values inside the registered type. Handwritten systems can also be added to RenderSchedule::Extract.

Tuple Fields

0: PhantomData<fn() -> T>

Trait Implementations

impl<T> Default for ExtractPlugin<T>

fn default() -> Self

Returns the “default value” for a type.

impl<T: Extract + Send + Sync + 'static> Plugin for ExtractPlugin<T>

fn build(&self, app: &mut App)

Configures the [App] to which this plugin is added.

fn ready(&self, _app: &App) -> bool

Has the plugin finished its setup? This can be useful for plugins that need something asynchronous to happen before they can finish their setup, like the initialization of a renderer. Once the plugin is ready, finish should be called.

fn finish(&self, _app: &mut App)

Finish adding this plugin to the [App], once all plugins registered are ready. This can be useful for plugins that depends on another plugin asynchronous setup, like the renderer.

fn cleanup(&self, _app: &mut App)

Runs after all plugins are built and finished, but before the app schedule is executed. This can be useful if you have some resource that other plugins need during their build step, but after build you want to remove it and send it to another thread.

fn name(&self) -> &str

Configures a name for the [Plugin] which is primarily used for checking plugin uniqueness and debugging.

fn is_unique(&self) -> bool

If the plugin can be meaningfully instantiated several times in an [App], override this method to return false.