JeffBurr
26 Sep 2007, 12:25 PM
[SOLVED - But Buggy]
This problem is caused by having columns that have a number as their ID in the ColumnModel of the grid. This has something to do with the multiple levels of CSS that gets appplied to the grid, which use the column ID if you have one. Apparently, there is a problem with CSS and classes that begin with a number(?) - at least with regrad to width...
So, the lesson is: don't use numbers as column ID!
*****************
I have a grid and all is well. Until I add a column that uses a date renderer:
},{
header: "Start",
dataIndex: 'StartTime',
width: 70,
sortable: true,
renderer: Ext.util.Format.dateRenderer('h:i A')
},
...etc
{
Now the column headers in the grid have widths that don't match the rest of the grid. It is something to do with the renderer, since it is this column that is off.
Any suggestions would be appreciated!
[SOLVED - But Buggy]
This problem is caused by having columns that have a number as their ID in the ColumnModel of the grid. This has something to do with the multiple levels of CSS that gets appplied to the grid, which use the column ID if you have one. Apparently, there is a problem with CSS and classes that begin with a number(?) - at least with regrad to width...
So, the lesson is: don't use numbers as column ID!
*****************
I have a grid and all is well. Until I add a column that uses a date renderer:
},{
header: "Start",
dataIndex: 'StartTime',
width: 70,
sortable: true,
renderer: Ext.util.Format.dateRenderer('h:i A')
},
...etc
{
Now the column headers in the grid have widths that don't match the rest of the grid. It is something to do with the renderer, since it is this column that is off.
Any suggestions would be appreciated!
[SOLVED - But Buggy]