Hello,
In our product we use the UltraGrid. When doing a print preview, we get an OutOfRangeException.
Did anyone have seen this before and is there a workaround/solution available?
I checked the code in Infragistics.Win.UltraWinGridPrintManager.CalculateFirstRows.
There ut seems to be a situation of an endless loop when adding a new logical page. Somehow, for certain a certain amount of rows, it cannot determine what should be on the next logical page or it keep generating the same logical page.
I can reproduce this with one of the samples of NetAdvantage Select 2010, Vol. 1.
1. Goto Windows Forms -> Samples -> Grids -> Samples Explorer -> Print/Print Preview
2. Deselect Portrait
3. Delete first 30 rows.
4. Click on Preview
-> IndexOutOfRangeException
Service Release Version 0.1.2018
We're running on Windows7
Best regards,
Henk Wagterveld
Issue "32895: Print preview gives an OutOfRangeException" has been addressed in service release versions 10.1.20101.2033 CLR 2.0, 10.2.20102.2003 CLR 2.0.
Hi Henk,
As this is the same issue you reported in your support case, a development issue has already been created for you with an issue ID of 32895.
Okay, that was the key. When I maximized the form, I get the exception. I will forward this thread over to Infragistics Developer Support so they can get this fixed.
Hi Mike,
I did some more testing and found out that this occurs when maximaxing the grid application to its maximum size (in my case I use a screenresolution 1900 x 1200. However, I could also reproduce it for 1280x1024.
When I keep the test application to its initial size, then the error doesn't come.
I tried both 32- and 64-bit, but see the same behaviour. Also the printerchoice doesn't help.
I installed the latest service release, but that didn't help either.
Can you test with these resolutions and resize your application to maximum size?
Regards, Henk
I used 10.1, since that's what you said you were using in your initial post. But I am using the latest internal build so it's possible that I have some fixes that you don't.
I believe that the 20101.2027 service release is now available. So perhaps you should try that and see if you still have the problem.