4 posts, 0 answers
  1. Jim
    Jim avatar
    1 posts
    Member since:
    Jun 2009

    Posted 24 Jun 2009 Link to this post

    I am placing a RadExpander on a WPF window and set the IsExapnded property to False so when the window is loaded it (the expander) should display closed initially.

    I'm using a MVVM pattern so I initially thought that something was wrong with the binding, but after explicitly setting the IsExpanded="False" on the RadExpander control in the xaml I recieved the same result with the window opening with the expander open instead of closed.  I even went as far as coding in the code behind of the window loaded event handler to set the IsExpanded = False.  This didn't work either.

    The odd thing is the toggle thinks the expander is closed, but the content area is open.  so you have to toggle open and then closed and the functionality of the control starts to work.

    Here is the code:



    telerik:RadExpander x:Name="ValidationExpander" BorderBrush="#888888" BorderThickness="1" Background="#EEEEEE"          
    ="False" MinWidth="500" Canvas.Bottom="0" ExpandDirection="Up" Canvas.Left="0">








              <TextBlock x:Name="expanderCaption" Foreground="#000000" Visibility="Visible" />












                  <local:MessageBoxControl DataContext="{Binding MessageBoxViewModel, UpdateSourceTrigger=PropertyChanged}"











  2. Ivan
    Ivan avatar
    519 posts

    Posted 25 Jun 2009 Link to this post

    Hi Jim,

    Thank you for your interest in the RadExpander control.

    We confirm this is an issue with the WPF version of the RadExpander in our last release (2009-Q1)  and in order to workaround it you should toggle the IsExpanded to true and then to false.

    This issue is already addressed and the fix will be available in the upcoming Q2 release.

    Because of reporting the issue and sharing the workaround we updated your Telerik points.

    Best wishes,
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Check out the tips for optimizing your support resource searches.
  3. UI for WPF is Visual Studio 2017 Ready
  4. AJ
    AJ avatar
    8 posts
    Member since:
    Oct 2010

    Posted 09 Nov 2010 Link to this post

    Has this been fixed yet. I am having the same issue on a project I am working on
     and I have the latest release.

  5. Viktor Tsvetkov
    Viktor Tsvetkov avatar
    382 posts

    Posted 10 Nov 2010 Link to this post

    Hi Arie,

    I cannot get such behavior. Could you please examine the attached sample project and if you have further questions do not hesitate to ask?

    All the best,
    Viktor Tsvetkov
    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
Back to Top