I have come across an unpleasant issue. We have a few table views that consist only of labels, because only then we can use the onDoubleClick event. This seems to prevent the web client from setting the record index correctly. Whenever I do something like controller.getSelectedIndex(), I get wrong values.
As soon as I use fields, it works.
Version: 4.1.2 - build 663
Hi Patrick, did you file a case?
Yes. I consider this quite crucial. I noticed because wrong records were deleted .
If you trigger the action on the row itself (so double or single click or focus lost/gained) then the index should always be ok
If you trigger an action outside of the row itself so in the header of a tableview
Then currently not always in all circumstances the right row is selected because if you just click on a label in a row of a tableview
that label has no event nothing for that click/focus then the label doesnt do a callback to the server to set the selection.
For example with a field that should work if you click in a field we have a focus event attached that will set the right row.
But for labels we dont do that yet
Please make a case for this then we can look if we can enhance that