gracefully kill windows #13

Closed
by weskerfoot opened 4 years ago · 1 comments
weskerfoot commented 4 years ago (Migrated from github.com)
Owner

Clients, usually those with multiple top-level windows, whose server connection must survive the deletion of some of their top-level windows, should include the atom WM_DELETE_WINDOW in the WM_PROTOCOLS property on each such window. They will receive a ClientMessage event as described above whose data[0] field is WM_DELETE_WINDOW.

Clients receiving a WM_DELETE_WINDOW message should behave as if the user selected "delete window" from a hypothetical menu. They should perform any confirmation dialog with the user and, if they decide to complete the deletion, should do the following:

Either change the window's state to Withdrawn (as described in section 4.1.4) or destroy the window
Destroy any internal state associated with the window 
> Clients, usually those with multiple top-level windows, whose server connection must survive the deletion of some of their top-level windows, should include the atom WM_DELETE_WINDOW in the WM_PROTOCOLS property on each such window. They will receive a ClientMessage event as described above whose data[0] field is WM_DELETE_WINDOW. > > Clients receiving a WM_DELETE_WINDOW message should behave as if the user selected "delete window" from a hypothetical menu. They should perform any confirmation dialog with the user and, if they decide to complete the deletion, should do the following: > > Either change the window's state to Withdrawn (as described in section 4.1.4) or destroy the window > Destroy any internal state associated with the window
weskerfoot commented 4 years ago (Migrated from github.com)
Poster
Owner
https://tronche.com/gui/x/xlib/ICC/client-to-window-manager/XGetWMNormalHints.html
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.