This problem first arose when I upgraded from GIMP 2.10.18 to GIMP 2.10.24 but I now find also exists in GIMP 2.10.28, which in this case is being run on Windows.
I'm NOT confidant when it comes to proper terminology for describing what happens. Therefore, I've produced some screenshots that display what I'd call the first sign of a problem. Start by opening an image file using GIMP 2.10.18. Then crop the image. The attached file named G21018cropped.jpg (maybe 1 of 4) displays the result, which is what I've always been accustomed to when using GIMP (i.e., GOOD result). Now do the same thing using GIMP 2.10.28. The attached file named G21028cropped.jpg (2 of 4) displays what I call a strange result (i.e., BAD).
Notice the difference in the yellow dashed rectangle (whatever that might be called). In the GOOD case it corresponds to the size/shape of the new image produced by the crop operation. In the BAD case I'm NOT sure exactly what it corresponds to but my guess is that it is the size/shape of the original image before cropping.
If you look at things like Image>Canvas Size, Image>Print Size, Image>Scale Image what is displayed in the number of pixels in the cropped image. In that, GOOD and BAD are the same. However, I commonly add a Background Layer to my photos which fit the size of the paper intended for printing and provide a border of my choosing which means preferred color and some times includes text.
To add such a background involves creating a new/larger layer which is offset in such manner that it surrounds the image/photo/picture. I typically add a transparent layer after which it becomes necessary to use the Image>Fit Canvas To Layers operation in order to fill that layer with a background color. That is when the strange/BAD results first appear as shown in the attached file named G21028error.jpg (3 of 4). If you perform Image>Canvas Size the height is what was expected but the width does NOT correspond to anything recognizable. Note: when the crop was performed in this case the height was NOT changed. My guess is that if it had been changed the same unpredictable result may have occurred for the height as well. The file named G21018desired.jpg (4 of 4) shows the desired/intended result.
The only difference between the GOOD and BAD scenario is the version of GIMP being used. While the same investigation was NOT performed on GIMP 2.10.24, recollection is that the same thing happened but it was easy to revert to using the older version of GIMP thinking this problem would get resolved going forward. However, that did NOT happen for GIMP 2.10.28 so it was decided to report the problem.
As a learning exercise I have created a Python script which takes a plug-in template, allows changes from the keyboard, and then saves it as a new blank plug-in.
I can use PF_STRING to enter one item of data (although it is not a pretty sight!), but it would seem that I can only use a PF_STRING once in a program.
Is there an elegant way that I can enter multiple items into variables, such as Name, Description, etc. via the keyboard in response to screen prompts?
and click the Download button. Unzip. Put the file chop_path.py in the user's plug-ins folder. Restart Gimp. In the Paths tab, right-click the path you want to chop. Follow the links
Tools > Chopping > ...
There you see two plugins:
Chop the path at its anchors
Chop the path by another path
I explain now both a little.
Chop the path at its anchors
This is the old one but now it is in a different place in Gimp's menu. Also the wording of the GUI and the default action are a little different. The plugin chops the strokes of the path at the anchors, producing 2-anchor strokes. The default differs from what it was before: now the default is to make one path, so that the effect is to chop the strokes of the path into small 2-anchor strokes. Optionally you can make all the 2-anchor strokes into separate paths.
Chop the path by another path
In this plugin we have two paths: the one to be chopped and another path. The action is that the strokes of the path are chopped into shorter strokes by cutting them at the crossing points with the other path. Optionally all the shorter strokes can be made to separate paths each.
Example 1
On the left the red path has 1 stroke with 4 anchors. That path we want to chop. There is another path (blue), and that is the chopping path.
In the middle picture the plugin has been applied: The red path is chopped by the blue path. You see there 3 new anchors at the crossing points; those 3 anchors are in fact double anchors and stroke ends. The red stroke has been cut into 4 shorter strokes, so the path consists now of 4 strokes. To show that they are indeed 4 separate strokes, I moved their ends a little apart, on the right.
Example 2
A spiral chopped to pieces. To begin with, the spiral (red) is one stroke. It is chopped by the fan of lines (another path, blue).
After chopping, the spiral consists of 48 strokes, on the right. In this picture the spiral is chopped into 2-anchor strokes, and I grabbed and moved 3 of them to show that they indeed are separate strokes.
In this example the new short strokes happen to have only 2 anchors each (the end points). But since the plugin preserves all original anchors, in general you often get strokes with more than 2 anchors. If needed, you can try to get rid of some anchors with the Simplify plugin.
The ordering of the strokes follows the original spiral. The plugin enables you also to make separate paths instead of one path with several strokes.
Example 3
You can also use the plugin to chop a path by itself. On the left we have a red path, one stroke with 3 anchors. In the middle picture the path is chopped by itself. This means that the stroke has been cut at the crossing points. On the right I moved the stroke ends a little so that you can see how the cuts are done. Now there are 5 strokes.
For those interested: To do this plugin I had to compute intersections of two Bezier curves. I implemented the "interval subdivision algorithm" in Section 7.6 of:
Hi
I am trying to use some Tutorials that I saved way back and they want to use the Filters/Render/ Clouds/ Difference Clouds. I understand the Difference clouds filter has changed to a "Noise" filter now in 2.10. Does the filter in 2.8 not work at all now? I have the .scm file in my scripts folder, but it is all greyed out when I try to use it. I am sure I did use it recently and it worked. Maybe I am doing something incorrectly? I am trying to put some water with a reflection in front of some houses. The background file downloaded is in .png format, and it is only the "Clouds" issue that has me stumped.
Gazza
Sorry folks............ got it sorted. Welll sort of. The filter works, but having trouble with this particular project.
Thanks
Hello. I am very new to scripting and plug-ins in general. I am trying to create a script that works with BIMP (Batch processing of GIMP) that gets the metadata from each image and updates selected fields while keeping the non-updated ones. I mainly want to update the Copyright of each of the images that are batch processed. I know I can use exiftool for this, but I am also using BIMP for more than just editing metadata and would like to only use BIMP for all these purposes. I know I need to use pdb.gimp_image_get_metadata(image) and pdb.gimp_image_set_metadata(image,data). But I just don't know how to code the script to do what I want it to do.
Has anyone tried using MathMap with the latest 2.10.28 version of GIMP? I'm a bit wary of trying it as I couldn't get it to work with 2.10.24 and reverted back to 2.10.22.
I was wondering whether there's a way to take a photograph and simplify the colours in order to give it a "painted on" look. It's difficult to describe, but I have a photo of a cat that I would like to incorporate onto a flag in a way so that it looks similar to the California state flag (with the bear). Can anybody help? Cheers.
Let say we have a layer with some lines, it can be pen or brush or something else ; that does no matter, I can take any of them for the following purpose : I would like to change the thickness of an already drown line through someting like options, preferences, etc.
