Hi,
I've just installed new 2012.2 version, but I still have the same problem I had with last version.
I am using different grid objects and, only with this one, I have this strange behavior:
Do you know which can be the problem? In other grids I left out column width during their definition and it works correctly.
Thanks
Flavio
Hello Flavio,
Thank you for the detailed explanations and I appologize for the late answer.
I was able to reproduce the issue when the igGrid is in the second tab and its width is 100%.
It seems that the width is taken in pixels then and that causes the issue.
You may fix this by NOT setting the width property. The default styling of .ui-iggrid-table (from infragistics.ui.grid.css) automatically sets width:100%
Your solution is OK too. I tried it and it seems to solve the issue.
Try by removing the width property and let me know the results.
I partially solved in this way, but please correct me if I am wrong.Let's start from the above bad visualization. If I select a hiddable column and I hide it, all the grid layout is re-rendered to a perfect visualization.This is great...so what I tried to do? I just put this kind of code in the javascript section:
$(".tab").tabs({ select: function (event, ui) { if ((ui.index == 1)) { $("#grid_id").igGridHiding("hideColumn", "XXXColumn"); } } });
What I do is the following: when I click on a tab, I force the grid to hide a column that I wanted to hide, but I set on show by default. The result is that when the script code hide theXXXColumn, grid layout is rendered again, occuping the 100% width. And in this way it is done automatically...
Ok. Now I am sure. After different samples, I know for sure that the situation is the following one:
I need to put 2 grids in the tab component, so I really don't know how to solve this issue...do you have any idea? Is this something caused by some CSS definitions or by a js code?
no: I am not using any kinf of virtualization, but I know why you are not able to reproduce it.
I tried in different grids and all seem to work perfectly. I found out that the only grids that give me this problem are the 2 ones those are included in a jQueryUI tab component. I don't know exactly why, but I am sure that the case is restricted to this situation...
Thank you for posting in our forums.
I wasn't able to reproduce the behavior with the RTM of 12.2 using your code snippet.
Are you sure that you haven't any kind of virtualization turned on?
An isolated sample reproducing the issue will be appreciated.
Hope hearing from you.