I am using the 2008 Q3 1314 version. I have two questions/issues:
First, I have a problem where the very first row of my RadGrid (that has 4 rows of data, for example) does not initially display any values when using GridDropDownColumn columns. After editing that first row and canceling changes, the row properly displays values. Is it true that this was fixed in a later version?
For this first problem, it only happens when I use a GridDropDownColumnEditor tag. So I ask again, has this been fixed in a more recent version?
Second, if this RadGrid is initially empty (zero rows) and I attempt to insert the first row, the GridDropDownColumn columns (which use RadComboBox) are all empty. This is not the case if I attempt to insert a new row in this RadGrid that has pre-existing rows. In that case, the RadComboBoxes all show the appropriate list of selections. I know that, in either case, the ListDataMember tables are available and populated in the data source. Is this also something that has been fixed in a later release, or am I not considering something.
I found the second problem and fixed the bug.
Thanks
Frank
First, I have a problem where the very first row of my RadGrid (that has 4 rows of data, for example) does not initially display any values when using GridDropDownColumn columns. After editing that first row and canceling changes, the row properly displays values. Is it true that this was fixed in a later version?
For this first problem, it only happens when I use a GridDropDownColumnEditor tag. So I ask again, has this been fixed in a more recent version?
Second, if this RadGrid is initially empty (zero rows) and I attempt to insert the first row, the GridDropDownColumn columns (which use RadComboBox) are all empty. This is not the case if I attempt to insert a new row in this RadGrid that has pre-existing rows. In that case, the RadComboBoxes all show the appropriate list of selections. I know that, in either case, the ListDataMember tables are available and populated in the data source. Is this also something that has been fixed in a later release, or am I not considering something.
I found the second problem and fixed the bug.
Thanks
Frank