I like and applaud many new features in LR2-B (localized adjustments, new metadata search bar, improved keyword implementation, to mention just a few). But one of the new "features" I am less thrilled with, and one that quietly slipped into LR2-B almost unnoticed, is a very different way that the app handles selections in the grid and filmstrip modules.
>> In LR 1.x when the user selected multiple images, one of them was treated as active selection, and any quick develop (or develop module) changes (exposure, WB, clarity, etc.) were applied to this "active selection" image only (Apple calls this "primary select" in Aperture). If one was happy with the initial result, the change could easily be propagated to other (previously co-selected) images by simply clicking on the Sync Settings button (available in both, the Library's and Develop module). Yes, admittedly, some actions such as photo rotation or keywords (and other metadata) assignments were applied to all selects, not just the active photo. Although this behavior was somewhat inconsistent (and not particularly well documented), it was easy to remember .
In LR2-B this behavior has changed: now, with multiple images selected ALL selects (not just the active / primary select) are immediately affected by any develop changes. While some people may prefer this behavior, it is quite dangerous: since collapsing / expanding ALL stacks requires selecting and deselecting ALL images in the catalog, it is relatively easy to forget that, and accidentally / unintentionally apply major develop changes to several thousand images all at once. Oops! I haven't dared to try this so I don't know. My guess is, this would likely slow the whole thing down (or crash it) and undoing say, 8000 accidental WB or clarity changes might be a less-than-fun experience. Given that this is significantly changed behavior, I think there is a very good chance that previous LR 1.x users will make this mistake often.
Aperture solves this problem elegantly - it has a "primary only" toggle button which allows the user to decide if multiple selected images will be affected by any changes, or if just the "primary select" will. LR does not have that option, and the current "improvement" will inevitably result in LR 1.x users making unintended, massive changes to their catalogs. It would be great if Adobe un-did this "feature", reverting to its previous, much safer implementation, or (in a perfect world) simply gave us the option (Aperture-like) to toggle all-selects vs. primary-only.
OK - I stand corrected - I is NOT a new problem in LR2-B. It's an old one - always been there (I guess I just usually develop in thhe D-module, and then sync). Still it would be nice to have a primary only switch like in Aperture, to turn this "feature" off.