You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
windows-reactor: SplitView.display_mode() compiles but never reaches WinUI #4837
SplitView exposes a .display_mode(SplitViewDisplayMode::…) builder and the WinUI backend already implements Prop::DisplayMode -> ISplitView::SetDisplayMode, but the generated bindings never emit that prop. Calling .display_mode() updates only the Rust struct,WinUI always keeps the default Inline mode.The official sample uses .display_mode(SplitViewDisplayMode::Inline), which matches the WinUI default, so the sample appears to work while the API is effectively broken for every other mode (Overlay, CompactOverlay, CompactInline).
use windows_reactor::*;fnapp(_cx:&mutRenderCx) -> Element{split_view(border(text_block("Main content area.\n\ In Overlay mode this should stay full width\n\ and the pane should float on top.\n\ Instead it behaves like Inline (content is pushed aside).",).padding(16.0),).background(Color::rgb(40,40,40)),).pane(border(vstack((text_block("Pane content").bold(),text_block("display_mode(Overlay) is ignored"),text_block("WinUI stays in default Inline mode"),)).spacing(8.0).padding(16.0),).background(Color::rgb(0,90,158)),).display_mode(SplitViewDisplayMode::Overlay).is_pane_open(true).open_pane_length(260.0).into()}fnmain() -> windows_core::Result<()>{bootstrap()?;App::new().title("SplitView display_mode repro").size(900.0,500.0).render(app)}
Activity
kennykerr commentedon Aug 18, 2026
Thanks for the report - working on an update that will prevent such quiet failures from compiling - hopefully have an update out soon.
kennykerr commentedon Aug 27, 2026
As of #4848,
SplitView::display_modeis included in the generated property path and reaches WinUI correctly.