Sorry Todd, blonde moment on my behalf. I was passing a negative index to TableViewRowEditor.edit.
On Mon, 14 Sep 2009 12:41:30 pm Todd Volkert wrote: > Strange - the list button shouldn't be asking the list data for the item at > index -1 -- what's the call stack when that happens? > -T > > On Sun, Sep 13, 2009 at 10:04 PM, Scott Lanham <[email protected]> wrote: > > Thanks Todd, > > > > Getting close. The ListButton is now asking it's data source for the item > > at > > index -1. If I get my Dictionary to return a null value it causes > > problems elsewhere. > > > > On Mon, 14 Sep 2009 11:51:59 am Todd Volkert wrote: > > > One problem stems from the fact that ListButton.setSelectedItem(null) > > > was explicitly throwing IllegalArgumentException, when it probably > > > should > > > > have > > > > > been translating to setSelectedIndex(-1). I just checked in a fix for > > > this, so that might fix you up. > > > > > > So you're creating blank rows, and immediately opening an editor on the > > > > row > > > > > for the user to populate it with initial values? > > > > > > Let me know if that check-in fixes the issue. > > > > > > -T > > > > > > On Sun, Sep 13, 2009 at 9:22 PM, Scott Lanham <[email protected]> wrote: > > > > Howdy Hi, > > > > > > > > I have a TableView which displays data from a database table. That > > > > data is bound to the TableView using a custom Dictionary. It all > > > > works fine until it is > > > > time to add a new record using the TableView and in place editing it > > > > using TableViewRowEditor. Several of the fields in a TableView row > > > > have ListButtons > > > > assocated with them to restrict the field values. When the field > > > > value > > > > is > > > > > > initially Null, as with a new record, the ListButtons don't like it > > > > because Null can't be found in the lists data. > > > > > > > > Is there any way I can get ListButton to not throw an exception in > > > > this case? > > > > > > > > Thanks, > > > > > > > > Scott.
