Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug title #1254

Open
zz62569 opened this issue Oct 17, 2024 · 0 comments
Open

Bug title #1254

zz62569 opened this issue Oct 17, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@zz62569
Copy link

zz62569 commented Oct 17, 2024

Describe the bug

Actually, when I'm calling NavigationView, the SelectedItem can't be accessed directly since it's protected. And when I try to use typeof with Navigate, it just shows the object as undefined. It feels really inconvenient, and the design kind of forces you to work with the structure they provided.

To Reproduce

Actually, when I'm calling NavigationView, the SelectedItem can't be accessed directly since it's protected. And when I try to use typeof with Navigate, it just shows the object as undefined. It feels really inconvenient, and the design kind of forces you to work with the structure they provided.

Expected behavior

Actually, when I'm calling NavigationView, the SelectedItem can't be accessed directly since it's protected. And when I try to use typeof with Navigate, it just shows the object as undefined. It feels really inconvenient, and the design kind of forces you to work with the structure they provided.

Screenshots

Actually, when I'm calling NavigationView, the SelectedItem can't be accessed directly since it's protected. And when I try to use typeof with Navigate, it just shows the object as undefined. It feels really inconvenient, and the design kind of forces you to work with the structure they provided.

OS version

Actually, when I'm calling NavigationView, the SelectedItem can't be accessed directly since it's protected. And when I try to use typeof with Navigate, it just shows the object as undefined. It feels really inconvenient, and the design kind of forces you to work with the structure they provided.

.NET version

Actually, when I'm calling NavigationView, the SelectedItem can't be accessed directly since it's protected. And when I try to use typeof with Navigate, it just shows the object as undefined. It feels really inconvenient, and the design kind of forces you to work with the structure they provided.

WPF-UI NuGet version

Actually, when I'm calling NavigationView, the SelectedItem can't be accessed directly since it's protected. And when I try to use typeof with Navigate, it just shows the object as undefined. It feels really inconvenient, and the design kind of forces you to work with the structure they provided.

Additional context

Actually, when I'm calling NavigationView, the SelectedItem can't be accessed directly since it's protected. And when I try to use typeof with Navigate, it just shows the object as undefined. It feels really inconvenient, and the design kind of forces you to work with the structure they provided.

@zz62569 zz62569 added the bug Something isn't working label Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant