-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Can't bind to Uri
-path for Source
property
#7717
Comments
Source binding isn't supported, just like it isn't in wpf/uwp. |
@maxkatz6 Thank you very much for your answer! That's what I supposed. Is there a specific reason for that, which is not necessarily bound to difficulties in implementation or is exactly that the reason, which I doubt if it isn't supported in WPF and UWP either? And while we're at it, what would you propose as a better way to have a path that may change at runtime? A dynamic resource for example? |
Simply remove this and add new StyleInclude from the styles collection. It will work. |
Oh yes, that definitely makes sense. Just removing this entry from Thank you a lot! |
Describe the bug
I can't bind to a property of type
Uri
(not evenUri?
) for theSource
property of aStyleInclude
in this case. I get faced with this error upon building the application:I hope I'm not missing something too obvious, which is not unlikely to happen, considering my current state of concentration due to specific reasons, but I'm pretty sure this looks plausible. I'm not able to see where the issue lies.
The reason why I'm opening an issue for this, is that it might not look like expected behaviour at once and is possible to be an internal issue. It would also automatically be a proposal for a "feature" if it's not intended to bind for
Uri
sources.I thoroughly searched through previous issues and the internet in general, which didn't help me much.
To Reproduce
App.axaml:
App.axaml.cs:
Expected behavior
It should bind correctly and not throw this error.
Desktop (please complete the following information)
The text was updated successfully, but these errors were encountered: