No Header Except When Minimized

3 posts, 1 answers
  1. Paul
    Paul avatar
    15 posts
    Member since:
    Jan 2012

    Posted 05 Jan 2015 Link to this post


    While trying to implement the OutlookBar as a container in Prism tutorial (, the headers do not appear as the tutorial shows. 

    I am following the first guide where it adds a header by adding a member, ItemHeader, to the view.  The OutlookBar is set with the DisplayProperty = "ItemHeader", but upon execution, the application does not show the header.  If the horizontal bar is dragged down, the items are minimized and can be read.  So, it appears that the header is set, but is not being displayed properly while not minimized.

    I'm assuming this is a simple binding error, but I'm not sure how to proceed.
  2. Answer
    Martin Ivanov
    Martin Ivanov avatar
    1444 posts

    Posted 08 Jan 2015 Link to this post

    Hello Paul,

    I tested the reported behavior and it seems that the DisplayMemberPath property of RadOutlookBar does not work in WPF and this is why the Headers of the items are not displayed. I logged an item in our feedback portal that relates to this issue. You can track the issue's status by following the feedback item. I also updated your Telerik points as a small sign of gratitude for reporting this behavior.

    As a workaround you can use an implicit style targeting RadOutlookBarItem instead of the DisplayMemberPath property. You can define the style in the xaml page (the view) where the RadOutlookBar control is defined.

    Here is an example in code:
        <Style TargetType="telerik:RadOutlookBarItem">
            <Setter Property="Header" Value="{Binding ItemHeader}" />

    I hope this information helps.


    Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.

  3. Paul
    Paul avatar
    15 posts
    Member since:
    Jan 2012

    Posted 08 Jan 2015 in reply to Martin Ivanov Link to this post

    Thanks for the reply and workaround!
Back to Top