<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Selecting a tree view row with a check box entry toggles the entry" href="https://bugs.documentfoundation.org/show_bug.cgi?id=138865#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Selecting a tree view row with a check box entry toggles the entry" href="https://bugs.documentfoundation.org/show_bug.cgi?id=138865">bug 138865</a> from <a class="email" href="mailto:caolanm@redhat.com" title="Caolán McNamara <caolanm@redhat.com>"> Caolán McNamara</a> <pre>Maybe... a) the auto-toggle on click should only kick in if there is only one checkbox in a row (which would solve this case regardless of any other potential changes) because how do we know which one should toggle. b) it seems more natural to me that the first click on an unselected row just selects it. Subsequent clicks on a selected row to change the toggle like it currently does seems fairly ok too. Another option is that this toggle on single click is something that really only the autofilter wants to do, it might then be the case that setting "single-click-activate" on the treeviews in filterdropdown.ui to true (which sets mbActivateOnSingleClick in SvTreeListBox) then connecting via connect_row_activated to know when a row was clicked on and manually toggle the row's checkbox in a callback there would work and make this auto-toggling on row click an autofilter only feature. and/or some hybrid of b where if mbActivateOnSingleClick is set then a first click on an unselected row *does* toggle and select it, but with mbActivateOnSingleClick false it just selects it.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>