GitLab

CameraImportJob will copy RAW and JPEG, pass only the raws down to the
batch importer.

The batch importer then won't know about the associated file, and
extract the embedded file (or worse, make a development) of the RAW
file, schedule thumbnailing for that.

In the conclude step of the CameraImportJob, the files would be
associated, leading to the development being thrown away and run another
thumbnailing job.

notify_altered("image", ... will trigger thumnail re-genration and in
consequence other events, and it does all of this twice. Otoh, the
thumbnail is already generated on inport.

https://bugzilla.gnome.org/show_bug.cgi?id=716448

This will only work for "local" imports, not from camera.

https://bugzilla.gnome.org/show_bug.cgi?id=717305

Richard B. Kreckel authored Jan 03, 2017 and Jens Georg committed Jan 04, 2017

https://bugzilla.gnome.org/show_bug.cgi?id=776839

 - ExtendedPosix - replaced by GLib.get_num_processors()
 - unique-3.0 - unused, replaced with GApplication
Signed-off-by: Jens Georg <mail@jensge.org>

Adds corrupt image errors to the family of errors detected by the import logging system. Closes #6445.

Makes permissions problems leading to write failures show up under manifest.write_failed; closes #5786.

Allows the user to save a detailed log of any import complications (duplicates, file errors, etc.). Closes #2593 and #3126.

Prevents the application from inappropriately renaming 'sister' JPEG files -and- forces the application to always prefer the camera development over the embedded one if it's available; closes #4149.

Mostly grunt-work to ensure that all delegates may be stored as unowned refs and that all
out parameters are assigned prior to exiting the method.  One binding change (Gdk.EventAny)
makes these changes incompatible with 0.12.

Newly imported RAW photos are set to the developer set in the preferences dialog.

This adds the ability to switch between Shotwell developed RAW images and camera developed RAW images. It will automatically group newly imported RAW+JPEG pairs, using the JPEG as the camera developed image when available.

This addresses #3371 by using the absolute file and path as source and dest identifier when making the new BatchImportResult, instead of just using the job source and dest.

This fixes #3163 by adding the absolute path to the rejected file to the newly-created BatchImportResult, rather than just the job path.

#3132: When a duplicate file is imported and a match is marked offline, the match will be brought back online pointing to the new file.

#601: Import TIFF files.  This represents basic TIFF support, 8-bit pipeline only, using gdk-pixbuf as the support library.