Handler for a proxy with version >= 4.
constraint 'a = [< `V4 | `V5 | `V6 ]
method private virtual on_destroy : [> `V4 | `V5 | `V6 ] t -> unitDestroy the xdg_toplevel.
This request destroys the role surface and unmaps the surface; see "Unmapping" behavior in interface section for details.
method private virtual on_set_parent : [> `V4 | `V5 | `V6 ] t ->
parent:
([ `Xdg_toplevel ], [> {Imports}1.Xdg_toplevel.versions ], [ `Server ])
{Proxy}2.t
option ->
unitSet the parent of this surface.
Set the "parent" of this surface. This surface should be stacked above the parent surface and all other ancestor surfaces.
Parent surfaces should be set on dialogs, toolboxes, or other "auxiliary" surfaces, so that the parent is raised when the dialog is raised.
Setting a null parent for a child surface unsets its parent. Setting a null parent for a surface which currently has no parent is a no-op.
Only mapped surfaces can have child surfaces. Setting a parent which is not mapped is equivalent to setting a null parent. If a surface becomes unmapped, its children's parent is set to the parent of the now-unmapped surface. If the now-unmapped surface has no parent, its children's parent is unset. If the now-unmapped surface becomes mapped again, its parent-child relationship is not restored.
The parent toplevel must not be one of the child toplevel's descendants, and the parent must be different from the child toplevel, otherwise the invalid_parent protocol error is raised.
method private virtual on_set_title : [> `V4 | `V5 | `V6 ] t ->
title:string ->
unitSet surface title.
Set a short title for the surface.
This string may be used to identify the surface in a task bar, window list, or other user interface elements provided by the compositor.
The string must be encoded in UTF-8.
method private virtual on_set_app_id : [> `V4 | `V5 | `V6 ] t ->
app_id:string ->
unitSet application ID.
Set an application identifier for the surface.
The app ID identifies the general class of applications to which the surface belongs. The compositor can use this to group multiple surfaces together, or to determine how to launch a new application.
For D-Bus activatable applications, the app ID is used as the D-Bus service name.
The compositor shell will try to group application surfaces together by their app ID. As a best practice, it is suggested to select app ID's that match the basename of the application's .desktop file. For example, "org.freedesktop.FooViewer" where the .desktop file is "org.freedesktop.FooViewer.desktop".
Like other properties, a set_app_id request can be sent after the xdg_toplevel has been mapped to update the property.
See the desktop-entry specification 0 for more details on application identifiers and how they relate to well-known D-Bus names and .desktop files.
0 https://standards.freedesktop.org/desktop-entry-spec/
Show the window menu.
Clients implementing client-side decorations might want to show a context menu when right-clicking on the decorations, giving the user a menu that they can use to maximize or minimize the window.
This request asks the compositor to pop up such a window menu at the given position, relative to the local surface coordinates of the parent surface. There are no guarantees as to what menu items the window menu contains, or even if a window menu will be drawn at all.
This request must be used in response to some sort of user action like a button press, key press, or touch down event.
method private virtual on_move : [> `V4 | `V5 | `V6 ] t ->
seat:([ `Wl_seat ], [> {Imports}1.Wl_seat.versions ], [ `Server ]) {Proxy}2.t ->
serial:int32 ->
unitStart an interactive move.
Start an interactive, user-driven move of the surface.
This request must be used in response to some sort of user action like a button press, key press, or touch down event. The passed serial is used to determine the type of interactive move (touch, pointer, etc).
The server may ignore move requests depending on the state of the surface (e.g. fullscreen or maximized), or if the passed serial is no longer valid.
If triggered, the surface will lose the focus of the device (wl_pointer, wl_touch, etc) used for the move. It is up to the compositor to visually indicate that the move is taking place, such as updating a pointer cursor, during the move. There is no guarantee that the device focus will return when the move is completed.
method private virtual on_resize : [> `V4 | `V5 | `V6 ] t ->
seat:([ `Wl_seat ], [> {Imports}1.Wl_seat.versions ], [ `Server ]) {Proxy}2.t ->
serial:int32 ->
edges:{Imports}1.Xdg_toplevel.Resize_edge.t ->
unitStart an interactive resize.
Start a user-driven, interactive resize of the surface.
This request must be used in response to some sort of user action like a button press, key press, or touch down event. The passed serial is used to determine the type of interactive resize (touch, pointer, etc).
The server may ignore resize requests depending on the state of the surface (e.g. fullscreen or maximized).
If triggered, the client will receive configure events with the "resize" state enum value and the expected sizes. See the "resize" enum value for more details about what is required. The client must also acknowledge configure events using "ack_configure". After the resize is completed, the client will receive another "configure" event without the resize state.
If triggered, the surface also will lose the focus of the device (wl_pointer, wl_touch, etc) used for the resize. It is up to the compositor to visually indicate that the resize is taking place, such as updating a pointer cursor, during the resize. There is no guarantee that the device focus will return when the resize is completed.
The edges parameter specifies how the surface should be resized, and is one of the values of the resize_edge enum. Values not matching a variant of the enum will cause the invalid_resize_edge protocol error. The compositor may use this information to update the surface position for example when dragging the top left corner. The compositor may also use this information to adapt its behavior, e.g. choose an appropriate cursor image.
method private virtual on_set_max_size : [> `V4 | `V5 | `V6 ] t ->
width:int32 ->
height:int32 ->
unitSet the maximum size.
Set a maximum size for the window.
The client can specify a maximum size so that the compositor does not try to configure the window beyond this size.
The width and height arguments are in window geometry coordinates. See xdg_surface.set_window_geometry.
Values set in this way are double-buffered. They will get applied on the next commit.
The compositor can use this information to allow or disallow different states like maximize or fullscreen and draw accurate animations.
Similarly, a tiling window manager may use this information to place and resize client windows in a more effective way.
The client should not rely on the compositor to obey the maximum size. The compositor may decide to ignore the values set by the client and request a larger size.
If never set, or a value of zero in the request, means that the client has no expected maximum size in the given dimension. As a result, a client wishing to reset the maximum size to an unspecified state can use zero for width and height in the request.
Requesting a maximum size to be smaller than the minimum size of a surface is illegal and will result in an invalid_size error.
The width and height must be greater than or equal to zero. Using strictly negative values for width or height will result in a invalid_size error.
method private virtual on_set_min_size : [> `V4 | `V5 | `V6 ] t ->
width:int32 ->
height:int32 ->
unitSet the minimum size.
Set a minimum size for the window.
The client can specify a minimum size so that the compositor does not try to configure the window below this size.
The width and height arguments are in window geometry coordinates. See xdg_surface.set_window_geometry.
Values set in this way are double-buffered. They will get applied on the next commit.
The compositor can use this information to allow or disallow different states like maximize or fullscreen and draw accurate animations.
Similarly, a tiling window manager may use this information to place and resize client windows in a more effective way.
The client should not rely on the compositor to obey the minimum size. The compositor may decide to ignore the values set by the client and request a smaller size.
If never set, or a value of zero in the request, means that the client has no expected minimum size in the given dimension. As a result, a client wishing to reset the minimum size to an unspecified state can use zero for width and height in the request.
Requesting a minimum size to be larger than the maximum size of a surface is illegal and will result in an invalid_size error.
The width and height must be greater than or equal to zero. Using strictly negative values for width and height will result in a invalid_size error.
method private virtual on_set_maximized : [> `V4 | `V5 | `V6 ] t -> unitMaximize the window.
Maximize the surface.
After requesting that the surface should be maximized, the compositor will respond by emitting a configure event. Whether this configure actually sets the window maximized is subject to compositor policies. The client must then update its content, drawing in the configured state. The client must also acknowledge the configure when committing the new content (see ack_configure).
It is up to the compositor to decide how and where to maximize the surface, for example which output and what region of the screen should be used.
If the surface was already maximized, the compositor will still emit a configure event with the "maximized" state.
If the surface is in a fullscreen state, this request has no direct effect. It may alter the state the surface is returned to when unmaximized unless overridden by the compositor.
method private virtual on_unset_maximized : [> `V4 | `V5 | `V6 ] t -> unitUnmaximize the window.
Unmaximize the surface.
After requesting that the surface should be unmaximized, the compositor will respond by emitting a configure event. Whether this actually un-maximizes the window is subject to compositor policies. If available and applicable, the compositor will include the window geometry dimensions the window had prior to being maximized in the configure event. The client must then update its content, drawing it in the configured state. The client must also acknowledge the configure when committing the new content (see ack_configure).
It is up to the compositor to position the surface after it was unmaximized; usually the position the surface had before maximizing, if applicable.
If the surface was already not maximized, the compositor will still emit a configure event without the "maximized" state.
If the surface is in a fullscreen state, this request has no direct effect. It may alter the state the surface is returned to when unmaximized unless overridden by the compositor.
method private virtual on_set_fullscreen : [> `V4 | `V5 | `V6 ] t ->
output:
([ `Wl_output ], [> {Imports}1.Wl_output.versions ], [ `Server ])
{Proxy}2.t
option ->
unitSet the window as fullscreen on an output.
Make the surface fullscreen.
After requesting that the surface should be fullscreened, the compositor will respond by emitting a configure event. Whether the client is actually put into a fullscreen state is subject to compositor policies. The client must also acknowledge the configure when committing the new content (see ack_configure).
The output passed by the request indicates the client's preference as to which display it should be set fullscreen on. If this value is NULL, it's up to the compositor to choose which display will be used to map this surface.
If the surface doesn't cover the whole output, the compositor will position the surface in the center of the output and compensate with with border fill covering the rest of the output. The content of the border fill is undefined, but should be assumed to be in some way that attempts to blend into the surrounding area (e.g. solid black).
If the fullscreened surface is not opaque, the compositor must make sure that other screen content not part of the same surface tree (made up of subsurfaces, popups or similarly coupled surfaces) are not visible below the fullscreened surface.
method private virtual on_unset_fullscreen : [> `V4 | `V5 | `V6 ] t -> unitUnset the window as fullscreen.
Make the surface no longer fullscreen.
After requesting that the surface should be unfullscreened, the compositor will respond by emitting a configure event. Whether this actually removes the fullscreen state of the client is subject to compositor policies.
Making a surface unfullscreen sets states for the surface based on the following: * the state(s) it may have had before becoming fullscreen * any state(s) decided by the compositor * any state(s) requested by the client while the surface was fullscreen
The compositor may include the previous window geometry dimensions in the configure event, if applicable.
The client must also acknowledge the configure when committing the new content (see ack_configure).
method private virtual on_set_minimized : [> `V4 | `V5 | `V6 ] t -> unitSet the window as minimized.
Request that the compositor minimize your surface. There is no way to know if the surface is currently minimized, nor is there any way to unset minimization on this surface.
If you are looking to throttle redrawing when minimized, please instead use the wl_surface.frame event for this, as this will also work with live previews on windows in Alt-Tab, Expose or similar compositor features.
method min_version : int32