Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

gimp-image-crop bad parameter #53

Alsciende opened this Issue Dec 9, 2013 · 2 comments


None yet
2 participants

When using "Crop", the procedure "gimp-image-crop" is called with the value "-64" for the parameter "offx". This value is off-limits.

Can you tell the exact steps to reproduce this problem=

Gimp 2.8.6 on windows 7 Enterprise 64bits
Bimp 1.7
1st filter: Crop, Manual Crop, 429x599
2nd filter: Resize. Set exact size in pixel. For both dimensions. Cubic. 300x418. Change resolution. 72x72.

Add an image 430x600. Apply.

Ok, so I understand what happens. BIMP applies the "Resize" filter before the "Crop" filter, so the image is too small for the crop operation. If I do only the crop, it works fine. I already noticed before that the manipulations were not always processed from left to right.

Which brings me to this question: how is the order of the manipulations decided? Why isn't it first in, first out, from left to right?

I'd like to know the answer to that question, but whatever the answer is, in my mind the fact that manipulations are not processed in the order decided by the user is a bug.

alessandrofrancesconi added a commit that referenced this issue Apr 21, 2014

Pushed to 1.9
- Added watermark alignment buttons for top-center, center-left,
center-right, bottom-center (thanks to @Walt9Z)
- It's now possible to resize both dimension but keeping the aspect
ratio. In this case, the pixel width/height
are treated as maximum sizes for the resulting image. (issue #25)
(thanks to @Walt9Z)
- Resize and Crop manipulations are now treated as "normal priority"
steps. Originally they started first, now they follow
the original order given by the user in the GUI (issue #53)
- Added "tall" smartphone screen Crop presets (for devices like iPhone
- JPEG subsampling settings was wrong (issue #52)
- Updated Italian translation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment