afx wrote:How should a regular copy know whether you want the lens correction
Of course you're right but don't forget we're in the "Wishlist zone" and I actually meant the comment in a slightly different context that I didn't expressed well enough.
I was thinking in terms of getting new users good results quickly, and how the documentation and videos make things appear more straight forward than the really are.
For example: The documentation shows how to use "Copy Sets" and we know that using them lets one avoid copying & pasting too much data between images.
The problem is that the documentation gives no indication that "Copy Sets" is the way to avoid copying & pasting too much data between images, or why that could be important.
I don't believe any new user will grasp this right away.
What I didn't say, because sometimes I forget that others aren't mind readers, is it might be useful if some of the control panels had a "Ctrl+C Lock" check box.
I'm just thinking about the few panels like "Lens Correction" "Color Management" "White Balance" that mostly get set by ASP/DefaultRaw and usually don't need changing.
Think of it as the opposite of "Copy Sets", call it a "Don't Copy Set", check boxes on Controls that tells Ctrl+C not to copy this control.
On the topic of Edit>Copy selective Image Settings versus Keyboard Shortcut Ctrl+Shift+C
Here's a demonstration that might shed some light on why new users get mixed-up with ASP.
Choose one of your test images and do a keyboard Ctrl+Shift+C. Try to ignore the fact that it failed to bring up the Selection Panel. Which I guess is a bug.
Paste the clipboard contents into one panel of WinMerge. Next copy the same image data using Edit>Copy selective Image Settings(select All - OK).
Paste the new clipboard contents into the other panel of WinMerge. Hit refresh on WinMerge and see the differences.
Presumably this is a bug - not sure how or to whom to report it but I trust it will be read here.
Even though ASP is awesome - ASP can always use a tad more awesomeness.