I'm curious about *why* this shouldn't be a configuration checkbox, since it's only a UI behavior option, and wouldn't have implications for backwards/forwards compatibility. It seems like something that makes sense for some people and not for others.
Aside from that, a status message when zooming into this 'single selection' mode might be a good idea, or some other indicator. I would also +1 the desire to not introduce inconsistent behavior between different modules in this regard. Nobody likes surprising results from significant UI interractions. But then again, I struggled with the way pointer hovering overrides selections in LT mode, so maybe I'm just slow to catch on. ;) On 2013-07-31 [email protected] wrote: > Am Mittwoch, 31. Juli 2013, 18:03:17 schrieb Pierre Le Magourou: > > Hello, > > Hi. > > [Discussion about actions only working on one image when zoom level == 1] > > There is an important difference between actions like rating, rotation, ... > and > export: The latter doesn't work on the image but with the image and creates > something new, while the rest changes the selected image(s). Let's forget > that > there are a few tags added/removed when exporting, since that is not the > intended behaviour why people export but just a side effect. > > So I would vote for ignoring the zoom level for exporting (and probably also > for HDR creation, that one doesn't make sense for a single image) and keep > the > current behaviour for the actions that actually do something to the images. > > > Of course this behaviour need to be discussed, I just wanted to simplify the > > UI and I forgot to think about people who did not want this feature. (Sorry > > about that) If you think this is not the good behaviour we can return to > > the previous one (or make this new behaviour configurable). > > No, this is nothing that should be configurable. ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ Darktable-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-users
