Hi Mike,
I am using ultrawingrid with 2 bands. In that, i use Rowlayoutinfo to design the columns in the second band. The column width and alignment is correct and the grid is working fine. But when i export this grid to "PDF" the column size for some columns are not coming proper. Please guide me to solve this problem. I attached the screenshot below:
Grid Image :
PDF Image :
In the above images you can see the difference in the columns "Gross amount, TDS Amount & TDS %"
Hi,
In that case, as I said, we will need to see a small sample project demonstrating this problem in order to get it corrected. This looks like a pretty simple layout to recreate in a small sample. But there are a lot of things I don't know just from looking at a screen shot.
For example, is the 194c header a column or a group?
Are you creating the RowLayout in code or at design-time? Either way, it would help to know all the properties of the 194c object here as well as the RowLayoutColumnInfo settings of the three columns under it.
Mike,
I download the service release and installed in my system. After the installation, my reference changed from version 10.1.20101.1007 to 10.1.20101.2096. After the installation also i got the same issue. I gave the screen shot below.
PDF for this grid is as below :
Please guide us to solve this problem.
I do not have any way of knowing exactly what version this was fixed in, if it was fixed at all.
I recommend that you download and install the latest service release and try it. You can always roll it back if it does not work.
If you cannot install the service release, then you could try posting a small sample project here and I will run it against the latest service release and see if it works.
I am using Infragistics version 10.1. Whether this problem solved in this version?
Since the cell are not lining up with the column headers, that's clearly a bug.
What version of the controls are you using? Do you have the latest Service Release?
How to get the latest service release - Infragistics Community
I vaguely remember fixing an issue something like this a while back. So it might already be fixed. But if the latest service release does not help, then we would need to see a small sample project demonstrating the issue so we can check it out and get it corrected.