I think there is a problem in fwt::Table implementation regarding row selection. Depending on how I sort the rows and which row I select (I use multiple selection), I do not always get the correct index of the row matching the TableModel.
I use a Table to show and edit data, when I double-click on a row it should edit it, but sometimes the program finds the wrong row. It finds the wrong index for some rows and the right index for the others.
It is annoying but not too critical as I am only developing this application for my own interest (not commercial), and I have enough time to finish it until I would eventually use it for some job.
Thanks in advance for your feedback, Regards
brianWed 27 Jul 2011
Hi sarnold, I played around with it and can't duplicate that problem.
Do you have a specific test case that I could use? If you need to send some code you can email it to me - [email protected]
brianThu 28 Jul 2011
In case anyone else has this problem, set of fixes: changeset
I don't think I ever really wrung out the code when I added support for column visibility and row sorting (without the model having to care). But I have greatly beefed up table.fan example script to verify all the different APIs work with the logical model col and row indices.
sarnold Wed 27 Jul 2011
Hello,
I think there is a problem in
fwt::Tableimplementation regarding row selection. Depending on how I sort the rows and which row I select (I use multiple selection), I do not always get the correct index of the row matching theTableModel.I use a Table to show and edit data, when I double-click on a row it should edit it, but sometimes the program finds the wrong row. It finds the wrong index for some rows and the right index for the others.
It is annoying but not too critical as I am only developing this application for my own interest (not commercial), and I have enough time to finish it until I would eventually use it for some job.
Thanks in advance for your feedback, Regards
brian Wed 27 Jul 2011
Hi sarnold, I played around with it and can't duplicate that problem.
Do you have a specific test case that I could use? If you need to send some code you can email it to me - [email protected]
brian Thu 28 Jul 2011
In case anyone else has this problem, set of fixes: changeset
I don't think I ever really wrung out the code when I added support for column visibility and row sorting (without the model having to care). But I have greatly beefed up table.fan example script to verify all the different APIs work with the logical model col and row indices.