Brett Spell wrote:
Since you indicated you're interested in feedback I can think of a couple of things you might want to consider. First, instead of implementing your DocumentFilter as an anonymous inner class you should make it a proper standalone class so that it can be used with other tables without having to copy and paste the code.
Right, thats a fantastic thought, and in the plans, just haven't gotten there yet.
Brett Spell wrote:
Second, instead of overriding getCellEditor() to return the double editor it's generally better to associate that editor with a data type (e.g., Double) returned by your table model or to explicitly assign it to be the editor for that column.
That's part of the problem. I do like the idea of the associate that editor with a dataType, I'll have to look to see if i can make that work.
I was avoiding trying to make it an editor for the column, because I don't always know that THAT particular column will be of that data type. I read in metadata for a particular object, and then I create the columns based on that metadata, and if that metadata tells me that column "X" happens to be a double, int,picklist, then I need to handle that. It's been quite a pain the moose caboose, but it's been great learning as well. I'm sure I'm far from done with my questions for the community!