- Apr 19, 2024
-
-
Alx Sa authored
Resolves #11347 In multi-window mode, it is possible to change images without causing the layer effects popover to close. This results in the prior image's layer effects being shown over the new image, which is confusing. This patch causes the popover to automatically close when the image is changed to prevent this problem.
-
- Apr 18, 2024
-
-
Bruno Lopes authored
AppImage is pretty fast to make, like the win crossbuild; and portable, being very appropriate to do quick tests on Linux when pushing to git. The overall organization of Debian jobs was changed to take advantage of this and make things less complicated (but less clear at first sight). I reinforce that this was the most efficent way to make the AppImage.
-
Jehan authored
This fix doesn't feel right. The whole point of having a generated manifest from the build was to use it for our flatpak job (through job dependency). Right now, it has been rendered useless. We must either re-implement the proper job dependency or find another way to fill the proper "command" with the right version (maybe just a standalone script to be used in Gitlab CI and which we could tell about to people who wish to build the nightly flatpak themselves). Anyway for now, it should do as I don't want to spend too long on this. It should fix this error in the log generated as artefact of the "gimp-flatpak-x64" job: > ../build/flatpak/meson.build:6:2: ERROR: File org.gimp.GIMP-nightly.json.in does not exist.
-
Jehan authored
Syncing dependencies back and forth with the current branch, preparing for 3.0.0 RC1 release: https://github.com/flathub/org.gimp.GIMP/pull/287
-
Jordi Mas authored
-
Bruno Lopes authored
These files has been generated by the installer scripts for historical reasons. Now that we have full-blown local builds and the upcoming MS Store version, this pervasive pratice can't continue since it creates disparity between builds.
-
-
Jacob Boerema authored
When closing the Page Setup dialog we had warnings and criticals in the terminal. The cause for this was that we were looking for the temp procedure to notify the print plug-in. However, this temp procedure is only installed if the print plug-in is running, not when running the Page Setup directly, in which case it is not needed. We now check if the procedure is valid (meaning the print plug-in is running) before calling the temp notify procedure.
-
-
-
Jehan authored
-
Jehan authored
Making sure not only that the PDB passes correctly the number of colors, but taking one random color in the array and verifying it is correct.
-
Jehan authored
-
Fixes some scripts, followup to c92cf7e8
-
Alx Sa authored
Removes an index that was needed to GimpRGB, but no longer valid now that gimp_palette_entry_get_color () returns a GeglColor object. Also, fixed an issue in Interactive Mode where the first valid palette would be used for every other attempt, no matter which palette you clicked on.
-
Alx Sa authored
Switch to using gimp_item_convert () instead of gimp_item_duplicate () so that the filter mask can be properly associated with a new image when copy/pasted.
-
Alx Sa authored
Previously, filters were lost when copying individual layers. This patch copies them to the clipboard image on cut or copy, then copies them back to the pasted image. It also fixes an issue where filters would be merged down if a selection was copied instead of the entire layer.
-
- Apr 17, 2024
-
-
Jehan authored
Color propwidgets now use GeglColor only.
-
Jehan authored
We don't need to convert GimpRGB to GeglColor now as we work directly with GeglColor!
-
Jehan authored
The comment I had written back then was wrong. Meson in fact can create an env object from another with a simple assignment (which copies the object, rather than pointing to a same object), per the answer which has been given to me in: https://github.com/mesonbuild/meson/issues/13045 This allows to have a properly separate environment (when using GIMP as a build tool, we don't want to load the test files).
-
Jehan authored
-
Jacob Boerema authored
We are using `gimp_image_set_file` to set the filename, which requires an extension, not doing so caused an error. So let's add .xcf to all compose filenames.
-
Jacob Boerema authored
When decomposing, the plug-in sets the filename without changing the extension. However, gimp_image_set_file requires the filename to be an .xcf file. To fix this we simplified `generate_filename` to always add an .xcf extension. While doing this we also fixed a critical that happened when no filename was set (new image), by testing `gimp_image_get_file` for being NULL first. When no filename was set it also didn't use the type when config_as_layers was set, this is also fixed.
-
Alx Sa authored
Resolves #11334 GBR, GIH, and PAT have internal save functions which are not meant to be run directly. However, they were showing up in the Search dialogue as valid options. This patch adds an additional check for "-internal" to prevent users from accidentally running them, as they only give a warning.
-
-
Jehan authored
The whole action name prefixing will definitely need to be straightened up in our codebase at some point (differenciating the global actions and the local ones).
-
-
-
-
-
-
-
Jacob Boerema authored
For certain min/max values of the LabelSpin widget, in combination with zero digits, it proves impossible to change the initial value. The reason for this is that the step size may become less than 1.0. In which case, stepping doesn't work because the number of digits is set to zero. Let's check for this situation and when digits is zero set the step to 1.0 and make sure that page is at least the same value. While testing this I also noticed another issue: when initializing the upper value was set to 0.0 and the lower to 1.0 which leads to a critical because lower > upper. We fix this by switching the initial upper and lower values.
-