Closed ptilopteri closed 1 month ago
This comes up from time to time, including your own previous #14740. There are arguments either way, and I guess none have ever gotten enough traction for a dev to sit down and code something.
This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.
This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.
ping
-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
On my side after years of using copy/part I have always first clicked on button to unselect all items. So I'm in favor of doing that. I'll do a PR and we will see...
On my side after years of using copy/part I have always first clicked on button to unselect all items. So I'm in favor of doing that. I'll do a PR and we will see...
yes, it is illogical to choose "selective copy" and then to have to unselect unwanted items.
-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
currently when one activates "selective copy" in the "history stack", all applicable modules are selected which requires clearing current selection and then selecting desired modules. this duplicates the option in "history stack" of "copy".
"selective copy" should default to no selection and leave the operator to make his own selections.
better user experience.