WindowTitle binding error with R3

4 posts, 0 answers
  1. PaulR
    PaulR avatar
    19 posts
    Member since:
    Jun 2016

    Posted 20 Sep 2016 Link to this post

    Hi,

    I'm seeing a new binding error in the Output window with 2016 R3 that was not there before:

    System.Windows.Data Warning: 4 : Cannot find source for binding with reference 'RelativeSource FindAncestor, AncestorType='Telerik.Windows.Controls.RadRibbonView', AncestorLevel='1''. BindingExpression:Path=IsHostedInRibbonWindow; DataItem=null; target element is 'WindowTitle' (Name='WindowTitle'); target property is 'NoTarget' (type 'Object')

     

    This is coming from the new MultiDataTrigger condition added to the WindowTitleStyle. It's also coming from the WindowTitle that exists in the RadRibbonWindowStyle control template, which does not have a RadRibbonView ancestor, as opposed to the one in the RadRibbonViewTemplate.

  2. Dinko
    Admin
    Dinko avatar
    439 posts

    Posted 23 Sep 2016 Link to this post

    Hi PaulR,

    Thank you for contacting us.

    We are aware of this warning. Our development team knew about it and it will be probably fixed in one of our next LIB (latest internal build released every week).

    Regards,
    Dinko
    Telerik by Progress
    Do you need help with upgrading your AJAX, WPF or WinForms project? Check the Telerik API Analyzer and share your thoughts.
  3. Hans
    Hans avatar
    1 posts
    Member since:
    Mar 2012

    Posted 30 Jan in reply to Dinko Link to this post

    Hi,

     

    In 2017 R1 (Office 2016 theme) the error is still there, is that correct? I get the error in the output window twice.

     

    Regards,

    Hans

     

  4. Evgenia
    Admin
    Evgenia avatar
    1437 posts

    Posted 02 Feb Link to this post

    Hello Hans,

    Unfortunately I was able to reproduce this Output binding error with our latest official binaries R1 2017 (NoXAML) when RadRibbonView is hosted in RadRibbonWindow with Title. I logged it in our Feedback portal where you can track its progress.
     
    I have also updated your Telerik points as a small appreciation for your cooperation. 
    Please excuse us for any inconvenience caused.

    Regards,
    Evgenia
    Telerik by Progress
    Want to extend the target reach of your WPF applications, leveraging iOS, Android, and UWP? Try UI for Xamarin, a suite of polished and feature-rich components for the Xamarin framework, which allow you to write beautiful native mobile apps using a single shared C# codebase.
Back to Top