Skip to content

Refactor preview sizing and fix PageUp/PageDown - #4723

Draft
DavidGBrett wants to merge 3 commits into
devfrom
fix-page-navigation-visible-rows
Draft

DavidGBrett wants to merge 3 commits into
devfrom
fix-page-navigation-visible-rows

Conversation

@DavidGBrett

@DavidGBrett DavidGBrett commented Oct 25, 2026 •

Copy link
Copy Markdown
Contributor

WIP
Follow-up for #4719
Fixes #4722

This currently contains two related pieces. They can still be split into separate PRs if that makes review easier.

Preview refactor

  • Use one shared preview minimum-height constant in result sizing and XAML.
  • Make InternalPreviewVisible the authoritative preview state.
  • Derive the result grid column span from the preview state.
  • Remove the redundant IsPreviewOn state and keep standalone preview behavior explicit.

PageUp/PageDown fix

  • Calculate the page step from the number of rows that can actually be displayed.
  • Account for the preview pane reducing available result height.
  • Keep refreshes and page navigation synchronized.

Testing

  • 40 focused preview and navigation tests passed.
  • dotnet build Flow.Launcher.Test\Flow.Launcher.Test.csproj --no-restore --nologo

@github-actions github-actions Bot added this to the 2.2.0 milestone Oct 25, 2026
@DavidGBrett DavidGBrett changed the title Use visible rows for page navigation Refactor preview sizing and fix PageUp/PageDown Oct 25, 2026
@DavidGBrett
DavidGBrett force-pushed the fix-page-navigation-visible-rows branch from 9339e97 to 048246e Compare October 25, 2026 22:01
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.

BUG: Page up/down is based only on MaxResultsToShow setting which doesn't always apply

1 participant