When I start an image I can use the Dodge/Burn tool as normal. However once I use a layer of any sort, even once I merge all layers the Burn tool now can only give me hard edges.

I can find no way to reset that.

I run it on a Asus windows ten rig.

2.10 has a "new" symmetry tool. Helpful, however.... is there a way to show guides/lines from the origin point out per each axis of the mandala?

While it's nice that it's new, it's difficult to see how many axis and where my lines start and end in relation to the number of symmetry segments.

MandalaGaba does it well, but it does not have the editing functions we have come to enjoy and rely on such as Gimp does. If anyone here has played with the Kaleidoscope in Corel Painter, the view of the axis is another example of the guide function. However, Corel Painter 12 stops at 12 segments, where Gimp has 100 AND a proper : tool.

Hello--I am stumped!
I have a font in my GIMP fonts search path that would show a weird character instead of a plain space in Gimp, ... apparently depending on whether or not other 2 fonts (system .fon, not .ttf nor .otf) are also loaded by Gimp.
1. Screenshot showing the issue     : the two topmost fonts are 8514fix.fon and 8514Oem.fon, living in C:\Windows\winsxs\amd64_microsoft-windows-font-bitmap-fixed_31bf3856ad364e35_6.1.7600.16385_none_db04d3f548508fd9--they don't appear in usual font menus, nor in windows character map
2. After first bumping into the issue, I tried again with the same font 
  great-western-way.zip (Size: 47.28 KB / Downloads: 603) , it shows in menu as Old Street Signs:  8514fix.fon and 8514Oem.fon weren't on Gimp font menu and I was able to insert and edit the text without trouble (I have the .xcf file with the normal text)
3. However, they are back now--both in win7 and win10)--and so is the trouble.
Please: is there a way to prevent Gimp from loading those fonts (or bitmap fonts in general--I don't use them)? Or, if the trouble isn't actually related with bitmap .fon fonts, is there some workaround not involving tagging the spaces as Times New Roman or whatever--thus disturbing the font's line-height?

I am trying to change the color of a pair of white shoes in GIMP before I actually do it in real life. 

I have looked at several videos on youtube and searched this forum as well and haventh been able to find my answer.

I am trying to change the color by using the new layer option. However when I got to color the section of the shoe it doesnt show it applying. I can see what I have done by looking at the new layer with the checkered background but the color isnt applying to the actual image.

Any help would be appreciated.

I have a single object with multiple colors and a complex shape isolated on a layer with no background or other elements. How can I transform this layer into a selection without going through the tedious process of using the imprecise scissors or foreground select tools? I've spent nearly twenty minutes trying to word a search query to find the answer with no luck. Is it even possible?

➤> pdb.gimp_image_list()
(1, (1,))

➤> gimp.image_list()
[<gimp.Image '[KentsHouse-FamInDen] (imported)'>]

Obviously two different commands (procedures? attributes? properties?), despite their similar names.

The Python Console "Browse" button shows info about pdb.gimp_image_list(), but seems to know nothing about the other. Where is this other command coming from (if not GIMP's internal Procedure DataBase), and how would I know about it if I hadn't just stumbled onto it?

--
Kent

Gimp 2.10
I am trying to make a logo. In previous versions I knew how but now I think it must be different. It would be a round image with circular text around this. It would be like this image but with a different name (text)

Attached Files

Image(s)
   

That will help me pixelize an image with varying sizes dependent on similar colors.
Like pixelize just does constant size.

I want it to get varying possible pixelize dependent on similar colors for example if the area of similar colors is larger it'll return the larger size that i can pixelize on and if an area of similar colors is smaller it'll return the smaller size that i can pixelize on?

I hope I explained that right.

Caveat: I'm new to Python & Object-Oriented Programming (and not particularly skilled with GIMP)

I'm trying to learn a little about automating GIMP, and found this tutorial:

https://www.gimp.org/tutorials/Automate_Editing_in_GIMP

I was able to do the first little example, finding the python console within GIMP, and learned quite a bit, enough to do some experimenting on my own.

One thing I wanted to experiment with was setting the grid color, and I guessed at several properties ("attributes"?) of the object (?) "pdb" (which I googled to discover was GIMP's "procedural database", which I take to mean the database of scriptable procedures within GIMP), but none of my attempts (like "pdb.gimp_image_grid_set_fgcolor()" or pdb.gimp_image_grid_set_foreground_color()", etc) worked. So I figured there must be a way to list all the attributes ("properties"?) of an object, and after quite a bit of googling, came up with two [relatively easy, one-liner) possibilities:

dir(pdb)

and

pdb.query()

(I see they produce different info, so I'm unclear as to which, if either, will be my better option, but that's a question for later).

The problem is that both commands give too much information to look through efficiently.

So I did yet more googling, and came up with:

re.findall("grid",str(pdb.query()))

hoping to just get the items mentioning "grid", but all that returned was a bunch of "grid"s.

In bash, I'd try something like "pdb.query() | grep grid" (which might or might not give me usable results).

So, my questions:

1. Which is better and why, pdb.query() or dir(pdb), or are neither of these suitable for learning about the attributes/properties of an object?

2. Is there a better way of learning about the properties/attributes of an object (to figure out what attribute/property to tinker with to change the color of the grid a la the tutorial mentioned above?

3. How do I list all the attributes/properties of an object that has a lot of these attributes/properties and filter the results or present them in a way that is digestible, particularly as it relates to the output of "pdb.query" or "dir(pdb)"?

Thanks!

--
Kent

Absolute Beginner here, to python & to scripting/macroing/extending GIMP.

I had a vague remembrance that GIMP is "scriptable", and the term "macro" came to my  mind.

After considerable googling, I've about decided that "macro" is an inaccurate term, and "extending GIMP" is the correct terminology (although I tend to think of "extending" as adding new features more then simply automating the features that already exist).

I've also about decided that "script-fu" and "python-fu" are "the" automating options; I'm unsure if either is built-in, but I didn't notice these options in my Gimp's "Filter" menu until I did, on my Debian box, "aptitude install gimp-python". Not saying they weren't there; I just didn't know to look for them until after I added gimp-python to my computer.

So my first question (with more to come under different posts): Am I getting close to understanding the terminology/concepts for automating steps in GIMP? To give you an idea of where I'm trying to head, I just added a bunch of numbered labels to 28 people in a photo:



I did this manually by creating 28 layer groups, one for each label, and then on one layer drawing an ellipse and bucket-filling it, and then creating a text layer centered on the white ellipse. Afterward I realized that this repetitive process could probably be automated. My next questions will tackle various aspects of this task, but first I just want to make sure I'm understanding the concepts/terminology.

Thanks!

--
Kent