🚀 go-pugleaf

I was already doing that.  The solution turned out to be to override JTable's
editCellAt() method and check the return code on isCellEditable() and not
prepare the editor if isCellEditable() returned false.

Thanks.

Ernesto Basc�n Pantoja wrote:

> Hi:
>
> Well, your overridden getTableCellRendererComponent(...) method receives a
> column as
> parameter. Its value is the index of the "viewed" column, not the index of
> its model, so,
> to obtain the right value, you must use:
>
> int modelColumn = myTable.convertColumnIndextoModel(columnParameter);
>
> and work with it to render the cells.
>
> Saludos
>
> Ernesto
>
> Michael Kintzer wrote:
>
> > I have a JTable constructed with a subclass of DefaultTableModel.  In my
> > implementation of MyDefaultTableModel, I override isCellEditable to
> > return true or false conditionally based on the value in a particular
> > column.  If the cell is not editable, I use a renderer to render the
> > cell's background gray.
> >
> > My problem is that if the column's are moved around, in some cases, even
> > though isCellEditable is (correctly) returning false, and the renderer
> > is correctly showing the gray background for what should be a
> > non-editable cell, the JTable prepares an editor anyway.  The reverse is
> > also true, after I move the columns around. i.e. isCellEditable returns
> > true (correctly), and the renderer paints a white background (again
> > correctly), but the JTable fails to create an editor.  Is this a bug in
> > JTable?
> >
> > Thanks for any insights,
> >
> > Michael Kintzer