62 ClutterStage

Top level visual element to which actors are placed.

62.1 Overview

<clutter-stage> is a top level 'window' on which child actors are
placed and manipulated.

Backends might provide support for multiple stages. The support for this
feature can be checked at run-time using the
clutter-feature-available function and the
‘CLUTTER_FEATURE_STAGE_MULTIPLE’ flag. If the backend used supports
multiple stages, new <clutter-stage> instances can be created
using clutter-stage-new. These stages must be managed by the
developer using clutter-actor-destroy, which will take care of
destroying all the actors contained inside them.

<clutter-stage> is a proxy actor, wrapping the backend-specific
implementation of the windowing system. It is possible to subclass
<clutter-stage>, as long as every overridden virtual function
chains up to the parent class corresponding function.

62.2 Usage

— Function: clutter-stage-new ⇒ (ret <clutter-actor>)

Creates a new, non-default stage. A non-default stage is a new top-level
actor which can be used as another container. It works exactly like the
default stage, but while clutter-stage-get-default will always
return the same instance, you will have to keep a pointer to any
<clutter-stage> returned by clutter-stage-new.

The ability to support multiple stages depends on the current backend.
Use clutter-feature-available and
‘CLUTTER_FEATURE_STAGE_MULTIPLE’ to check at runtime whether a
backend supports multiple stages.

ret

a new stage, or ‘#f’ if the default backend does not support
multiple stages. Use clutter-actor-destroy to programmatically
close the returned stage.

Asks to place the stage window in the fullscreen or unfullscreen states.

( Note that you shouldn't assume the window is definitely full screen
afterward, because other entities (e.g. the user or window manager)
could unfullscreen it again, and not all window managers honor requests
to fullscreen windows.

If you want to receive notification of the fullscreen state you should
either use the <"fullscreen"> and <"unfullscreen">
signals, or use the notify signal for the <"fullscreen-set">
property