COSMIC toplevel info

This request indicates that the client no longer wishes to receive events for new toplevels. However, the compositor may emit further toplevel_created events until the finished event is emitted.

The client must not send any more requests after this one.

Note: This request isn't necessary for clients binding version 2 of this protocol and will be ignored.

Request a zcosmic_toplevel_handle_v1 extension object for an existing ext_foreign_toplevel_handle_v1.

All initial properties of the toplevel (states, etc.) will be sent immediately after this event via the corresponding events in zcosmic_toplevel_handle_v1.

This event is never emitted for clients binding version 2 of this protocol, they should use `get_cosmic_toplevel` instead.

This event is emitted for clients binding version 1 whenever a new toplevel window is created. It is emitted for all toplevels, regardless of the app that has created them.

All initial properties of the toplevel (title, app_id, states, etc.) will be sent immediately after this event via the corresponding events in zcosmic_toplevel_handle_v1.

This event indicates that the compositor is done sending events to the zcosmic_toplevel_info_v1. The server will destroy the object immediately after sending this request, so it will become invalid and the client should free any resources associated with it.

Note: This event is emitted immediately after calling `stop` for clients binding version 2 of this protocol for backwards compatibility.

This event is sent after all changes for currently active zcosmic_toplevel_handle_v1 have been sent.

This allows changes to multiple zcosmic_toplevel_handle_v1 handles and their properties to be seen as atomic, even if they happen via multiple events.

This request should be called either when the client will no longer use the zcosmic_toplevel_handle_v1.

The server will emit no further events on the zcosmic_toplevel_handle_v1 after this event. Any requests received aside from the destroy request will be ignored. Upon receiving this event, the client should make the destroy request to allow freeing of resources.

Note: This event will not be emitted for clients binding version 2 of this protocol, as `ext_foreign_toplevel_handle_v1.closed` is equivalent.

This event is sent after all changes in the toplevel state have been sent.

This allows changes to the zcosmic_toplevel_handle_v1 properties to be seen as atomic, even if they happen via multiple events.

Note: this is is not sent after the closed event.

Note: This event will not be emitted for clients binding version 2 of this protocol, as `ext_foreign_toplevel_handle_v1.done` is equivalent.

This event is emitted whenever the title of the toplevel changes.

Note: This event will not be emitted for clients binding version 2 of this protocol, as `ext_foreign_toplevel_handle_v1.title` is equivalent.

This event is emitted whenever the app_id of the toplevel changes.

Note: This event will not be emitted for clients binding version 2 of this protocol, as `ext_foreign_toplevel_handle_v1.app_id` is equivalent.

This event is emitted whenever the toplevel becomes visible on the given output. A toplevel may be visible on multiple outputs.

This event is emitted whenever the toplevel is no longer visible on a given output. It is guaranteed that an output_enter event with the same output has been emitted before this event.

This event is emitted whenever the toplevel becomes visible on the given workspace. A toplevel may be visible on multiple workspaces.

This event is emitted whenever the toplevel is no longer visible on a given workspace. It is guaranteed that an workspace_enter event with the same workspace has been emitted before this event.

This event is emitted once on creation of the zcosmic_toplevel_handle_v1 and again whenever the state of the toplevel changes.

Emitted when the geometry of a toplevel (it's position and/or size) relative to the provided output has changed.

This event is emitted once on creation of the zcosmic_toplevel_handle_v1 for every entered output and again whenever the geometry of the toplevel changes relative to any output.

This event is emitted whenever the toplevel becomes visible on the given workspace. A toplevel may be visible on multiple workspaces.

This event is emitted whenever the toplevel is no longer visible on a given workspace. It is guaranteed that an workspace_enter event with the same workspace has been emitted before this event.

The different states that a toplevel may have. These have the same meaning as the states with the same names defined in xdg-toplevel