[EMAIL PROTECTED] schrieb:
> There's a lot of work to do throughout the code, for just this kind of
> thing.
> Both your issue and Christian's getClientDocument() problem raise the issue
> yet again. From a user perspective, one shouldn't need to go delving deep
> into
> the guts of internal cla
"Jim Hunter" <[EMAIL PROTECTED]> writes:
> I created a new table method called getCurrentRow that calls your code so
> now I can just do table.getCurrentRow() and it returns the correct value.
There's a lot of work to do throughout the code, for just this kind of thing.
Both your issue and Christ
This worked great. I wonder why I couldn't find it in the docs?I created a new table method called getCurrentRow that calls your code so now I can just do table.getCurrentRow() and it returns the correct value. You might think of adding a property like this to the table. I personally don't feel tha
> What is the Namespaces way to get the row # of the currently selected
> row in a Table? The ListView way was
> this.getPane().getManager().getSelectedItems(); but this does not work
> in Namespaces.
table.getSelectionModel().getLeadSelectionIndex()
What is the Namespaces way to get the row # of the currently selected row in a Table? The ListView way was this.getPane().getManager().getSelectedItems(); but this does not work in Namespaces. I found nothing in the documentation on this and nothing in the demos to respond to clicks. A little help
