pub fn show(&self) {
        unsafe {
            ffi::cogl_onscreen_show(self.to_glib_none().0);
        }
    }
/// This requests to make `self` visible to the user.
///
/// Actually the precise semantics of this function depend on the
/// window system currently in use, and if you don't have a
/// multi-windowining system this function may in-fact do nothing.
///
/// This function will implicitly allocate the given `self`
/// framebuffer before showing it if it hasn't already been allocated.
///
/// When using the Wayland winsys calling this will set the surface to
/// a toplevel type which will make it appear. If the application wants
/// to set a different type for the surface, it can avoid calling
/// `Onscreen::show` and set its own type directly with the Wayland
/// client API via `cogl_wayland_onscreen_get_surface`.
///
/// `<note>`Since Cogl doesn't explicitly track the visibility status of
/// onscreen framebuffers it wont try to avoid redundant window system
/// requests e.g. to show an already visible window. This also means
/// that it's acceptable to alternatively use native APIs to show and
/// hide windows without confusing Cogl.`</note>`
///
This requests to make `self` visible to the user.
Actually the precise semantics of this function depend on the
window system currently in use, and if you don't have a
multi-windowining system this function may in-fact do nothing.

This function will implicitly allocate the given `self`
framebuffer before showing it if it hasn't already been allocated.

When using the Wayland winsys calling this will set the surface to
a toplevel type which will make it appear. If the application wants
to set a different type for the surface, it can avoid calling
`Onscreen::show` and set its own type directly with the Wayland
client API via `cogl_wayland_onscreen_get_surface`.

``Since Cogl doesn't explicitly track the visibility status of
onscreen framebuffers it wont try to avoid redundant window system
requests e.g. to show an already visible window. This also means
that it's acceptable to alternatively use native APIs to show and
hide windows without confusing Cogl.``
This requests to make ` self ` visible to the user . Actually the precise semantics of this function depend on the window system currently in use and if you don ' t have a multi - windowining system this function may in - fact do nothing . This function will implicitly allocate the given ` self ` framebuffer before showing it if it hasn ' t already been allocated . When using the Wayland winsys calling this will set the surface to a toplevel type which will make it appear . If the application wants to set a different type for the surface it can avoid calling ` Onscreen :: show ` and set its own type directly with the Wayland client API via ` cogl_wayland_onscreen_get_surface ` . ` ` Since Cogl doesn ' t explicitly track the visibility status of onscreen framebuffers it wont try to avoid redundant window system requests e . g . to show an already visible window . This also means that it ' s acceptable to alternatively use native APIs to show and hide windows without confusing Cogl . ` `
pub fn show(&self) {
        unsafe {
            ffi::cogl_onscreen_show(self.to_glib_none().0);
        }
    }
pub fn show ( & self ) { unsafe { ffi :: cogl_onscreen_show ( self . to_glib_none ( ) . 0 ) ; } }
This requests to make `self` visible to the user.
This requests to make ` self ` visible to the user .
&self
&self