Well, beat me. I was able to reproduce on 3.5.0+1747~gc22f6a90e-dirty Manjaro Linux. Selecting 3 images in custom sort mode (file manager layout) and moving them around using drag and drop does invert the order of the selected pictures. The same thing happens in the film strip in other view modes.
I don't think that it depends on file name, or any other exif specific data fields because if I move the pictures a second time, the order gets inverted a second time, so it is normal again. If DT would look at exif data and sort descending by filename or something like this, the order would not return to normal upon moving the files a second time. Have a nice evening. Jan On 20.04.21 18:27, Solarer wrote: > Please let us try to stay objective and not start calling people names. > I am not on my PC right now so could you please try the following: > > Open a new collection with 10 pictures. Before you start to move them, > make sure they all have the same rating. Then first sort by rating, > then sort by manual order. Now try to move pictures 7-9 like you did > earlier. > Does the problem still occur? > > Best, Jan > > 20.04.2021 17:15:17 Peter Harde <peter.harde.pri...@gmail.com>: > >> ... I tried it on Lr & Cp1... if you think i'm stupid!... > > ????? What has my bug report to do with Lightroom or CaptureOne > ?????? Why should I think you are stupid ????? > >> "as imported" is the problem... The exif are the reference to >> sort the images in lightable > What is "The exif" ? Which exif tag do you mean? DateTime ? > DateTimeOriginal ? CreateDate ? Any other ? And if I choose > "custom order" this order should be only relevant one when sorting > the collection, not any other order. >> If your images are renamed in the opposite time order > They are *not* imported or renamed in opposite time order. And if > I drag/drop the same selection of three images a second time, the > sequence is inverted *again*. So as I understand, the bug > described could have to do with some "refacturing", done in the > last weeks/month which also caused the bug fixed with > https://github.com/darktable-org/darktable/pull/8719- > > > ___________________________________________________________________________ > darktable developer mailing list to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org > > > ___________________________________________________________________________ > darktable developer mailing list to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
