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
335
Looping through hierarchical UltraGrid
posted

Hello,

I have a question again regarding a hierarchical dataset as datasource for my ultragrid. I have on every level a checkbox column in the header and therefore in every row. This is for checking or unchecking the row for later processing later on. Unfortunately this header checkbox is only working for the level it is on, that means if I check it, it doesn't check the child rows automatically. Thus I manually programmed this functionality but it has bad performance for a higher amount of datarows. I my current test example I have 1500 rows on the first level and multiple bands which are holding lots of childrows, one of em even about 8000-12000 rows. I also need to set a headercheckbox to indeterminate if at least one datarow in the lower childlevels is not checked. And here is my problem, because therefore I have to iterate through ALL rows and have to look if it is checked. Currently I'm doing this with the example code of this:

http://help.infragistics.com/Help/NetAdvantage/WinForms/2011.1/CLR2.0/html/Infragistics2.Win.UltraWinGrid.v11.1~Infragistics.Win.UltraWinGrid.UltraGridRow~ChildBands.html

That takes in my example (I have single core 64bit, 2ghz, 32bit winxp, 2gb ram) almost one minute.

my question is, do you think this is normal with that mass of datarows or do you have any idea too make things differently?

here is my part of code:

    Protected Function IsEveryRowChecked(ByVal Rows As RowsCollection) As Boolean

        For Each Row As UltraGridRow In Rows
            If DirectCast(Row.Cells("check").Value, Boolean) Then
                If Not Row.ChildBands Is Nothing Then
                    For Each ChildsChildBand As UltraGridChildBand In Row.ChildBands
                        If Not IsEveryRowChecked(ChildsChildBand.Rows) Then
                            Return False
                        End If
                    Next
                End If
            Else
                Return False
            End If
        Next
        Return True


    End Function

 

Greetings,

Renelope

 

Parents
No Data
Reply
  • 469350
    Offline posted

    Hi Renelope,

    I took a look at the link you posted and that code is out of date. There's actually a much easier way to loop through every row in the grid, now:


            For Each Row As UltraGridRow In Me.UltraGrid1.Rows.GetAllNonGroupByRows()
                ' Do somehting to the row
            Next

    This will loop through all of the data rows in the grid that are not GroupByRows. There are other methods on the Rows collection to get enumerators like this, depending on what you want. For example, you might want to use GetFilteredInNonGroupByRows if you want to ignore rows that have been filtered out.

    Anyway... I doubt that has anything to do with the performance issue you are experiencing.

    Regarding performance, my guess is that the major part of the performance hit is not coming from the grid, it's coming from the data source. Asking the DataSet for the child rows of any particular parent row can be a very expensive operation. This makes sense if you think about it, because let's say, for example, you have a DataSet with 2 tables and a Relationship between those tables. Let's further assume that your child table has a total of 10,000 row in it.  When you ask for the child rows for any individual parent row, the DataSet has to loop through all 10,000 child rows and evaluate each one. And then when you ask for the child rows of another parent, it has to loop through all 10,000 rows again.

    If that is the case, then there's not much you can do. You could use some other data source, of course, but there will always be a hit somewhere as you load the data and link up the parent and child rows.

    There are certain things you can do to make the grid code more efficient. For example, you can save a lot of memory by not forcing the grid to create cell objects. This is described in detail in the WinGrid Performance Guide.

    If you can post the code you are using that actually accesses the grid rows and cells so I can see what you are doing there, I might be able to offer you some other suggestions about improving that code. But if I am right about the DataSource, then the efficiency of the grid code probably won't make much of a dent.

Children