Horizontally Sliced TreeMap

4 posts, 0 answers
  1. Jacob
    Jacob avatar
    2 posts
    Member since:
    Jun 2014

    Posted 21 Aug 2014 Link to this post

    I am using a horizontally sliced TreeMap. Is it possible to control the VERTICAL distance (Y-Direction)?  I understand the horizontal distance is determined by the values (X-Direction).  

    Ideally, the space would be equidistant vertically with all 3 groups having the same vertical distance.  Similar to a Grid with 3 RowDefinitions where Height="*"

    Current XAML:
    01.<telerik:RadTreeMap x:Name="TreeMap"  Grid.Row="0" Grid.Column="2"
    02.  ClipToBounds="True" >
    03. 
    04.     <telerik:RadTreeMap.LayoutStrategy>
    05.          <telerik:SliceDiceStrategy Orientation="Horizontal" />
    06.     </telerik:RadTreeMap.LayoutStrategy>
    07. 
    08.     <telerik:RadTreeMap.TypeDefinitions>
    09.           <telerik:TypeDefinition TargetTypeName="ModelInfo"
    10.              ValuePath="Value" ChildrenPath="Children" LabelPath="Name"
    11.              ItemStyle="{StaticResource IcicleStyle}" />
    12. 
    13.            <telerik:TypeDefinition TargetTypeName="GroupInfo"
    14.              ValuePath="Value" ChildrenPath="Children" LabelPath="Name"
    15.              ItemStyle="{StaticResource IcicleStyle}" />
    16. 
    17.            <telerik:TypeDefinition TargetTypeName="EventInfo"
    18.              ValuePath="Value" LabelPath="Name"
    19.              ItemStyle="{StaticResource IcicleStyle}" />
    20. 
    21.      </telerik:RadTreeMap.TypeDefinitions>
    22. 
    23.</telerik:RadTreeMap>

    StaticResource IcicleStyle:

    1.<Style x:Key="IcicleStyle" TargetType="telerik:RadTreeMapItem" >
    2.    <Setter Property="Control.Background" Value="White" />
    3.    <Setter Property="MaxHeight" Value="50" />
    4.    <Setter Property="FontFamily" Value="Segoe UI" />
    5.    <Setter Property="FontWeight" Value="SemiBold" />
    6.    <Setter Property="Margin" Value="-1" />
    7.    <Setter Property="Padding" Value="0" />
    8.</Style>


    A screenshot of the current layout is attached.  If you look at the last section labelled "S", Ideally,  (S.Height === %G1.Height).  Even if I remove the third level of data {1,2,3,4}, the result is the same.

    Any help is appreciated.

    Thanks,
    Jacob
  2. Petar Marchev
    Admin
    Petar Marchev avatar
    968 posts

    Posted 22 Aug 2014 Link to this post

    Hi Jacob,

    Thank you for attaching a snapshot of the current result, but can you please attach an image(a drawing of some sort) of the desired output?

    Regards,
    Petar Marchev
    Telerik
     
    Check out Telerik Analytics, the service which allows developers to discover app usage patterns, analyze user data, log exceptions, solve problems and profile application performance at run time. Watch the videos and start improving your app based on facts, not hunches.
     
  3. UI for WPF is Visual Studio 2017 Ready
  4. Jacob
    Jacob avatar
    2 posts
    Member since:
    Jun 2014

    Posted 22 Aug 2014 in reply to Petar Marchev Link to this post

    Hello Petar,

    Thank you for the quick reply. I realize my explanation was confusing, sorry.

    I have attached a screenshot of the desired output.  In this screenshot, the height of each row (Y) is the same.  The X-Direction would be calculated by the Value of each cell.
  5. Petar Marchev
    Admin
    Petar Marchev avatar
    968 posts

    Posted 27 Aug 2014 Link to this post

    Hi Jacob,

    Thank you for the additional information. The treemap does not have such a functionality built-in and I think it will be a difficult task to try and implement it in you project. Perhaps you can use a custom solution for this, using Grids as you mentioned earlier.

    Regards,
    Petar Marchev
    Telerik
     
    Check out Telerik Analytics, the service which allows developers to discover app usage patterns, analyze user data, log exceptions, solve problems and profile application performance at run time. Watch the videos and start improving your app based on facts, not hunches.
     
Back to Top