The RGB histogram shows three histograms overlaid on each other.
This multiples the pixel and count attributes by 3. To correct this,
the result of gimp_histogram_get_count () is divided by 3 for the
pixel and count displays.
(cherry picked from commit bf1e125138)
So apparently Python 2 has been removed from the new Debian stable (bookworm).
As we still want to build the Python plug-ins in the CI, let's move on using
oldstable (bullseye) in gimp-2-10.
Resolves#5742.
From fa0a0212, the splash's upper text was scaled to PANGO_SCALE_MEDIUM
both when the image width was 2x or less than 2x. This was likely a
copy/paste issue, as the lower text code scaling does not duplicate.
This patch fixes it by changing the else condition to scale to
PANGO_SCALE_SMALL.
Note that this change is unlikely to be seen as it requires a very small
splash screen image to reach the else condition.
See also commit d22f1c3332 on the `master` branch. The main difference is that
right now the stable branch exits cleanly in all cases, so we don't need the
temporary environment variable to force the dirty exit (which ironically means
no crashes).
Photoshop can save metadata when exporting to tiff or jpeg, including
a thumbnail that we can't update. This can contain sensitive data, so we
should not export it. See issue #8383.
To do this, we add the two Photoshop specific tags that we know of to the
list of tags that should not be exported, so they won't be saved.
(cherry picked from commit f681c50414)
After testing a bit more, I realized that the thread was constantly re-rendering
the thumbnails, even though I didn't touch the "white-background"
button/argument.
This was not just a completely invisible problem, it actually affected the page
selection (it was very hard to select pages by clicking on them, it was randomly
working, and more often not selecting anything). This is how I realized there
was a problem.
The reason was simply that I was never actually calling g_cond_wait() because of
a first_loop flag I forgot to set.
Note that docs of g_cond_wait() explains that it is possible that "spurious
wakeup" happen. At first I thought I had this issue, which is why this commit
also adds a boolean flag to check after a wakeup, to make sure that I was in the
"condition met" case and not the "spurious wakeup" one.
Even though I realized afterwards the real reason was much more stupid, I still
left this additional check.
Fortunately this issue doesn't seem to affect the 2.10 code. Or to be more
accurate: the continuous render very likely happens there too, yet it doesn't
break page selection interaction with GTK+2 as far as I can see.
(cherry picked from commit 1584a9ba50)
Cherry pick note: though this issue didn't affect the dialog interaction in the
gimp-2-10 branch, I thought it'd still be better not to have never-ending
re-rendering of thumbnails for no good reasons.
...no image is active.
There are Arbitrary Rotation options under both the Image and Layer
menus. All of those rotation options are disabled without an image open.
To keep consistency, this disables those menu options as well.
The Tools menu Rotation option is left as-is.
(Backport)
...as parameters.
Currently, only file-gif-save can accept file paths in addition to URIs.
This results in inconsistent/unexpected behavior.
Now both versions of the GIF save procedure accept URIs or file paths.
First noted by Massimo in issue #5552.
"globalcomment" is used to store and retrieve comments for GIFs.
However, it is only loaded via the GUI; thus, the comment is lost if
you re-export non-interactively.
This patch adds code to also load the comment from GimpParasite if
non-interactive export modes are used.
