Forums Ultimate UI for WPF
Your Privacy Matters: We use our own and third-party cookies to improve your experience on our website. By continuing to use the website we understand that you accept their use. Cookie Policy
Close
Matt
250
A public appeal
posted

Bring some of the developers off XamRibbon and XamChart, and these largely pointless Caraosel controls, and let's clean up the bugs and issues with apparently established controls like XamDataGrid and XamEditors, there are issues with are present in the old forums from over six months ago that have still not been fixed, there are loads of issues in this forums which haven't even had an aknowledgement, compare this to Xceed and MSDN WPF and Infragistics seriously lacks behind, who signs off these projects as complete? You do have a basis for a good product if only you put a little more attention to them.

Some of my issues:

1) Cell resizing to fit content.. No other way than hardcoding pixels in declarative XAML, defeats point of WPF? CellWidth, CellMaxWidth, dont work with AutoFit and only accept double values rather than relative, WPF grid seems more powerful in this respect.
2) XamEditors are badly broke... See example code in xameditors forum
3) Databinding doesnt follow WPF principles , can't  dot into stuff, converters etc.. Why break the standard? Seem to need to use CellValuePresenter  on nearly all columns
4) Extensibility poor, workarounds presented seem dirty

 

Parents
  • 8576
    Offline posted
    Hi Matt -
     
    To answer your technical questions:
     
    1 - 'Cell resizing to fit content' -
    The way accomplish this is by setting a DataRecordCellAreaGridTemplate which provides the DataPresenter with a specific grid structure of your choice for it use when arranging cells within a RecordCellArea.  Here is an example:
     

          <igDP:XamDataPresenter x:Name="DP1" AutoFit="Treu" >

            <igDP:XamDataPresenter.FieldLayoutSettings>

              <igDP:FieldLayoutSettings>

                <igDP:FieldLayoutSettings.DataRecordCellAreaGridTemplate>

                  <ItemsPanelTemplate>

                    <Grid>

                      <Grid.ColumnDefinitions>

                        <ColumnDefinition Width="Auto"/>

                        <ColumnDefinition Width="Auto"/>

                        <ColumnDefinition Width="*"/>

                      </Grid.ColumnDefinitions>

                   </Grid>

                  </ItemsPanelTemplate>

                </igDP:FieldLayoutSettings.DataRecordCellAreaGridTemplate>

              </igDP:FieldLayoutSettings>

             

            </igDP:XamDataPresenter.FieldLayoutSettings>

          </igDP:XamDataPresenter>

     
    2 - 'XamEditors are badly broke' -
    Sandip from Infragistics has replied to this and suggested you use the 'n' mask character instead of the '#' mask character.  Does this solve the problem you were seeing?  If not, please elaborate.
     
    3 - 'Data Binding doesn't follow WPF principles' -
    We do indeed support and use WPF binding throughout the product.  I had responded to you on the binding issue in a separate post, but I will repeat it here for clarity:

    To bind a Field to a sub-property of a record's property, you would need to create and add an UnboundField defintion to the FieldLayout.Fields collection.  Here's an example of an UnboundField definition that binds to the DisplayName property of the record's Author property:

    <igDP:FieldLayout>

         <igDP:FieldLayout.Fields>

              <igDP:UnboundField Name="author_displayname" BindingPath="Author.DisplayName", BindingMode="TwoWay" DataType="sys:string"/>

         </igDP:FieldLayout.Fields>

    </igDP:FieldLayout>

    4 - 'Extensibility poor, workarounds presented seem dirty' -
    Can you provide some specific examples? 
     
     
     
    "matt83uk" wrote in message news:11768@forums.infragistics.com...

    Bring some of the developers off XamRibbon and XamChart, and these largely pointless Caraosel controls, and let's clean up the bugs and issues with apparently established controls like XamDataGrid and XamEditors, there are issues with are present in the old forums from over six months ago that have still not been fixed, there are loads of issues in this forums which haven't even had an aknowledgement, compare this to Xceed and MSDN WPF and Infragistics seriously lacks behind, who signs off these projects as complete? You do have a basis for a good product if only you put a little more attention to them.

    Some of my issues:

    1) Cell resizing to fit content.. No other way than hardcoding pixels in declarative XAML, defeats point of WPF? CellWidth, CellMaxWidth, dont work with AutoFit and only accept double values rather than relative, WPF grid seems more powerful in this respect.
    2) XamEditors are badly broke... See example code in xameditors forum
    3) Databinding doesnt follow WPF principles , can't  dot into stuff, converters etc.. Why break the standard? Seem to need to use CellValuePresenter  on nearly all columns
    4) Extensibility poor, workarounds presented seem dirty

     


    http://forums.infragistics.com/forums/p/1289/11768.aspx#11768

Reply Children
No Data