-
Notifications
You must be signed in to change notification settings - Fork 146
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
Binding errors when using ComboBox #18
Comments
I cannot reproduce this behavior with ComboBoxes but I get similar output for TabControls. I found this blog post stating that they are harmless and handled internally. It seems the error can occur for all controls that contain dynamically created lists. To resolve the binding errors you could try to explicitly set the watermark to |
Oh wait I just noticed that you received BindingError 40 and I get BindingError 4. My answer was supposed to target BindingError 4. I will do some research again but as I cannot reproduce it, it will be hard to tackle. |
I created a small application where I tried to recreate your setup and finally got the errors as well. Writing <DataTrigger Binding="{Binding Path=(adonisExtensions:WatermarkExtension.IsWatermarkVisible)}"/> instead of <DataTrigger Binding="{Binding (adonisExtensions:WatermarkExtension.IsWatermarkVisible)}"/> fixed it for me. Please reopen in case the errors are still present in your application. |
I noticed, that the application output is filled with messages, that a BindingExpression path error occured, when using a ComboBox:
These two errors occur for every ComboBox in my view.
I'm using the latest version of AdonisUI (1.9), I haven't noticed this with earlier versions but I have not tested it specifically with other versions of AdonisUI.
This is the view, the error occurs, the following code snippet is the ComboBox in the view:
The view for an installer bundle consists of only a single TextBox:
There seems to be no error while using the application, I just wanted to check, if the errors can be ignored.
The text was updated successfully, but these errors were encountered: