Michael Natterer e16c8a2352 Move the new "default_new_layer_mode" APIs to the image... ... ...in both the core and libgimp. Images now know what the default mode for new layers is: - NORMAL for empty images - NORMAL for images with any non-legacy layer - NORMAL_LEGAVY for images with only legacy layers This changes behavior when layers are created from the UI, but *also* when created by plug-ins (yes there is a compat issue here): - Most (all?) single-layer file importers now create NORMAL layers - Screenshot, Webpage etc also create NORMAL layers Scripts that create images from scratch (logos etc) should not be affected because they usually have NORMAL_LEGACY hardcoded. 3rd party plug-ins and scripts will also behave old-style unless they get ported to gimp_image_get_default_new_layer_mode().		2017-08-21 20:18:00 +02:00
..
.gitignore	Adding Microsoft Windows executables to the .gitignore files	2009-06-19 00:14:17 +02:00
Makefile.am	*/Makefile.am: merge INCLUDES into AM_CPPFLAGS	2013-06-05 20:48:37 +02:00
fits-io.c	plug-ins: s/snprintf/g_snprintf/ in fits-io.c	2017-08-21 12:31:28 +02:00
fits-io.h	Bug 780698 - 32-bit integer FITS files won't open	2017-04-30 19:43:21 +02:00
fits.c	Move the new "default_new_layer_mode" APIs to the image...	2017-08-21 20:18:00 +02:00