Skip to content

Do not persist status line visibility under the perspective bar key - #4281

Open
vogella wants to merge 1 commit into
eclipse-platform:masterfrom
vogella:statusline-visible-wrong-key
Open

Do not persist status line visibility under the perspective bar key#4281
vogella wants to merge 1 commit into
eclipse-platform:masterfrom
vogella:statusline-visible-wrong-key

Conversation

@vogella

@vogella vogella commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

WorkbenchWindow.setStatusLineVisible stored its value in the window's persisted state under the perspectiveBarVisible key. An RCP application calling WorkbenchWindowConfigurer.setShowStatusLine(false) therefore silently changed the perspective bar state for that window on the next start.

Nothing ever reads a status line key back, and the Window > Appearance > Hide Status Bar command persists its state through MUIElement.visible on the status trim, so the write is dropped rather than replaced by a new key. The Javadoc of the two accessors was copied from the perspective bar methods and is corrected as well.

The wrong key dates back to 8a8be4d (Bug 403461).

setStatusLineVisible wrote the perspectiveBarVisible entry into the
window's persisted state, so hiding the status line via
WorkbenchWindowConfigurer.setShowStatusLine changed the perspective bar
state on the next start. Nothing reads back a status line key, and the
Hide Status Bar command persists through MUIElement.visible, so drop the
write instead of adding a key. Also corrects the copy-pasted Javadoc.

Introduced by 8a8be4d (Bug 403461 - Allow toggling toolbar on
per-window basis).
@github-actions

Copy link
Copy Markdown
Contributor

Test Results

   858 files  ±0     858 suites  ±0   54m 50s ⏱️ - 2m 54s
 8 174 tests ±0   7 931 ✅ ±0  243 💤 ±0  0 ❌ ±0 
20 424 runs  ±0  19 768 ✅ ±0  656 💤 ±0  0 ❌ ±0 

Results for commit 0d07238. ± Comparison against base commit f0ef795.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant