What happens if you init isShowingBrowser to false?

They eventually added iOS Support and I used it for a bunch of apps. But the UIKit based system made it harder and harder to achieve a modern UI. Lots of limitations. So it was time to go.

Last year, at age 73, I decided to switch my hobby programming to Swift/SwiftUI from XOJO. I waited for SwiftUI to mature as UIKit made my eyes glaze over. After about 6 months of grinding, I successfully converted one of my XOJO apps. I now know there's a few things I did sub-optimally, so I'm continuing to learn. Jump in, the water's fine.

It's become obvious to me that I should stop fighting the system and just rethink my approach.

Thanks for the suggestions. As I mentioned above, I'm trying to persist the same detail view when navigating, and not replace it. The only way I found to do this was to use NavigationLink with .isDetailLink(false). But when using a NavigationPath approach, NavigationLinks push the view onto the stack but the view doesn't appear. If I then push another view using the router(which does appear) and navigate back, then the view I pushed with the NavigationLink is revealed. // Destination view does not appear but is pushed to stack NavigationLink( destination: { BasicDataView(citizen: "johndoe") .navigationBarBackButtonHidden(true) }, label: { Text("Character Generation") } ) .isDetailLink(false) // Keep in sidebar // Works correctly but replaces entire content, or if pushed view uses NavigationSplitView then replaces the detail view which is not desirable Button(action: { router.push(route: .basicdata(citizen: "johndoe")) }) { Text("Character Generation") }