Partially revert "Let's not reinvent wheel here: replace DT_MAX_PATH_LEN with PATH_MAX" - we still need upgrade path for storage and format!
Relax g_assert() a little - 4096 is still just a guess about upper limit
Replace g_assert with some kind of error handling
Add option to filter images drawn on map

This reduces the images drawn on the map to the current collection/
filter, increasing the performance and reducing the mess on the map when
many images are geotagged within the current map section.
Also, changing map preferences doesn't require a restart any more.
use memory.collected_images for map view filter
removed superfluous loop index
introduce signal DT_SIGNAL_PREFERENCES_CHANGE
Small cleanups of the latest maps changes

Take care of
- typos,
- formatting,
- the unused proxy function,
- make the generated SQL query less ugly
Call reload_defaults when duplicating an instance

... since at least profiled denoise sets its GUI in that callback.
Fixes #9462.
Don't reset mouse_over_id when cursor not over filmstrip

Fixes #9933.
It's important to match g_malloc() with g_free() and plain malloc() with free()
See https://developer.gnome.org/glib/2.39/glib-Memory-Allocation.html
adobe_coeff: no longer automatically derived from dcraw

remove dcraw related stuff

dcraw's matrices depend on very fuzzy matching which with
some recurrence causes regressions.

we're going to maintain adobe_coeff ourselves :(
Fix histogram double-click (initially reported by Roumano in darktable-devel ML)
colorin: notify user if color matrix is missing
Updated Dutch translation
Merge pull request #553 from MRIG/master

Updated Dutch translation
Updated Dutch translation
Merge pull request #554 from MRIG/master

Updated Dutch translation
Fix #9948: Don't optimize isnan() away

I wonder why they broke this and what will be next ...
First batch of high DPI fixes

Soem small things like the triangles in our custom dr widgets are still
missing, but the big issues should be solved now.
I only tested these thigns by setting the screen DPI using xrandr, I am
not 100% sure if that is a perfect simulation.
People using a high DPI screen should still set the panel_width in the
config to something bigger.