QGIS » QGIS Application

Indeed, works fine in master but not in 2.14.3 (this is was I was about to send before I gave it another try and it works).
However, my next tries fail and I'm not really sure my pad is the culprit, given that i easily use the buttons in 2.15 but often fail to get them work in 2.14 (is it a click or a press action in 2.14?)

@Matthias Kuhn

I unselect some checkboxes, click the "select all" button on the toolbar and all boxes are checked.

In case it works like that, why not call it "Check All" instead of "Select All"?
Then what is the reset button for: just reset the changes since last application or reset to customization=false state?

Multiselect does not work but I would also not know what to expect from multiple selected items.

I neither know. I tried it because of the " Select All" button.
But can't we imagine a check/uncheck option in context menu user can use to change state of items in few clicks?

"Select All" > "Check All" done.

But can't we imagine a check/uncheck option in context menu user can use to change state of items in few clicks?

Do you think that's still necessary when we have something like #15009?

Matthias Kuhn wrote:

"Select All" > "Check All" done.

Thanks. would that be backported? actually I'm writing QGIS 2.14 Doc about this feature so might be good to have the right text if it is to be documented.

But can't we imagine a check/uncheck option in context menu user can use to change state of items in few clicks?

Do you think that's still necessary when we have something like #15009?

Not sure it's needed. If I had to choose, I'd vote for #15009 (and #15022?)

Thanks. would that be backported? actually I'm writing QGIS 2.14 Doc about this feature so might be good to have the right text if it is to be documented.

I'm not sure. I thought one of the ideas of LTR was to maintain a stable UI and especially if you document it, it would be bad to have a documentation that does not match all versions.

I do not really agree with you.
LTR has fixes and thus new releases. People who are stuck to 2.14 expect its issues to be fixed so they should update to 2.14.x when released imo. I'm not sure UI modification should be blocker for bug fix. And more generally it's not easy to document a feature you know is buggy.

That said the current change is about a tooltip on an icon so not visible in UI and to be honest, I've Nyall already merged a PR I proposed after my previous message.