| Age | Commit message (Collapse) | Author |
|---|
|
`_container_destroy` emits a destroy event, and any listener for this
event should have access to the full container, not a half destroyed
one.
`_container_destroy` also destroys the swayc, so we have to grab a
reference to the sway_workspace so we can free it afterwards.
This also fixes a memory leak where the floating container wasn't freed.
Fixes #2092.
|
|
|
|
Introduced in 7c810dc344c28d1876c5ee158cb0806289d0f813
|
|
Only send frame done to visible views
|
|
Also don't accumulate empty damage
|
|
|
|
|
|
|
|
Reduce work duplication in keyboard and binding code
|
|
Fixes #2085.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The same shortcut algorithm is now used for keycodes,
raw keysyms, and translated keysyms. Pressed keysyms
are now stored in association with the keycodes that
generated them. Modifier keycodes (and associated
keysyms) are identified retroactively by the subsequent
change to the modifier flags.
|
|
|
|
|
|
Implement floating
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Attach sticky containers to new workspaces when switching
* Fire the close event *before* we start destroying the workspace to
prevent a crash
Because the sticky container now follows the visible workspace, this
simplifies the rendering and container_at logic.
|
|
|
|
|
