Create a new WPF project, add a RadDocking to the page, then add a DocumentHost to the RadDocking, like so:
Run the app in debug mode and you'll get the following error in the VIsual Studio output window:
System.Windows.Data Error: 4 : Cannot find source for binding with reference 'ElementName=DropDownButtonElement'. BindingExpression:Path=IsChecked; DataItem=null; target element is 'DropDownMenu' (Name='DropDownMenuElement'); target property is 'IsOpen' (type 'Boolean')
Using version 2011.1.419.40. Noticed that there was a similar problem with the RadTabControl (see http://www.telerik.com/community/forums/wpf/tabcontrol/strange-error-message-in-debug-view.aspx). Can't reproduct the same error with RadTabControl. Suspect this is a similar issue. Doesn't cause any problems but would be nice to remove the error.
Can can anyone else confirm this?
<telerik:RadDocking HasDocumentHost="True"> <telerik:RadDocking.DocumentHost> <telerik:RadSplitContainer> <telerik:RadPaneGroup> <telerik:RadDocumentPane Header="Document 1" Title="Document 1" /> </telerik:RadPaneGroup> </telerik:RadSplitContainer> </telerik:RadDocking.DocumentHost> </telerik:RadDocking>
Run the app in debug mode and you'll get the following error in the VIsual Studio output window:
System.Windows.Data Error: 4 : Cannot find source for binding with reference 'ElementName=DropDownButtonElement'. BindingExpression:Path=IsChecked; DataItem=null; target element is 'DropDownMenu' (Name='DropDownMenuElement'); target property is 'IsOpen' (type 'Boolean')
Using version 2011.1.419.40. Noticed that there was a similar problem with the RadTabControl (see http://www.telerik.com/community/forums/wpf/tabcontrol/strange-error-message-in-debug-view.aspx). Can't reproduct the same error with RadTabControl. Suspect this is a similar issue. Doesn't cause any problems but would be nice to remove the error.
Can can anyone else confirm this?
7 Answers, 1 is accepted
0
Accepted
Hello Sean,
We were able to reproduce this issue, I've logged it in our public issue tracking system and it will be fixed. You can track its progress here.
As a small token of gratitude for your involvement, I've updated your points.
Greetings,
Yana
the Telerik team
We were able to reproduce this issue, I've logged it in our public issue tracking system and it will be fixed. You can track its progress here.
As a small token of gratitude for your involvement, I've updated your points.
Greetings,
Yana
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items
0
Kristoffer
Top achievements
Rank 1
answered on 05 Dec 2012, 12:47 PM
I'm running the latest build of RadControls, and I also get this warning in the Debug window.
System.Windows.Data Warning: 4 : Cannot find source for binding with reference 'ElementName=DropDownButtonElement'. BindingExpression:Path=IsChecked; DataItem=null; target element is 'DropDownMenu' (Name='DropDownMenuElement'); target property is 'IsOpen' (type 'Boolean')
Wasn't this fixed?
System.Windows.Data Warning: 4 : Cannot find source for binding with reference 'ElementName=DropDownButtonElement'. BindingExpression:Path=IsChecked; DataItem=null; target element is 'DropDownMenu' (Name='DropDownMenuElement'); target property is 'IsOpen' (type 'Boolean')
Wasn't this fixed?
0
Hi Kristoffer,
This issue is not fixed yet. I would suggest to track the PITS item in order to get notified when it is resolved.
Kind regards,
Yana
the Telerik team
This issue is not fixed yet. I would suggest to track the PITS item in order to get notified when it is resolved.
Kind regards,
Yana
the Telerik team
Explore the entire Telerik portfolio by downloading Telerik DevCraft Ultimate.
0
Amer
Top achievements
Rank 1
answered on 16 Oct 2013, 07:29 PM
Hi,
I'm new here and this is my first post , so I'd like to start by saying "a BIG Thank you" to all of Telerik team for your great work , I really love your components :)
Now back to the main thread issue, I know this is not critical and it is just a warning and can be safely ignored, but it is strange that it is still exists in the latest version "2013 Q3" ..
I'm new here and this is my first post , so I'd like to start by saying "a BIG Thank you" to all of Telerik team for your great work , I really love your components :)
Now back to the main thread issue, I know this is not critical and it is just a warning and can be safely ignored, but it is strange that it is still exists in the latest version "2013 Q3" ..
0
Hi Amer,
Thank you for the nice words.
Indeed, the fix wasn't included in Q3 2013 release, we will do our best to fix it for some of the upcoming internal builds.
We're sorry for any inconvenience caused.
Regards,
Yana
Telerik
Thank you for the nice words.
Indeed, the fix wasn't included in Q3 2013 release, we will do our best to fix it for some of the upcoming internal builds.
We're sorry for any inconvenience caused.
Regards,
Yana
Telerik
TRY TELERIK'S NEWEST PRODUCT - EQATEC APPLICATION ANALYTICS for WPF.
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>
0
Kristoffer
Top achievements
Rank 1
answered on 30 Jan 2014, 12:08 PM
Just like car enthusiasts want their car paint scratch free, software enthusiasts want their code free of warnings. Please fix this annoyance now!
This minor issue actually becomes quite expensive in the long run. When our developers see this warning they go 'Wait, what's that?!' - losing their concentration for a minute. So far, this annoyance has cost us $1800. (2011-2014, roughly two years with approximately 225 days per year. Four developers with a minute price of $1: 2*225*4*1=1800)
You get my point :)
This minor issue actually becomes quite expensive in the long run. When our developers see this warning they go 'Wait, what's that?!' - losing their concentration for a minute. So far, this annoyance has cost us $1800. (2011-2014, roughly two years with approximately 225 days per year. Four developers with a minute price of $1: 2*225*4*1=1800)
You get my point :)
0
Hello Kristoffer,
I understand and I'd like once again to apologize for the caused troubles.
We have moved the item into our new Telerik UI for WPF Feedback Portal, here is the link:
http://feedback.telerik.com/Project/143/Feedback/Details/113135-raddocking-with-documenthost-shows-a-binding-error-in-the-vs-output-window
and I have raised its priority as well.
Regards,
Yana
Telerik
I understand and I'd like once again to apologize for the caused troubles.
We have moved the item into our new Telerik UI for WPF Feedback Portal, here is the link:
http://feedback.telerik.com/Project/143/Feedback/Details/113135-raddocking-with-documenthost-shows-a-binding-error-in-the-vs-output-window
and I have raised its priority as well.
Regards,
Yana
Telerik
TRY TELERIK'S NEWEST PRODUCT - EQATEC APPLICATION ANALYTICS for WPF.
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>