Kristoffer
Top achievements
Rank 1
Rank 1
Kristoffer
asked on 05 Oct 2008, 02:16 PM
Hi.
I found something that might not be a bug, but took me some time to find the error in my code, because no error was thrown.
If the UniqueName of OrderId in the XAML below is changed from "OrderID" to "orderid" for instance, the expand-icon will appear on the row for a hierarchy, but when clicked no rows appears below. So it seems as if UniqueName is "half case sensitive".
I do not know if this should be corrected, or if this is proper behavior of the control, but I think that either the expand icon is shown and there is data below, OR no expand icon and no data below.
These are great controls, by the way.
Thanks.
I found something that might not be a bug, but took me some time to find the error in my code, because no error was thrown.
If the UniqueName of OrderId in the XAML below is changed from "OrderID" to "orderid" for instance, the expand-icon will appear on the row for a hierarchy, but when clicked no rows appears below. So it seems as if UniqueName is "half case sensitive".
I do not know if this should be corrected, or if this is proper behavior of the control, but I think that either the expand icon is shown and there is data below, OR no expand icon and no data below.
These are great controls, by the way.
Thanks.
| <telerik:RadGridView AutoGenerateColumns="False" Name="radGridView1" ShowGroupPanel="False"> |
| <telerik:RadGridView.Columns> |
| <telerik:GridViewDataColumn HeaderText="Order Number" UniqueName="OrderID" /> |
| <telerik:GridViewDataColumn HeaderText="Order Reference" UniqueName="OrderReference" /> |
| </telerik:RadGridView.Columns> |
| </telerik:RadGridView> |
1 Answer, 1 is accepted
0
Accepted
Hi Kristoffer,
We confirmed this behavior in our "Hierarchy/Autogenerated Hierarchy" example. We always use case-sensitive comparison with the UniqueName property. The problem is that we do not check if there is any data present for the child table before we build the UI hierarchy. This bug is now added to our bug-tracking system. We are very thankful both for your valuable feedback and for your kind words about our product. It would be a pleasure for us to discuss with you any other issues you encounter.
Your Telerik points have been updated for your involvement.
Best wishes,
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
We confirmed this behavior in our "Hierarchy/Autogenerated Hierarchy" example. We always use case-sensitive comparison with the UniqueName property. The problem is that we do not check if there is any data present for the child table before we build the UI hierarchy. This bug is now added to our bug-tracking system. We are very thankful both for your valuable feedback and for your kind words about our product. It would be a pleasure for us to discuss with you any other issues you encounter.
Your Telerik points have been updated for your involvement.
Best wishes,
Dimitar Dobrev,
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.