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
Relax conditions for converters #3433
Comments
Hmm, unsure about this one. Avalonia is asking you to convert I need to look into how/why WPF handles this, but my initial thought is that your converter is broken. |
Any decision? :-) |
Sorry, I've not had chance to look into it. Any idea where in the WPF codebase it handles |
no, sadly |
Just to check: what is |
|
Yeah, so I really think this is a bug in your code. I know that WPF handles it fine, but there's nothing to my knowledge that says that WPF should accept this, I expect it's a case of it working by accident. |
But can it at least gave a warning or something? Because currently it just does nothing so TextBlock is empty. |
Anyway warning is a different Q. Closing the issue since this is not a bug. |
Hmm yeah it should be outputting an error to the log. If that's not happening then that is a bug I think. |
There is a error/warning message on master. So I will wait until next release is out and then re-check again. |
MCVE
And usage:
In Avalonia this will not work due to
ImplicitConversions
restrictions inTryConvertImplicit
.In WPF the same converter works just fine.
Additional thoughts: if I have
int
property that bound to Text and it works I would expect that if my converter returns int it will work as well.The text was updated successfully, but these errors were encountered: