This is the version I see we are using: 10.3.20103.1006.  We have a work around by which we set the Height to be 1 instead of 0, and we dont get that error.  Let me know if this version would have the fix.

Ok, Thanks Steve.

Hi, 

seemes this problem has not been fully solved yet.  I have this problem and have downloaded the latest SR. When the number of records is small there are no problems, but when there are a few thousands, the system crashes with an out of memory exception.

I have used a few simple lines of code:

          RowHeight h0=new RowHeight(0);

           RowHeight hn = new RowHeight(30);

            if (setStatus == true)

            {

                xamWebGrid1.RowHeight = h0;

            }

            else

            {

                xamWebGrid1.RowHeight = hn;

            }

When running this I see in taskmanager a huge consumption of memory (1Gb+) untill the out of memory exception occur. 

If I use RowHeight(1) instead of 0, the memory consumption seemes to be approximately half of this, and the process is able to complete.

Hi, 

The code you posted shows you hiding all rows in the xamGrid, not particular rows.  If you do that, then you're going to be essentially rendering every row, which is why you'd get a huge amount of memory consumption. 

If you want to hide all rows, just set the ItemsSource to null. 

If you want to hide a particular row, then set that particular row's height to zero. 

void grid_CellControlAttached(object sender, CellControlAttachedEventArgs e)

        {

            MyData data = (MyData)e.Cell.Row.Data;

            if (data.IsFavorite == false)

                e.Cell.Row.Height = new RowHeight(0);

            else

                e.Cell.Row.Height = new RowHeight(30);

        }

-SteveZ

Thank you for your reply Stephen.

Your suggestions makes sense if i just wanted to hide all data or just a few rows, but I am afraid what I am trying to do is a bit beyond this. The sent code-snippet was a simplified version that I used while 'investigating' the problem.  

 In the WPF version of the grid the group rows as default generates "sum xxx=yyyy.yy" when a column in the report has sum activated.  I have not found any way to get this for Silverlight.

Then as an alternative I thought of giving the users the option of  hiding/showing the detail rows in such grouped reports. The summaries-row wil not be affected, so the effect will be to have only summaries or summaries and details.

 This looks nice for relatively small reports, but I see here also quite a big memory consumption.  I see that when I hide detail rows in this way, the memory consumption goes up, and is not released again when the details are again displayed. Continued showing and hiding with the same set of data does not increase memory consumption significantly more, and performes much quicker.

I will buy your explanation if you can explain to me why rendering every row with a rowheight of 0 makes the report consume so very much more memory than any other value...?

Example:  

I have a report that makes the iexplorer consume 114 MB  of memory when the data is loaded.

If i render the report with a rowheight of 20 the memory consumption increases to 125 MB and is rather stable around 120 MB when continuing to switch between 30 and 20 as row height.

But when I set the row height to 0, memory consumption increases to 595 MB, and stays around 620 MB when switcing between 30 and 0.

NB: I have tried the same with the new 11.1 version of the grid, but the problem remains.

Regards

Jorvart

Hi Jorvart, 

The xamGrid uses virtualization. So when you have a million rows, it only ever renders whats needed in the visible viewport. This rendering is done based on the size of the rows. So, say normally only 30 rows fit into the viewport. When one row goes out of view, its then recycled and used for a new row coming into view.

However, when you set the RowHeight to 0 for all rows, you're telling the xamGrid to then render one million rows. Which means all of those controls now exist in memory.

When you set the RowHeight to 1, you're going to render a lot of rows, but only the amount for the size of your ViewPort. So say your Viewport is 800 px tall. Then you're going to render 800 rows, which is a lot, but certainly not a million.

 Now in the beginning of this post, you said you were trying to replicate a feature in WPF. Were you referring to GroupBy Rows?  And from what i understand you're trying to display summary information in them? If thats the case, its actually a feature we are working on adding for a future release. So if you could give me more information on exactly what you'd like out of the feature that'd be awesome. 

However, in it's current state, you can perform the summaries on your own for the GroupBy row, it just won't be calculated for you: 

You'd need to use a ValueConverter in your Binding, and then you can use the information of the GroupByDataContext to walk through your data and calculate your Sums:

http://help.infragistics.com/NetAdvantage/Silverlight/2011/1/CLR4.0/?page=SL_xamGrid_Custom_GroupBy_Row_Display.html 

I hope this helps makes things more clear, 

-SteveZ

Hi Darrell,

Thanks for suggestion, can you give me a simple example to use valueconverter or related link

Thanks

The FormatString is just what is going to get given eventually to a ToString on the value, and to my knowledge there isn't a format string that is going to convert NaN to a value.

You could add a ValueConverter to the column which can process your data and convert your NaNs to zeros or empty strings.

Hi Stevez,

if we are binding xamgrid with List of objects and have following column bind to some double type property:

<ig:TextColumn Key="MyDouble" HeaderText="My Double" FormatString="{}{0:0.00}" HorizontalContentAlignment="Right" />

It is working fine and even do not crash on NAN  vlaues, but it shows NaN which do not looks good, what we can do to show either empty or cutom value say dash (-).

Thanks

Thank you Stephen,

this worked perfectly and simplified my code considerable.

I only had to struggle a bit to make the decoding of 'Records' generic as my datagrid's ItemsSource is changing at runtime. 

Regards 

Jorvart