Welcome, Guest |
You have to register before you can post on our site.
|
|
|
Can the value editing of transparent pixels be disabled? |
Posted by: Nerrel - 05-09-2018, 04:51 PM - Forum: Gimp 2.10
- Replies (2)
|
 |
In 2.8.2 I made heavy use of the "value" mode for the paintbrush to do shading on layers with alpha channels. This would let me shade only the actual painted areas of the layer without altering the transparent areas whatsoever. In 2.10, Gimp now edits the transparency as well as the colored pixels, meaning that I can no longer use this brush to shade the objects on a given layer without also darkening the transparency around those objects in an unwanted way.
Is there any way to set the brush so that when in value mode it only alters the pixels that have been painted and not the transparency?
EDIT: I just discovered the "legacy" setting, which lets me get around this. I assume this is the only way to get what I'm looking for?
-Thanks
|
|
|
Limit line width |
Posted by: gimp-artist - 05-09-2018, 11:48 AM - Forum: General questions
- Replies (1)
|
 |
There is an option named "Limit line width" in the distort>engrave filter category. Anybody can easily see the difference when it is applied to an image. However I don't quite sure why the name is "limit line width". Does anyone know what the name of this option implies?
|
|
|
Python not working in 2.10.0 Windows |
Posted by: Someguy - 05-08-2018, 09:03 PM - Forum: Windows
- Replies (23)
|
 |
I installed GIMP 2.10.0 on Windows 10. During installation, I did select the option to install Python support. But for some reason, Python support is not working at all.
I do have Python installed and can run it in a terminal window just fine. However, GIMP isn't showing the Python-Fu console or any of my Python scripts in the menus at all.
During startup, GIMP shows errors in the console for all of my Python scripts:
Code:
Querying plug-in: 'C:\Program Files\GIMP 2\lib\gimp\2.0\plug-ins\python-eval.py'
C:\Program Files\GIMP 2\bin\gimp-2.10.exe: LibGimpBase-WARNING: gimp-2.10.exe: gimp_wire_read(): error
Querying plug-in: 'C:\Program Files\GIMP 2\lib\gimp\2.0\plug-ins\python-console\python-console.py'
C:\Program Files\GIMP 2\bin\gimp-2.10.exe: LibGimpBase-WARNING: gimp-2.10.exe: gimp_wire_read(): error
Querying plug-in: 'C:\Program Files\GIMP 2\lib\gimp\2.0\plug-ins\py-slice.py'
C:\Program Files\GIMP 2\bin\gimp-2.10.exe: LibGimpBase-WARNING: gimp-2.10.exe: gimp_wire_read(): error
Querying plug-in: 'C:\Program Files\GIMP 2\lib\gimp\2.0\plug-ins\palette-to-gradient.py'
C:\Program Files\GIMP 2\bin\gimp-2.10.exe: LibGimpBase-WARNING: gimp-2.10.exe: gimp_wire_read(): error
Querying plug-in: 'C:\Program Files\GIMP 2\lib\gimp\2.0\plug-ins\palette-sort.py'
C:\Program Files\GIMP 2\bin\gimp-2.10.exe: LibGimpBase-WARNING: gimp-2.10.exe: gimp_wire_read(): error
Querying plug-in: 'C:\Program Files\GIMP 2\lib\gimp\2.0\plug-ins\palette-offset.py'
C:\Program Files\GIMP 2\bin\gimp-2.10.exe: LibGimpBase-WARNING: gimp-2.10.exe: gimp_wire_read(): error
Querying plug-in: 'C:\Program Files\GIMP 2\lib\gimp\2.0\plug-ins\histogram-export.py'
C:\Program Files\GIMP 2\bin\gimp-2.10.exe: LibGimpBase-WARNING: gimp-2.10.exe: gimp_wire_read(): error
Querying plug-in: 'C:\Program Files\GIMP 2\lib\gimp\2.0\plug-ins\gradients-save-as-css.py'
C:\Program Files\GIMP 2\bin\gimp-2.10.exe: LibGimpBase-WARNING: gimp-2.10.exe: gimp_wire_read(): error
Querying plug-in: 'C:\Program Files\GIMP 2\lib\gimp\2.0\plug-ins\foggify.py'
C:\Program Files\GIMP 2\bin\gimp-2.10.exe: LibGimpBase-WARNING: gimp-2.10.exe: gimp_wire_read(): error
...and so on. Python worked fine in GIMP 2.8, but not now. Other plugins and Script-Fu works okay, just not anything in Python.
|
|
|
Plugin registry installation problem |
Posted by: Gewitty - 05-08-2018, 09:59 AM - Forum: Extending the GIMP
- Replies (5)
|
 |
I just upgraded to GIMP 2.10 from 2.8 on my Linux Mint 18 system. However, when I try to re-install the GIMP Plugin Registry, I get dependency errors for various packages which Synaptic has earlier versions of, which clearly don't work with the 2.10 version.
Has anyone else encountered this problem and, if so, is there a solution?
|
|
|
|