You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Ryan Dwyer b6058703fa Refactor destroy functions and save workspaces when there's no outputs ... This changes the destroy functions to the following: * output_begin_destroy * output_destroy * workspace_begin_destroy * workspace_destroy * container_begin_destroy * container_destroy * view_begin_destroy * view_destroy The terminology was `destroy` and `free`, and it has been changed to `begin_destroy` and `destroy` respectively. When the last output is disconnected, its workspaces will now be stashed in the root. Upon connection of a new output they will be restored. There is a new function `workspace_consider_destroy` which decides whether the given workspace should be destroyed or not (ie. empty and not visible). Calling container_begin_destroy will no longer automatically reap the parents. In some places we want to reap the parents and in some we don't, so this is left to the caller. container_reap_empty_recursive and container_reap_empty have been combined into one function and it will recurse up the tree.		6 years ago
..
arrange.c	Translate floating containers when a workspace is moved	6 years ago
container.c	Refactor destroy functions and save workspaces when there's no outputs	6 years ago
layout.c	Refactor destroy functions and save workspaces when there's no outputs	6 years ago
output.c	Refactor destroy functions and save workspaces when there's no outputs	6 years ago
root.c	Refactor destroy functions and save workspaces when there's no outputs	6 years ago
view.c	Refactor destroy functions and save workspaces when there's no outputs	6 years ago
workspace.c	Refactor destroy functions and save workspaces when there's no outputs	6 years ago