- Apr 26, 2024
-
-
-
-
Jacob Boerema authored
Copied over from the original separate work in: https://gitlab.gnome.org/Wormnest/gimp-file-plugin-tests After that further improved and changed and added more file format tests. Added meson.build files to integrate it in our build, but we do not install it for releases.
-
-
Jordi Mas authored
-
Alx Sa authored
Should resolve #11392 In dfb26f37, the NDE filters in the copied image are retrieved with gimp_image_get_layer_iter (). This works fine for single layer images or when all the layers are copied at once. However, if a subset is copied then the filters are always copied starting from the top level of the image. This can result in an incorrect filter being copied to the wrong layer. To fix this, we get the filters from the provided drawables list instead. This matches the number of layers in the copied image exactly, since it was used to create the copied image.
-
- Apr 25, 2024
-
-
-
Bruno Lopes authored
This regression was added by c064148a and it's similar to fb7a9954. Now, that we are using 'interruptible: false' in custom rules, this is probably fixed. Also, organize a bit better some pipelines with official GitLab .yml wizardy. I was hesitating to use "<<: *" since this creates a new layer of complexity, but this was the better way and the trick have a distinct marking by the way.
-
Anders Jonsson authored
-
-
Alx Sa authored
-
-
-
-
Alx Sa authored
-
This benefits script authors and testers of ScriptFu. Now a call to (display "foo") in a plugin goes to the terminal where GIMP started. Whether interactive or in batch mode. Make TS errors go to an error port instead of the output port. Tool plugins: Console, Eval, Server get error messages from the error port. TextConsole not changed. Tools behave per new doc "ScriptFu Tools" at dev web site. Driveby fix of SF Server: send whole message instead of byte by byte. Driveby comments and more semantic checking of set-output-port in TS. Add test plugin test-display.scm
-
Alx Sa authored
In addition, this restores the palette options for HGT import that were accidentally removed from 2.10. Mnemonics were also added to parameters which were missing them earlier.
-
- Apr 24, 2024
-
-
Jehan authored
As noticd by Bruno, the meson port is inconsistent with our 2.10 autotools build here too (and therefore our data path standards). Fixing.
-
Jehan authored
-
Bruno Lopes authored
It's not obvious (when browsing in the repo) where the macOS files are. Now, that we have one folder per OS, this became desirable for clarity.
-
-
Jehan authored
Hopefully now the CI jobs can run?!
-
-
Anders Jonsson authored
-
Jehan authored
This should hopefully fix: > realpath: /Users/circleci/macports-gimp3-arm64/var/macports/build/_Users_circleci_project_ports_graphics_gimp3/gimp3/work/build/.GIMP3-build-config-: No such file or directory Though it's harder to verify because of the "Intel macOS resource brownouts" going on on CircleCI infra, and only x86_64 runners allowed me to SSH to them. But I think that's the right fix seeing the error.
-
Jehan authored
The preview widget is a bit stretched, though at least I fix the contents to be distorted (instead, the preview is fine but we've got black-filled parts around). I'm not focusing on it because anyway, I'm not sure either if the preview is that important, or (if it is) whether we should not just integrate it as part of GimpVectorLoadProcedureDialog, i.e. for every vector images.
-
-
Bruno Lopes authored
For our two "development" sub-stages, the expiration is as follows: The 'dependencies' stage artifacts continues to expire in 2 hours. Now, all 'gimp' ones expires in 2 days (to avoid time zone limbo). For "stage"/tests and "production"/dist, the expire time depends on the source of the CI pipeline. If the artifact is oriented to a 'short-span' source (e.g. MRs and commits), it expires in 2 days. If is oriented to a 'LONG-span' one (e.g. web, schedule), 8 days (we choose 8 to have a +1 day artifact just in case if something goes wrong in the weekly schedule day, which isn't rare actually).
-
Jehan authored
This happens in particular for in-build runs (or when using GIMP3_DIRECTORY environment variable on an empty directory). In any case, I don't see why we wouldn't try and create a directory which was configured for data storage.
-
Jehan authored
We compile GObject-Introspection anyway (except for cross-builds, where anyway we don't rely on local Python scripts), so even if not installing the Python plug-ins, still use them locally.
-
Alx Sa authored
Resolves #11176 After the initial color space invasion, changing colors in the IFS color transformation section no longer affected the image. It seems that ifsD->*_cmap->color held the actual color selected by the user, but this value was not making it into elements[ifsD->current_element]->v.*_color. This patch connects the *_cmap->color values to the functions used to draw the image on the screen.
-
meson.build exclude subdirs script-fu/test/ and script-fu/scripts/test on a stable release.
-
Move test plugins from /scripts to /scripts/test. POTFILES.skip that directory. Add a readme to scripts dir. Revise readme in scripts/test Rename test9.scm which tests the new byte type support in Scheme. Install it in unstable build, it is an important test, long and sophisticated. Install contactsheet.scm as a test plugin in unstable build. See test/meson.build for comments about its issue.
-
Formerly, both Clothify and "Clothify v3" are installed in menu Filters>Artistic. They are duplicates. Clothify is the original using the old-style, homegrown interface. "Clothify v3" is new-style, GimpProcedureDialog interface. Both are marked for translation. Only Clothify (v2) is translated (in potfiles.in) "Clothify v3" is not translated (in potfiles.skip) This commit does not break string freeze. Moves "Clothify v3" to Demos menu. It only installs in an unstable build. The new is installed in unstable only for comparison with the old. FUTURE: when no string freeze: Swap the new and the old. Move "Clothify v3" clothify-v3.scm to potfiles.in and move "Clothify" clothify.scm to potfiles.skip. Swap the menu items, so the user doesn't see "v3."
-
Jehan authored
- Fix a few broken references and an inconsistent argument name. - Add the new headers in the introspectable header list. - Add a few missing class descriptions for GimpProcedure and subclasses.
-
Jehan authored
Instead of filling default GUI for a specific type of plug-in procedure in fill_list(), we add 2 methods: * fill_start() is ensured to run once (and only once) before any fill_list() code runs. * fill_end() is ensured to run once (and only once) after all fill_list() ran. This takes care of 2 kind of GUI bugs which we could have: 1. First if no explicit fill were run (i.e. neither gimp_procedure_dialog_fill() nor gimp_procedure_dialog_fill_list() were ever run), then the default interface would not be added to the dialog. Yet this case could happen when we don't want anything else but the default GUI (this will be the case in the upcoming file-wmf-load GUI). 2. Second if at the opposite, you fill several times fill functions (I hadn't thought of this, but noticed some already started to do this in our ported plug-ins), we obviously don't want the default GUI to be added several times either.
-
Alx Sa authored
-
- Apr 23, 2024
-
-
Jehan authored
-
Jehan authored
… GimpVectorLoadProcedureDialog.
-
Jehan authored
As expected, it is made to reuse shared code for every GimpVectorLoadProcedure. In particular, they all need to choose dimensions to load at, so we are sharing a same GimpResolutionEntry widget logic everywhere now. I am in fact still very unsure about the code logic for this widget by the way for these reasons: * It still puts too much emphasis on the "resolution" (pixel density) part, which makes people believe it's important, while they should in fact choose the pixel dimensions most of the time and not care about the pixel density. * Right now we can't break ratio (which in fact was already impossible in most vector format plug-ins we had). Do we want to add a chain and allow this? * If we consider the pixel density as the one we want to set the document with (which may not be the same thing as the one from when we load the document), we also want to break link between width/height dimensions and pixel density. Right now we can't (updating one field updates the others too). * There is always this issue of precision with pixel density vs. pixel dimensions because we don't necessarily find the same values when computing from one side to another because of lack of precision and this confuses people. * Finally there is the question of multi-page documents (e.g. PDF) where the chosen dimensions are the document dimensions whereas each page may have a different size which has to be recomputed independently and this got me off-by-one errors. I think I'll need to review a bit the logic, but I'll do once I've ported all the vector format load plug-ins first to see the most common usages.
-