Phosphor
Qt6 / Wayland library suite for window-management tools
Loading...
Searching...
No Matches
PhosphorScrollEngine::StashedColumn Struct Reference

#include <PhosphorScrollEngine/ScrollStashTypes.h>

Public Attributes

QVector< StashedTile > tiles
ColumnWidth width
ColumnDisplay display = ColumnDisplay::Normal
QString activeWindowId
 The column's ACTIVE tile, by window id — for a Tabbed column that is the shown tab.
QString heightOwnerId
 Which tab owns a TABBED column's cross extent, by window id.
bool maximizedToEdges = false
 The column's maximize-to-edges state (Column::maximizedToEdges).
bool shownTabRestored = false
 Latched once activeWindowId above has actually been put in force on the live column, and once heightOwnerId has.
bool heightOwnerRestored = false
bool arrivesAsMove = false
 Recorded by ScrollEngine::stashColumnForDesktopMove for a column moved here from another desktop, rather than captured from this context's own strip.

Member Data Documentation

◆ activeWindowId

QString PhosphorScrollEngine::StashedColumn::activeWindowId

The column's ACTIVE tile, by window id — for a Tabbed column that is the shown tab.

Carried because every insert makes the arriving tile its column's active one, so a restore without it shows whichever sibling happened to announce last.

◆ arrivesAsMove

bool PhosphorScrollEngine::StashedColumn::arrivesAsMove = false

Recorded by ScrollEngine::stashColumnForDesktopMove for a column moved here from another desktop, rather than captured from this context's own strip.

Its index among the entry's columns says nothing about where it belongs on a strip it never stood in, so its first arrival opens the column where a fresh arrival would (the screen's insert position) instead of at that index. Later arrivals join it through the ordinary sibling lookup.

Also what marks the column as a move RECORD rather than this context's own structure: an arrival somewhere else takes the window's tile out of it (ScrollEngine::forgetMovedColumnsElsewhere), because the move it records did not land.

Persisted, unlike the two latches above, so both answers survive a daemon restart that keeps the window ids: a move still pending at the restart opens where a fresh arrival would, and is still given up by an arrival elsewhere.

◆ display

ColumnDisplay PhosphorScrollEngine::StashedColumn::display = ColumnDisplay::Normal

◆ heightOwnerId

QString PhosphorScrollEngine::StashedColumn::heightOwnerId

Which tab owns a TABBED column's cross extent, by window id.

Carried for the same reason it is persisted to disk: the tabs that do not own it keep their own heights, so a restore without it falls back to the first non-Auto tab and can hand the column to a different one than held it. Distinct from activeWindowId on purpose — the shown tab and the sizing owner are allowed to differ, which is what keeps a tab switch from resizing the column.

◆ heightOwnerRestored

bool PhosphorScrollEngine::StashedColumn::heightOwnerRestored = false

◆ maximizedToEdges

bool PhosphorScrollEngine::StashedColumn::maximizedToEdges = false

The column's maximize-to-edges state (Column::maximizedToEdges).

Column presentation like width and display, so it rides the stash and is re-applied when the column is rebuilt on claim.

◆ shownTabRestored

bool PhosphorScrollEngine::StashedColumn::shownTabRestored = false

Latched once activeWindowId above has actually been put in force on the live column, and once heightOwnerId has.

Per COLUMN, unlike the strip- wide focus guard the restore derives from the consumed set: the two questions are answered at different arrivals (the shown tab may be a different tile from the extent owner, and either may still be absent when the first sibling lands), and a strip-wide latch would stop the re-assertion for every other column in the same burst.

While a latch is clear the restore keeps re-asserting the stashed value on each arrival, because every insert makes the arriving tile its column's active one and a non-Auto height claims the extent. Once it is set the restore hands back what the column held immediately BEFORE the insert instead: within a burst that is the value just restored, and for an arrival that lands long afterwards (a same-app window claiming a slot hours later) it is the tab the user has since switched to, which the stashed value must not rewind.

In-memory only. Deliberately not serialized: a stash staged from the persisted blob has restored nothing yet, so false is the right value on the far side of a restart.

◆ tiles

QVector<StashedTile> PhosphorScrollEngine::StashedColumn::tiles

◆ width

ColumnWidth PhosphorScrollEngine::StashedColumn::width

The documentation for this struct was generated from the following file: