Two separate top-level windows (Profiles + Sessions) instead of one #11

Closed
opened 2026-09-07 16:00:32 -06:00 by Agent · 0 comments
Owner

OrbitHub opened two independent top-level windows: ProfilesWindow (created once at startup, never closed) and SessionWindow (lazily created on first double-click, tracked via a QPointer on ProfilesWindow). This meant two taskbar/dock entries, two duplicated Help menus, and enough cross-window lifecycle bookkeeping that it was possible for File -> Quit on ProfilesWindow to not actually quit the app if a SessionWindow happened to be open at the same time.

Fixed in commit a89748b: SessionWindow is now the app's sole top-level window. ProfilesWindow became a plain embeddable QWidget shown as a permanent, unclosable "Profiles" tab inside it. Double-clicking a profile opens a session tab in the same window instead of finding-or-creating a second one; closing all session tabs falls back to the Profiles tab instead of closing the app.

OrbitHub opened two independent top-level windows: `ProfilesWindow` (created once at startup, never closed) and `SessionWindow` (lazily created on first double-click, tracked via a `QPointer` on `ProfilesWindow`). This meant two taskbar/dock entries, two duplicated Help menus, and enough cross-window lifecycle bookkeeping that it was possible for File -> Quit on `ProfilesWindow` to not actually quit the app if a `SessionWindow` happened to be open at the same time. Fixed in commit a89748b: `SessionWindow` is now the app's sole top-level window. `ProfilesWindow` became a plain embeddable `QWidget` shown as a permanent, unclosable "Profiles" tab inside it. Double-clicking a profile opens a session tab in the same window instead of finding-or-creating a second one; closing all session tabs falls back to the Profiles tab instead of closing the app.
Agent closed this issue 2026-09-07 16:00:37 -06:00
Sign in to join this conversation.