Closed GoogleCodeExporter closed 9 years ago
Why don't you better use the global settings?
Once that you define one table to have the autoselection enabled, the user
would likely expect the same behavior in all the tables with filters, right?
At least, that was my reasoning to avoid defining it in the TableFilterHeader'
API, using instead a global variable.
It is an easy to implement feature, just not sure whether it provides real
value.
Original comment by coderazzi
on 16 Jun 2013 at 4:15
I'm using tablefilter in two different contexts. In one the auto-select makes
sense, in other it does not. The first case is the usual scenario where I want
the toolbar actions to reflect the only existing row. In the other however the
auto-selection is problematic. The table there is used to allow selection of
(many) choices out of many. Auto-selection causes filtered row to be
auto-selected (zero column holds a checkbox) which is not the desired
behaviour. The filter should simply narrow the list of available choices, but
there is no reason to assume that the user really wants to toggle given choice.
Original comment by vojta.ja...@gmail.com
on 16 Jun 2013 at 5:23
Original comment by coderazzi
on 17 Jun 2013 at 10:10
Released version 5.1.1 with this update.
Original comment by coderazzi
on 29 Jun 2013 at 7:57
Original issue reported on code.google.com by
vojta.ja...@gmail.com
on 12 Jun 2013 at 1:48