Is the problem that calling insertRow() does not remove the emptyTableWidget and display the new row? It that is the case, it sounds like a bug. Adding a row using insertRow() should hide the emptyTableWidget. Thanks, John LaBanca [EMAIL PROTECTED]
On Sat, Oct 25, 2008 at 3:24 PM, Brad Larson <[EMAIL PROTECTED]> wrote: > > I'm having a little trouble after pulling up to the latest gwt- > incubator with the PagingScrollTable. I use this widget to display a > table of data and have a button to allow the user to add a row. When > this button is clicked, I want a new row to be added which has text > boxes instead of labels so the user can type in data to enter into the > table. When they are done filling in the boxes, they click a 'Done' > button and the data is sent to the server and added to the > cachedTableModel. > > This works fine if the table already contains data, but is broken for > empty tables now that they have the display: attribute set to false. > I am adding the row by calling cachedModel.insertRow(); and > dataTable.setWidget(row, col, textBoxWidget); for all cells in the new > row. The ideal fix for me is to call > setEmptyTableWidgetVisible(true); on my PagingScrollTable, but I'm > open to alternatives. Is there a better way I should handle this use- > case? > > Thanks in advance for any help!! > -Brad > > > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---