70a9576f27
… and s/gimp_parasite_flags/gimp_parasite_get_flags/ It is better to have a consistent API and the fact is that most getter/setter functions use the _get|set_ naming, but these didn't. I wondered if this was such a great idea to rename these anyway because even though we are breaking API in GIMP 3, is it the best idea to rename when no functional change happened? After discussing with Wormnest, we still agreed it was still better to go for consistency rather than regret later (and be stuck with these names for many more years). Also this fixes these warnings: > [649/1205] Generating gimp-3.0.vapi with a custom command > Gimp-3.0.gir:24162.7-24162.56: warning: Field `Gimp.Parasite.flags' conflicts with method of the same name > Gimp-3.0.gir:24318.7-24318.52: warning: Field `Gimp.Parasite.name' conflicts with method of the same name |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| gimpfont.c | ||
| gimpfont.h | ||
| gimpfontfactory.c | ||
| gimpfontfactory.h | ||
| gimptext-compat.c | ||
| gimptext-compat.h | ||
| gimptext-parasite.c | ||
| gimptext-parasite.h | ||
| gimptext-vectors.c | ||
| gimptext-vectors.h | ||
| gimptext-xlfd.c | ||
| gimptext-xlfd.h | ||
| gimptext.c | ||
| gimptext.h | ||
| gimptextlayer-transform.c | ||
| gimptextlayer-transform.h | ||
| gimptextlayer-xcf.c | ||
| gimptextlayer-xcf.h | ||
| gimptextlayer.c | ||
| gimptextlayer.h | ||
| gimptextlayout-render.c | ||
| gimptextlayout-render.h | ||
| gimptextlayout.c | ||
| gimptextlayout.h | ||
| gimptextundo.c | ||
| gimptextundo.h | ||
| Makefile.am | ||
| meson.build | ||
| text-enums.c | ||
| text-enums.h | ||
| text-types.h | ||