Skip to content

Fix #15 (round 2): bind finding-pane visibility to explicit bool#19

Merged
aclinick merged 1 commit into
mainfrom
fix/15-pane-visibility-round2
Jun 4, 2026
Merged

Fix #15 (round 2): bind finding-pane visibility to explicit bool#19
aclinick merged 1 commit into
mainfrom
fix/15-pane-visibility-round2

Conversation

@aclinick

@aclinick aclinick commented Jun 4, 2026

Copy link
Copy Markdown
Owner

Round-1 fix in #17 made the close handler fire reliably, but the pane still didn't collapse because the NullToCollapsed function binding wasn't re-evaluating. This switches to an explicit IsFindingDetailVisible bool kept in sync via OnSelectedFindingChanged. Manually verified.

The Click handler from the previous commit fired correctly but the pane
still didn't collapse, because the visibility binding
`{x:Bind local:MainPage.NullToCollapsed(ViewModel.SelectedFinding)}`
wasn't re-evaluating reliably after the property cleared.

- New observable bool MainPageViewModel.IsFindingDetailVisible, kept in
  sync with SelectedFinding via a partial OnSelectedFindingChanged hook.
- Pane Visibility now binds to BoolToVisibility(IsFindingDetailVisible).
- Close handler also sets IsFindingDetailVisible = false explicitly.
- BtnCloseFinding bumped to 32x32 with bigger glyph for a reliable hit
  target.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@aclinick aclinick enabled auto-merge (squash) June 4, 2026 14:22
@aclinick aclinick merged commit 45ff0ff into main Jun 4, 2026
2 checks passed
@aclinick aclinick deleted the fix/15-pane-visibility-round2 branch June 4, 2026 14:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant