[][src]Trait wayland_protocols::unstable::linux_explicit_synchronization::v1::client::zwp_linux_explicit_synchronization_v1::RequestsTrait

pub trait RequestsTrait {
    fn destroy(&self);
fn get_synchronization<F>(
        &self,
        surface: &Proxy<WlSurface>,
        implementor: F
    ) -> Result<Proxy<ZwpLinuxSurfaceSynchronizationV1>, ()>
    where
        F: FnOnce(NewProxy<ZwpLinuxSurfaceSynchronizationV1>) -> Proxy<ZwpLinuxSurfaceSynchronizationV1>
; }

Required methods

fn destroy(&self)

destroy explicit synchronization factory object

Destroy this explicit synchronization factory object. Other objects, including zwp_linux_surface_synchronization_v1 objects created by this factory, shall not be affected by this request.

This is a destructor, you cannot send requests to this object any longer once this method is called.

fn get_synchronization<F>(
    &self,
    surface: &Proxy<WlSurface>,
    implementor: F
) -> Result<Proxy<ZwpLinuxSurfaceSynchronizationV1>, ()> where
    F: FnOnce(NewProxy<ZwpLinuxSurfaceSynchronizationV1>) -> Proxy<ZwpLinuxSurfaceSynchronizationV1>, 

extend surface interface for explicit synchronization

Instantiate an interface extension for the given wl_surface to provide explicit synchronization.

If the given wl_surface already has an explicit synchronization object associated, the synchronization_exists protocol error is raised.

Graphics APIs, like EGL or Vulkan, that manage the buffer queue and commits of a wl_surface themselves, are likely to be using this extension internally. If a client is using such an API for a wl_surface, it should not directly use this extension on that surface, to avoid raising a synchronization_exists protocol error.

Loading content...

Implementations on Foreign Types

impl RequestsTrait for Proxy<ZwpLinuxExplicitSynchronizationV1>[src]

Loading content...

Implementors

Loading content...