Am Samstag, 16. November 2013, 19:10:41 schrieb Markus Jung: > Am 16.11.2013 11:15, schrieb Tobias Ellinghaus: > > The alternative would be to always reset the selection when > > entering darkroom (currently this is only done when < 2 images are > > selected) but that would hurt more people as selections would > > never survive a trip to darkroom. > > I do not agree with your conclusion. The alternative would be to > reset/replace the selection if images have been passed as commandline > arguments, irrespective of the number of previously selected images. > This is what happens if only one image has been selected, it > consequently it should also happen for the #selections > 1 case.
That's not what is happening. The selection is replaced for 1 image when you enter darkroom, it has nothing to do with the command line. If you want to try it yourself: - select one image on lighttable, hover another image, press 'd' - press 'l' - see that the image you opened in darkroom is now selected - now select >1 images - 'd' over another image - 'l' - selection didn't change. I am open to suggestions how to handle this, but since darkroom isn't meant to work on arbitrary sets of images but just the currently opened one I find it more confusing when anything but the current image is exported. > Regards, > Markus Tobias
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
_______________________________________________ Darktable-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-users
