Hello,
> > This seems *more* counter-intuitive than *not* performing an expected
> > > operation on all *selected* items, or is it limited only to exporting,
> > > which would be even more counter-intuitive? Isn't the selection
> > > process/action designed to limit actions to a *selection*? And in the
> > > same manner, I can limit view to four or ten images and having twenty
> > > selected, export all twenty instead of only those appearing in my
> > > view. Please consider returning to the previous behaviour.
> > >
> >
> > you'll have to fight that out with the proponents of the current
> behaviour,
> > i don't care either way.
>
> Ok, *who* do I *fight* with in order to return to previous action? Or is
> it possible to have it both ways with a configurable option?
>
>
I proposed some patches 3 weeks ago that have been merged in master.
In my opinion when you only have one picture displayed on screen,
actions should be done on that picture instead on the selected pictures
because in that case, you can't see which pictures are selected. For
example if you have one picture displayed and 10 selected in your
collection and press 'Rotate' button, Darktable will rotate the 10 selected
pictures instead of the one you are currently viewing. I found this was not
very intuitive for the user (rotating something you cannot see). This was
also
the case for all other actions ('Remove', 'Delete', 'tags', 'export', ...)
and some
users (including me) were requesting this feature.
When you have more than one picture displayed, the old behavior is still
used
and actions are done on the selected pictures. (if you have 20 images
selected and only 4 visible, export action will still export the 20 images
selected).
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).
------------------------------------------------------------------------------
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
