| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 5,148
» Latest member: vtgimp
» Forum threads: 7,822
» Forum posts: 42,474
Full Statistics
|
| Latest Threads |
Monochrome png exports as...
Forum: General questions
Last Post: rich2005
Yesterday, 09:51 PM
» Replies: 2
» Views: 135
|
Monitoring a pixel's RGB ...
Forum: General questions
Last Post: rich2005
Yesterday, 09:36 PM
» Replies: 2
» Views: 148
|
re-coloured pixels hide c...
Forum: Extending the GIMP
Last Post: programmer_ceds
Yesterday, 01:04 PM
» Replies: 3
» Views: 239
|
Wavelet-decompose doing m...
Forum: General questions
Last Post: JohnWilliams
02-26-2026, 07:46 AM
» Replies: 9
» Views: 5,299
|
Smudge tool not working
Forum: General questions
Last Post: sallyanne
02-26-2026, 12:51 AM
» Replies: 3
» Views: 270
|
Thank you for Gimp
Forum: Watercooler
Last Post: Sampollyt
02-25-2026, 12:38 PM
» Replies: 0
» Views: 135
|
RapidRAW
Forum: Other graphics software
Last Post: denzjos
02-25-2026, 07:40 AM
» Replies: 3
» Views: 1,051
|
Hiding Unwanted System Fo...
Forum: Extending the GIMP
Last Post: rich2005
02-24-2026, 10:05 AM
» Replies: 1
» Views: 251
|
Version Issue
Forum: General questions
Last Post: rich2005
02-23-2026, 09:40 PM
» Replies: 1
» Views: 289
|
GIMP 3 Python Enums: Defi...
Forum: Extending the GIMP
Last Post: MrsP-from-C
02-23-2026, 08:27 PM
» Replies: 6
» Views: 452
|
|
|
| Monochrome png exports as grayscale antialiased (RESOLVED) |
|
Posted by: vtgimp - Yesterday, 07:57 PM - Forum: General questions
- Replies (2)
|
 |
I'm presently trying to export a png file as monochrome only, but every time I do, it converts to grayscale antialiased in the saved .png.
Specifically, I save a strictly monochrome 300 dpi bitmap from MTPaint. I can view that image in any image viewer, including in GIMP itself, zoom in, and see that all of the pixels are either black or white. No grays.
In Gimp if I now export that as a png with a new name, the saved png when opened in any viewer now has antialiased greyscale pixels in curved shapes.
If I take that new image back in, and go to colors>image>threshold and again to make it monochrome, succeed at that, then save it as a png, it converts back to antialiased grayscale in the file.
I'd appreciate any advice on how I can simply save a true monochrome .png with Gimp.
Thanks in advance.
|
|
|
| Thank you for Gimp |
|
Posted by: Sampollyt - 02-25-2026, 12:38 PM - Forum: Watercooler
- No Replies
|
 |
I just want to say thank you for Gimp.
Neighbour called and asked for help, scanner on old slow win 10 machine not working.
I convinced her to let me install Gimp.
2 minutes later I was scanning on her system.
I am a Linux dude since long time.
Gimp was always the first stop solution.
Yeah, I am not showing my graphics here - this way, I am not spoiling the thank you thing.
Be assured, I am using Gimp since a very long time.
And since a very long time, it is possible to load .psd into Gimp.
I worked in the graphics "industry" back then and I had to use apple and had to use adobe producs but, when it comes to "graphics", Gimp has been the number one solution for decades.
It can do the job.
It runs on your machine.
There are even ports for android.
thanks goes to the devs and surely to the whole user community base.
thanks
|
|
|
| Smudge tool not working |
|
Posted by: steele - 02-25-2026, 03:05 AM - Forum: General questions
- Replies (3)
|
 |
I recently installed gimp to edit my photos. I end up having to blur a lot of licence plates with the smudge tool. however, every so often, the smudge tool stops smudging, and seems to do nothing instead. I was able to fix this issue a couple of times by resetting the smudge tool, but this time it still isn't working. The only setting I adjust on the smudge tool is the size of it.
Any advice would be much appreciated. For reference, I am using gimp 3.0
|
|
|
| GIMP 3 Python Enums: Definitive Plug-in and Script-Fu Guide |
|
Posted by: chuckhenrich - 02-23-2026, 12:06 PM - Forum: Extending the GIMP
- Replies (6)
|
 |
If you’re developing Python plug-ins or Script-Fu scripts for GIMP 3, you’ll know the frustration of tracking down correct enum values. The official API docs are written for C developers, leaving Python authors to piece things together from source code, forum posts, and trial and error.
I’ve put together what I hope is the definitive reference: every enum available in GIMP 3.0, compiled directly from a live GIMP 3.0.8 instance using a Python-Fu console script. That means the values are guaranteed accurate for that version. And the script is available as a free download so you can regenerate the complete listing for any future GIMP 3 release.
Each enum includes:
- the Python form you actually use in your plug-ins (e.g. Gimp.LayerMode.NORMAL)
- the uppercase PDB identifier, most useful when cross-referencing with the C API docs or porting code from GIMP 2.x Script-Fu scripts
- the raw integer value for legacy Script-Fu work
- the GEGL nickname for serialisation.
The Gimp.LayerMode table also includes the full GEGL operation string.
Every enum has a plain-English description written specifically for Python and Script-Fu developers.
https://www.chuckhenrich.com/gimp-3-pyth...reference/
Comments/suggestions welcome.
|
|
|
| Odd problem with GIMP 3.0.8 Perspective Tool |
|
Posted by: cjsmall - 02-20-2026, 10:00 PM - Forum: General questions
- Replies (4)
|
 |
I've noticed a strange new behavior with perspective transformation under GIMP 3 -- something I never saw using GIMP2. Note that while I've seen this on multiple occasions, it does not occur every time I use the tool. I am having trouble attaching images so I will provide URL links:
Here is an example picture:
Original Picture
Here the perspective tool is being used:
Using the Perspective Tool
And here is the result after applying the perspective transformation:
Results
Notice that after dragging the lower left corner to the left, the right edge of the image has now been deleted even though it was not touched. As I said, I see this frequently but not always. Is this a bug needing to be reported or is it the result of some new tool setting that has changed?
Any help better understanding what is going on is appreciated.
|
|
|
|