Meta – 10

This class handles tracking and painting the root window background. By integrating with MetaWindowGroup we can avoid painting parts of the background that are obscured by other windows.

This class handles tracking and painting the root window background. By integrating with MetaWindowGroup we can avoid painting parts of the background that are obscured by other windows.

This class handles tracking and painting the root window background. By integrating with MetaWindowGroup we can avoid painting parts of the background that are obscured by other windows.

MetaBackgroundImage is an object that represents a loaded or loading background image.

MetaBackgroundImageCache caches loading of textures for backgrounds; there’s actually nothing background specific about it, other than it is tuned to work well for large images as typically are used for backgrounds.

The MetaBarrier structure contains only private data and should be accessed using the provided API.

MetaShadowFactory is used to create window shadows. It caches shadows internally so that multiple shadows created for the same shape with the same radius will share the same MetaShadow.

MetaShadow holds a shadow texture along with information about how to apply that texture to draw a window texture. (E.g., it knows how big the unscaled borders are on each side of the shadow texture.)

The MetaShadowParams structure holds information about how to draw a particular style of shadow.

MetaWindowShape represents a 9-sliced region with borders on all sides that are unscaled, and a constant central region that is scaled. For example, the regions representing two windows that are rounded rectangles, with the same corner radius but different sizes, have the same MetaWindowShape. MetaWindowShape is designed to be used as part of a hash table key, so has efficient hash and equal functions.

Function a window button can have. Note, you can’t add stuff here without extending the theme format to draw a new function and breaking all existing themes.

Indicates the appropriate effect to show the user for meta_compositor_show_window() and meta_compositor_hide_window()

Layers a window can be in. These MUST be in the order of stacking.

Menu the compositor should display for a given window.

Ensure log messages for the given topic topic will be printed.

Create a context.

Disables unredirection, can be useful in situations where having unredirected windows is undesirable like when recording a video.

Enables unredirection which reduces the overhead for apps like games.

Accessor for the singleton MetaBackend.

Returns TRUE if this instance of Mutter comes from Mutter restarting itself (for example to enable/disable stereo.) See meta_restart(). If this is the case, any startup visuals or animations should be suppressed.

Returns whether X synchronisation is currently enabled.

Allows users to register a custom handler for a builtin key binding.

Sets up a callback to be called at some later time. when determines the particular later occasion at which it is called. This is much like g_idle_add(), except that the functions interact properly with clutter event handling. If a “later” function is added from a clutter event handler, and is supposed to be run before the stage is redrawn, it will be run before that redraw of the stage, not the next one.

Removes a callback added with meta_later_add()

Stop printing log messages for the given topic topic. Note that this method does not stack with meta_add_verbose_topic(); i.e. if two calls to meta_add_verbose_topic() for the same topic are made, one call to meta_remove_verbose_topic() will remove it.

Starts the process of restarting the compositor. Note that Mutter’s involvement here is to make the restart visually smooth for the user - it cannot itself safely reexec a program that embeds libmuttter. So in order for this to work, the compositor must handle two signals - MetaDisplay::show-restart-message, to display the message passed here on the Clutter stage, and ::restart to actually reexec the compositor.