Dan Torop

Here are better steps to reproduce, without requiring any filesystem-level work. This is to show that the current code can result in inconsistent state: 1. Start darktable with a clean...

> You are right. `post-import-image` should be triggered for duplicates as well. > As you suggest, writing it to xmp could be a workaround, but I feel the previous solution...

> exiv2 should have no problem reading `Exif.Photo.ExposureBiasValue` or `Exif.Image.ExposureBiasValue`, if they exist in the raw file. Since 0.27.4, there's even the `exposureBiasValue()` shorthand API that'll query both of these...

> I'm not on top of that. If I've worked on image_import(), the duplicate part remains a bit tricky for me. Please feel free to propose something ! Will take...

> > There's one which Fujifilm writes that exiv2 can't read, even in v.0.27.5: `RawExposureBias` (`0x9650`). > > Ah, this one is in a [completely separate block of the RAF...

> I'm not sure it makes any sense to export a picture using a printer profile. As far as I know this is not a standard profile like work profile...

> > In which case, shouldn't we remove the printer profiles from the output profile dropdown (the one in the "print settings" section at the bottom)? > > No, because...

Belatedly, I can't replicate this on Gnome. I do see the (known) weirdness that as the cursor moves into the histogram, there are a couple button draw events for each...

@mediatechnologic @todd-prior Thanks for steering me to this. It's interesting! I appreciate that there's a good test case for this from @mediatechnologic. I haven't looked at the whole thread carefully...

> @dtorop : Looks like it could be closed at this stage, ok by you? Yes, closing! But I appreciate the discussion. Apologies for being slow on this -- was...