dnrops
/
gimp
mirror of https://github.com/GNOME/gimp.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
gimp/pdb/pdb.pl

613 lines
31 KiB
Perl
Raw Normal View History

In all files, changed the standard copyright notice to say "GIMP - The GNU 2006-12-09 Sven Neumann <sven@gimp.org> * In all files, changed the standard copyright notice to say "GIMP - The GNU Image Manipulation Program".
2006-12-10 05:33:38 +08:00
# GIMP - The GNU Image Manipulation Program
fix spelling of "quality" in comment 2003-07-03 Manish Singh <yosh@gimp.org> * plug-ins/common/jpeg.c: fix spelling of "quality" in comment * tools/pdbgen/*.pl: update copyright strings to 2003 * libgimp/gimpenums.h * libgimp/*_pdb.[ch] * app/pdb/*_cmds.[ch] * app/pdb/internal_procs.[ch] * plug-ins/pygimp/gimpenums.py * plug-ins/script-fu/script-fu-constants.c: regenerated
2003-07-03 08:47:26 +08:00
# Copyright (C) 1998-2003 Manish Singh <yosh@gimp.org>
PDB autogen stuff. Unfinished and undocumented -Yosh
1998-10-24 13:19:30 +08:00
Change licence to GPLv3 (and to LGPLv3 for libgimp). 2009-01-17 Michael Natterer <mitch@gimp.org> * all files with a GPL header and all COPYING files: Change licence to GPLv3 (and to LGPLv3 for libgimp). Cleaned up some copyright headers and regenerated the parsers in the ImageMap plugin. svn path=/trunk/; revision=27913
2009-01-18 06:28:01 +08:00
# This program is free software: you can redistribute it and/or modify
PDB autogen stuff. Unfinished and undocumented -Yosh
1998-10-24 13:19:30 +08:00
# it under the terms of the GNU General Public License as published by
Change licence to GPLv3 (and to LGPLv3 for libgimp). 2009-01-17 Michael Natterer <mitch@gimp.org> * all files with a GPL header and all COPYING files: Change licence to GPLv3 (and to LGPLv3 for libgimp). Cleaned up some copyright headers and regenerated the parsers in the ImageMap plugin. svn path=/trunk/; revision=27913
2009-01-18 06:28:01 +08:00
# the Free Software Foundation; either version 3 of the License, or
PDB autogen stuff. Unfinished and undocumented -Yosh
1998-10-24 13:19:30 +08:00
# (at your option) any later version.
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
# You should have received a copy of the GNU General Public License
Change the license URL from http://www.gnu.org/licenses/ to https://
2018-07-12 05:27:07 +08:00
# along with this program. If not, see <https://www.gnu.org/licenses/>.
PDB autogen stuff. Unfinished and undocumented -Yosh
1998-10-24 13:19:30 +08:00
package Gimp::CodeGen::pdb;
%arg_types = (
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
int32 => { name => 'INT32',
Remove GIMP_TYPE_INT32 and GimpParamSpecInt32 Use gint and GParamSpecInt instead.
2019-08-15 20:04:56 +08:00
gtype => 'G_TYPE_INT',
type => 'gint ',
const_type => 'gint ',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
init_value => '0',
get_value_func => '$var = g_value_get_int ($value)',
pdb, libgimp: use GIMP_VALUES_GET,DUP_FOO() in the libgimp PDB wrappers
2019-09-04 08:49:33 +08:00
dup_value_func => '$var = GIMP_VALUES_GET_INT ($value)',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
set_value_func => 'g_value_set_int ($value, $var)',
take_value_func => 'g_value_set_int ($value, $var)' },
float => { name => 'FLOAT',
gtype => 'G_TYPE_DOUBLE',
type => 'gdouble ',
const_type => 'gdouble ',
init_value => '0.0',
get_value_func => '$var = g_value_get_double ($value)',
pdb, libgimp: use GIMP_VALUES_GET,DUP_FOO() in the libgimp PDB wrappers
2019-09-04 08:49:33 +08:00
dup_value_func => '$var = GIMP_VALUES_GET_DOUBLE ($value)',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
set_value_func => 'g_value_set_double ($value, $var)',
take_value_func => 'g_value_set_double ($value, $var)' },
string => { name => 'STRING',
gtype => 'G_TYPE_STRING',
type => 'gchar *',
const_type => 'const gchar *',
init_value => 'NULL',
pdb, libgimp: annotate input arrays with (element-type foo)
2019-08-01 00:58:52 +08:00
out_annotate => '(transfer full)',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
get_value_func => '$var = g_value_get_string ($value)',
pdb, libgimp: use GIMP_VALUES_GET,DUP_FOO() in the libgimp PDB wrappers
2019-09-04 08:49:33 +08:00
dup_value_func => '$var = GIMP_VALUES_DUP_STRING ($value)',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
set_value_func => 'g_value_set_string ($value, $var)',
take_value_func => 'g_value_take_string ($value, $var)' },
Remove GimpStringArray in favor of GStrv GLib has a specific type of NULL-terminated string arrays: `G_TYPE_STRV`, which is the `GType` of `char**` aka `GStrv`. By using this type, we can avoid having a `GimpStringArray` which is a bit cumbersome to use for both the C API, as well as bindings. By using `GStrv`, we allow other languages to pass on string lists as they are used to, while the bindings will make sure to do the right thing. In the end, it makes the API a little bit simpler for everyone, and reduces confusion for people who are used to working with string arrays in other C/GLib based code (and not having 2 different types to denote the same thing). Related: https://gitlab.gnome.org/GNOME/gimp/-/issues/5919
2020-12-24 04:15:43 +08:00
strv => { name => 'STRV',
gtype => 'G_TYPE_STRV',
type => 'gchar **',
const_type => 'const gchar **',
init_value => 'NULL',
in_annotate => '(array zero-terminated=1)',
out_annotate => '(array zero-terminated=1) (transfer full)',
get_value_func => '$var = g_value_get_boxed ($value)',
dup_value_func => '$var = GIMP_VALUES_DUP_STRV ($value)',
set_value_func => 'g_value_set_boxed ($value, $var)',
take_value_func => 'g_value_take_boxed ($value, $var)' },
Remove GimpUint8Array in favor of GBytes GLib has a specific type for byte arrays: `GBytes` (and it's underlying GType `G_TYPE_BYTES`). By using this type, we can avoid having a `GimpUint8Array` which is a bit cumbersome to use for both the C API, as well as bindings. By using `GBytes`, we allow other languages to pass on byte arrays as they are used to, while the bindings will make sure to do the right thing. In the end, it makes the API a little bit simpler for everyone, and reduces confusion for people who are used to working with byte arrays in other C/GLib based code (and not having 2 different types to denote the same thing). Related: https://gitlab.gnome.org/GNOME/gimp/-/issues/5919
2023-05-24 05:37:46 +08:00
bytes => { name => 'BYTES',
gtype => 'G_TYPE_BYTES',
type => 'GBytes *',
const_type => 'GBytes *',
init_value => 'NULL',
out_annotate => '(transfer full)',
get_value_func => '$var = g_value_get_boxed ($value)',
dup_value_func => '$var = GIMP_VALUES_DUP_BYTES ($value)',
set_value_func => 'g_value_set_boxed ($value, $var)',
take_value_func => 'g_value_take_boxed ($value, $var)' },
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
int32array => { name => 'INT32ARRAY',
gtype => 'GIMP_TYPE_INT32_ARRAY',
type => 'gint32 *',
const_type => 'const gint32 *',
array => 1,
init_value => 'NULL',
pdb, libgimp: annotate input arrays with (element-type foo)
2019-08-01 00:58:52 +08:00
in_annotate => '(element-type gint32)',
out_annotate => '(element-type gint32) (transfer full)',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
get_value_func => '$var = gimp_value_get_int32_array ($value)',
pdb, libgimp: use GIMP_VALUES_GET,DUP_FOO() in the libgimp PDB wrappers
2019-09-04 08:49:33 +08:00
dup_value_func => '$var = GIMP_VALUES_DUP_INT32_ARRAY ($value)',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
set_value_func => 'gimp_value_set_int32_array ($value, $var, $var_len)',
take_value_func => 'gimp_value_take_int32_array ($value, $var, $var_len)' },
floatarray => { name => 'FLOATARRAY',
gtype => 'GIMP_TYPE_FLOAT_ARRAY',
type => 'gdouble *',
const_type => 'const gdouble *',
array => 1,
init_value => 'NULL',
pdb, libgimp: annotate input arrays with (element-type foo)
2019-08-01 00:58:52 +08:00
in_annotate => '(element-type gdouble)',
out_annotate => '(element-type gdouble) (transfer full)',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
get_value_func => '$var = gimp_value_get_float_array ($value)',
pdb, libgimp: use GIMP_VALUES_GET,DUP_FOO() in the libgimp PDB wrappers
2019-09-04 08:49:33 +08:00
dup_value_func => '$var = GIMP_VALUES_DUP_FLOAT_ARRAY ($value)',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
set_value_func => 'gimp_value_set_float_array ($value, $var, $var_len)',
take_value_func => 'gimp_value_take_float_array ($value, $var, $var_len)' },
app, libgimp, libgimpbase, pdb: GimpColorArray as a typedef to… … NULL-terminated array of GeglColor is now a boxed type usable in PDB.
2023-12-27 00:07:19 +08:00
colorarray => { name => 'COLOR_ARRAY',
gtype => 'GIMP_TYPE_COLOR_ARRAY',
type => 'GeglColor **',
const_type => 'const GeglColor **',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
init_value => 'NULL',
app, libgimp, libgimpbase, pdb: GimpColorArray as a typedef to… … NULL-terminated array of GeglColor is now a boxed type usable in PDB.
2023-12-27 00:07:19 +08:00
in_annotate => '(array zero-terminated=1)',
out_annotate => '(array zero-terminated=1) (transfer full)',
get_value_func => '$var = g_value_get_boxed ($value)',
dup_value_func => '$var = gimp_color_array_copy (g_value_get_boxed (gimp_value_array_index ($value)))',
set_value_func => 'g_value_set_boxed ($value, $var)',
take_value_func => 'g_value_take_boxed ($value, $var)' },
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
pdb, libgimp: change all generated ID array return values to object arrays and remove the manual libgimp wrappers which now have the same signature as the generated functions.
2019-09-05 18:57:43 +08:00
imagearray => { name => 'IMAGEARRAY',
gtype => 'GIMP_TYPE_OBJECT_ARRAY',
type => 'GimpImage **',
const_type => 'const GimpImage **',
array => 1,
init_value => 'NULL',
in_annotate => '(element-type GimpImage)',
out_annotate => '(element-type GimpImage) (transfer container)',
pdb: proper conversions for object arrays in PDB.
2020-05-07 19:03:11 +08:00
get_value_func => '$var = (const GimpImage **) gimp_value_get_object_array ($value)',
app, libgimp*, pdb, plug-ins: use g_memdup2() instead of g_memdup() Since it appeared with GLib 2.68.0, we could not change this until we bumped the dependency which has only become possible a few days ago (since Debian testing is our baseline for dependency bumps). Cf. previous commit. As this is a drop-in replacement (just a guint parameter changed to gsize to avoid integer overflow), search-and-replace with: > sed -i 's/g_memdup\>/g_memdup2/g' `grep -rIl 'g_memdup\>' *` … followed by a few manual alignment tweaks when necessary. This gets rid of the many deprecation warnings which we had lately when building with a recent GLib version.
2021-08-26 23:18:32 +08:00
dup_value_func => '{ GimpObjectArray *a = g_value_get_boxed (gimp_value_array_index ($value)); if (a) $var = g_memdup2 (a->data, a->length * sizeof (gpointer)); }',
pdb, libgimp: change all generated ID array return values to object arrays and remove the manual libgimp wrappers which now have the same signature as the generated functions.
2019-09-05 18:57:43 +08:00
set_value_func => 'gimp_value_set_object_array ($value, GIMP_TYPE_IMAGE, (GObject **) $var, $var_len)',
take_value_func => 'gimp_value_take_object_array ($value, GIMP_TYPE_IMAGE, (GObject **) $var, $var_len)' },
itemarray => { name => 'ITEMARRAY',
gtype => 'GIMP_TYPE_OBJECT_ARRAY',
type => 'GimpItem **',
const_type => 'const GimpItem **',
array => 1,
init_value => 'NULL',
in_annotate => '(element-type GimpItem)',
out_annotate => '(element-type GimpItem) (transfer container)',
pdb: proper conversions for object arrays in PDB.
2020-05-07 19:03:11 +08:00
get_value_func => '$var = (const GimpItem **) gimp_value_get_object_array ($value)',
app, libgimp*, pdb, plug-ins: use g_memdup2() instead of g_memdup() Since it appeared with GLib 2.68.0, we could not change this until we bumped the dependency which has only become possible a few days ago (since Debian testing is our baseline for dependency bumps). Cf. previous commit. As this is a drop-in replacement (just a guint parameter changed to gsize to avoid integer overflow), search-and-replace with: > sed -i 's/g_memdup\>/g_memdup2/g' `grep -rIl 'g_memdup\>' *` … followed by a few manual alignment tweaks when necessary. This gets rid of the many deprecation warnings which we had lately when building with a recent GLib version.
2021-08-26 23:18:32 +08:00
dup_value_func => '{ GimpObjectArray *a = g_value_get_boxed (gimp_value_array_index ($value)); if (a) $var = g_memdup2 (a->data, a->length * sizeof (gpointer)); }',
pdb, libgimp: change all generated ID array return values to object arrays and remove the manual libgimp wrappers which now have the same signature as the generated functions.
2019-09-05 18:57:43 +08:00
set_value_func => 'gimp_value_set_object_array ($value, GIMP_TYPE_ITEM, (GObject **) $var, $var_len)',
take_value_func => 'gimp_value_take_object_array ($value, GIMP_TYPE_ITEM, (GObject **) $var, $var_len)' },
layerarray => { name => 'LAYERARRAY',
gtype => 'GIMP_TYPE_OBJECT_ARRAY',
type => 'GimpLayer **',
const_type => 'const GimpLayer **',
array => 1,
init_value => 'NULL',
in_annotate => '(element-type GimpLayer)',
out_annotate => '(element-type GimpLayer) (transfer container)',
pdb: proper conversions for object arrays in PDB.
2020-05-07 19:03:11 +08:00
get_value_func => '$var = (const GimpLayer **) gimp_value_get_object_array ($value)',
app, libgimp*, pdb, plug-ins: use g_memdup2() instead of g_memdup() Since it appeared with GLib 2.68.0, we could not change this until we bumped the dependency which has only become possible a few days ago (since Debian testing is our baseline for dependency bumps). Cf. previous commit. As this is a drop-in replacement (just a guint parameter changed to gsize to avoid integer overflow), search-and-replace with: > sed -i 's/g_memdup\>/g_memdup2/g' `grep -rIl 'g_memdup\>' *` … followed by a few manual alignment tweaks when necessary. This gets rid of the many deprecation warnings which we had lately when building with a recent GLib version.
2021-08-26 23:18:32 +08:00
dup_value_func => '{ GimpObjectArray *a = g_value_get_boxed (gimp_value_array_index ($value)); if (a) $var = g_memdup2 (a->data, a->length * sizeof (gpointer)); }',
pdb, libgimp: change all generated ID array return values to object arrays and remove the manual libgimp wrappers which now have the same signature as the generated functions.
2019-09-05 18:57:43 +08:00
set_value_func => 'gimp_value_set_object_array ($value, GIMP_TYPE_LAYER, (GObject **) $var, $var_len)',
take_value_func => 'gimp_value_take_object_array ($value, GIMP_TYPE_LAYER, (GObject **) $var, $var_len)' },
channelarray => { name => 'CHANNELARRAY',
gtype => 'GIMP_TYPE_OBJECT_ARRAY',
type => 'GimpChannel **',
const_type => 'const GimpChannel **',
array => 1,
init_value => 'NULL',
in_annotate => '(element-type GimpChannel)',
out_annotate => '(element-type GimpChannel) (transfer container)',
app, pdb: fix a few "incompatible pointer type" conversions. That's the problem when there are still too many old warnings hiding the new ones!
2022-10-21 00:56:24 +08:00
get_value_func => '$var = (const GimpChannel **) gimp_value_get_object_array ($value)',
app, libgimp*, pdb, plug-ins: use g_memdup2() instead of g_memdup() Since it appeared with GLib 2.68.0, we could not change this until we bumped the dependency which has only become possible a few days ago (since Debian testing is our baseline for dependency bumps). Cf. previous commit. As this is a drop-in replacement (just a guint parameter changed to gsize to avoid integer overflow), search-and-replace with: > sed -i 's/g_memdup\>/g_memdup2/g' `grep -rIl 'g_memdup\>' *` … followed by a few manual alignment tweaks when necessary. This gets rid of the many deprecation warnings which we had lately when building with a recent GLib version.
2021-08-26 23:18:32 +08:00
dup_value_func => '{ GimpObjectArray *a = g_value_get_boxed (gimp_value_array_index ($value)); if (a) $var = g_memdup2 (a->data, a->length * sizeof (gpointer)); }',
pdb, libgimp: change all generated ID array return values to object arrays and remove the manual libgimp wrappers which now have the same signature as the generated functions.
2019-09-05 18:57:43 +08:00
set_value_func => 'gimp_value_set_object_array ($value, GIMP_TYPE_CHANNEL, (GObject **) $var, $var_len)',
take_value_func => 'gimp_value_take_object_array ($value, GIMP_TYPE_CHANNEL, (GObject **) $var, $var_len)' },
libgimp, app, pdb: Rename GimpVectors to GimpPath This commit renames the GimpVectors object to GimpPath in both app/core and in libgimp. It also renames the files to gimppath.[ch] and updates the relevant build and translation files. There are still outstanding gimp_vectors_* () functions on the app side that need to be renamed in a subsequent commit.
2024-07-12 14:16:25 +08:00
patharray => { name => 'PATHARRAY',
pdb, libgimp: change all generated ID array return values to object arrays and remove the manual libgimp wrappers which now have the same signature as the generated functions.
2019-09-05 18:57:43 +08:00
gtype => 'GIMP_TYPE_OBJECT_ARRAY',
libgimp, app, pdb: Rename GimpVectors to GimpPath This commit renames the GimpVectors object to GimpPath in both app/core and in libgimp. It also renames the files to gimppath.[ch] and updates the relevant build and translation files. There are still outstanding gimp_vectors_* () functions on the app side that need to be renamed in a subsequent commit.
2024-07-12 14:16:25 +08:00
type => 'GimpPath **',
const_type => 'const GimpPath **',
pdb, libgimp: change all generated ID array return values to object arrays and remove the manual libgimp wrappers which now have the same signature as the generated functions.
2019-09-05 18:57:43 +08:00
array => 1,
init_value => 'NULL',
libgimp, app, pdb: Rename GimpVectors to GimpPath This commit renames the GimpVectors object to GimpPath in both app/core and in libgimp. It also renames the files to gimppath.[ch] and updates the relevant build and translation files. There are still outstanding gimp_vectors_* () functions on the app side that need to be renamed in a subsequent commit.
2024-07-12 14:16:25 +08:00
in_annotate => '(element-type GimpPath)',
out_annotate => '(element-type GimpPath) (transfer container)',
get_value_func => '$var = (const GimpPath **) gimp_value_get_object_array ($value)',
app, libgimp*, pdb, plug-ins: use g_memdup2() instead of g_memdup() Since it appeared with GLib 2.68.0, we could not change this until we bumped the dependency which has only become possible a few days ago (since Debian testing is our baseline for dependency bumps). Cf. previous commit. As this is a drop-in replacement (just a guint parameter changed to gsize to avoid integer overflow), search-and-replace with: > sed -i 's/g_memdup\>/g_memdup2/g' `grep -rIl 'g_memdup\>' *` … followed by a few manual alignment tweaks when necessary. This gets rid of the many deprecation warnings which we had lately when building with a recent GLib version.
2021-08-26 23:18:32 +08:00
dup_value_func => '{ GimpObjectArray *a = g_value_get_boxed (gimp_value_array_index ($value)); if (a) $var = g_memdup2 (a->data, a->length * sizeof (gpointer)); }',
libgimp, app, pdb: Rename GimpVectors to GimpPath This commit renames the GimpVectors object to GimpPath in both app/core and in libgimp. It also renames the files to gimppath.[ch] and updates the relevant build and translation files. There are still outstanding gimp_vectors_* () functions on the app side that need to be renamed in a subsequent commit.
2024-07-12 14:16:25 +08:00
set_value_func => 'gimp_value_set_object_array ($value, GIMP_TYPE_PATH, (GObject **) $var, $var_len)',
take_value_func => 'gimp_value_take_object_array ($value, GIMP_TYPE_PATH, (GObject **) $var, $var_len)' },
pdb, libgimp: change all generated ID array return values to object arrays and remove the manual libgimp wrappers which now have the same signature as the generated functions.
2019-09-05 18:57:43 +08:00
app, libgimp, pdb: new PDB function gimp_fonts_get_by_name(). It returns all the fonts (possibly more than 1) with a given name. I left the function gimp_font_get_by_name() as a utility when one don't want to choose (or is not able anyway, e.g. a script with minimal information), though I wondered if we should not simplify with a single function (the new one, which is the correct one now that it is possible to have several fonts with a given name). It is easy to test with fonts named the same. For instance I could find 2 different fonts, both named 'Holiday'. This call in the Python console returns both: > Gimp.fonts_get_by_name('Holiday') As part of this commit, I also implemented resource arrays (or subtype arrays) as PDB arguments and return types.
2023-10-03 05:22:49 +08:00
resourcearray => { name => 'RESOURCEARRAY',
gtype => 'GIMP_TYPE_OBJECT_ARRAY',
type => 'GimpResource **',
const_type => 'const GimpResource **',
array => 1,
init_value => 'NULL',
in_annotate => '(element-type GimpResource)',
out_annotate => '(element-type GimpResource) (transfer container)',
get_value_func => '$var = (const GimpResource **) gimp_value_get_object_array ($value)',
dup_value_func => '{ GimpObjectArray *a = g_value_get_boxed (gimp_value_array_index ($value)); if (a) $var = g_memdup2 (a->data, a->length * sizeof (gpointer)); }',
set_value_func => 'gimp_value_set_object_array ($value, GIMP_TYPE_RESOURCE, (GObject **) $var, $var_len)',
take_value_func => 'gimp_value_take_object_array ($value, GIMP_TYPE_RESOURCE, (GObject **) $var, $var_len)' },
brusharray => { name => 'BRUSHARRAY',
gtype => 'GIMP_TYPE_OBJECT_ARRAY',
type => 'GimpBrush **',
const_type => 'const GimpBrush **',
array => 1,
init_value => 'NULL',
in_annotate => '(element-type GimpBrush)',
out_annotate => '(element-type GimpBrush) (transfer container)',
get_value_func => '$var = (const GimpBrush **) gimp_value_get_object_array ($value)',
dup_value_func => '{ GimpObjectArray *a = g_value_get_boxed (gimp_value_array_index ($value)); if (a) $var = g_memdup2 (a->data, a->length * sizeof (gpointer)); }',
set_value_func => 'gimp_value_set_object_array ($value, GIMP_TYPE_BRUSH, (GObject **) $var, $var_len)',
take_value_func => 'gimp_value_take_object_array ($value, GIMP_TYPE_BRUSH, (GObject **) $var, $var_len)' },
fontarray => { name => 'FONTARRAY',
gtype => 'GIMP_TYPE_OBJECT_ARRAY',
type => 'GimpFont **',
const_type => 'const GimpFont **',
array => 1,
init_value => 'NULL',
in_annotate => '(element-type GimpFont)',
out_annotate => '(element-type GimpFont) (transfer container)',
get_value_func => '$var = (const GimpFont **) gimp_value_get_object_array ($value)',
dup_value_func => '{ GimpObjectArray *a = g_value_get_boxed (gimp_value_array_index ($value)); if (a) $var = g_memdup2 (a->data, a->length * sizeof (gpointer)); }',
set_value_func => 'gimp_value_set_object_array ($value, GIMP_TYPE_FONT, (GObject **) $var, $var_len)',
take_value_func => 'gimp_value_take_object_array ($value, GIMP_TYPE_FONT, (GObject **) $var, $var_len)' },
gradientarray => { name => 'GRADIENTARRAY',
gtype => 'GIMP_TYPE_OBJECT_ARRAY',
type => 'GimpGradient **',
const_type => 'const GimpGradient **',
array => 1,
init_value => 'NULL',
in_annotate => '(element-type GimpGradient)',
out_annotate => '(element-type GimpGradient) (transfer container)',
get_value_func => '$var = (const GimpGradient **) gimp_value_get_object_array ($value)',
dup_value_func => '{ GimpObjectArray *a = g_value_get_boxed (gimp_value_array_index ($value)); if (a) $var = g_memdup2 (a->data, a->length * sizeof (gpointer)); }',
set_value_func => 'gimp_value_set_object_array ($value, GIMP_TYPE_GRADIENT, (GObject **) $var, $var_len)',
take_value_func => 'gimp_value_take_object_array ($value, GIMP_TYPE_GRADIENT, (GObject **) $var, $var_len)' },
palettearray => { name => 'PALETTEARRAY',
gtype => 'GIMP_TYPE_OBJECT_ARRAY',
type => 'GimpPalette **',
const_type => 'const GimpPalette **',
array => 1,
init_value => 'NULL',
in_annotate => '(element-type GimpPalette)',
out_annotate => '(element-type GimpPalette) (transfer container)',
get_value_func => '$var = (const GimpPalette **) gimp_value_get_object_array ($value)',
dup_value_func => '{ GimpObjectArray *a = g_value_get_boxed (gimp_value_array_index ($value)); if (a) $var = g_memdup2 (a->data, a->length * sizeof (gpointer)); }',
set_value_func => 'gimp_value_set_object_array ($value, GIMP_TYPE_PALETTE, (GObject **) $var, $var_len)',
take_value_func => 'gimp_value_take_object_array ($value, GIMP_TYPE_PALETTE, (GObject **) $var, $var_len)' },
patternarray => { name => 'PATTERNARRAY',
gtype => 'GIMP_TYPE_OBJECT_ARRAY',
type => 'GimpPattern **',
const_type => 'const GimpPattern **',
array => 1,
init_value => 'NULL',
in_annotate => '(element-type GimpPattern)',
out_annotate => '(element-type GimpPattern) (transfer container)',
get_value_func => '$var = (const GimpPattern **) gimp_value_get_object_array ($value)',
dup_value_func => '{ GimpObjectArray *a = g_value_get_boxed (gimp_value_array_index ($value)); if (a) $var = g_memdup2 (a->data, a->length * sizeof (gpointer)); }',
set_value_func => 'gimp_value_set_object_array ($value, GIMP_TYPE_PATTERN, (GObject **) $var, $var_len)',
take_value_func => 'gimp_value_take_object_array ($value, GIMP_TYPE_PATTERN, (GObject **) $var, $var_len)' },
libgimp*, pdb: support of GeglColor in the PDB. Eventually this is meant to fully replace GimpRGB (as well as GimpHSV, GimpHSL and GimpCMYK), both in libgimp and in core code, as part of both the space invasion and the API rework. For this first commit, I keep this new object side by side to GimpRGB.
2023-11-04 04:26:51 +08:00
geglcolor => { name => 'GEGLCOLOR',
gtype => 'GEGL_TYPE_COLOR',
type => 'GeglColor *',
const_type => 'GeglColor *',
init_value => 'NULL',
out_annotate => '(transfer full)',
get_value_func => '$var = g_value_get_object ($value)',
dup_value_func => '$var = g_value_dup_object (gimp_value_array_index ($value))',
set_value_func => 'g_value_set_object ($value, $var)',
modules, core, pdb, plug-ins: GeglColor ports More minor ports from GimpRGB to GeglColor. Note that file-mng's GimpRGB code was already dummied out.
2024-03-23 12:10:26 +08:00
take_value_func => 'g_value_take_object ($value, $var)',
headers => [ qw(<cairo.h> "libgimpcolor/gimpcolor.h") ] },
libgimp*, pdb: support of GeglColor in the PDB. Eventually this is meant to fully replace GimpRGB (as well as GimpHSV, GimpHSL and GimpCMYK), both in libgimp and in core code, as part of both the space invasion and the API rework. For this first commit, I keep this new object side by side to GimpRGB.
2023-11-04 04:26:51 +08:00
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
display => { name => 'DISPLAY',
app, libgimp: get rid of all ID GTypes and ID param specs Turn all ID param specs into object param specs (e.g. GimpParamImageID becomes GimpParamImage) and convert between IDs and objects in gimpgpparams.c directly above the the wire protocol, so all of app/, libgimp/ and plug-ins/ can deal directly with objects down to the lowest level and not care about IDs. Use the actual object param specs for procedure arguments and return values again instead of a plain g_param_spec_object() and bring back the none_ok parameter. This implies changing the PDB type checking functions to work on pure integers instead of IDs (one can't check whether object creation is possible if performing that check requires the object to already exist). For example gimp_foo_is_valid() becomes gimp_foo_id_is_valid() and is not involved in automatic object creation magic at the protocol level. Added wrappers which still say gimp_foo_is_valid() and take the respective objects. Adapted all code, and it all becomes nicer and less convoluted, even the generated PDB wrappers in app/ and libgimp/.
2019-08-29 17:25:35 +08:00
gtype => 'GIMP_TYPE_DISPLAY',
pdb, libgimp: now make all ID types classes of their own. No need of is_id_arg() anymore in pdb/lib.pl. Let's reuse the {id} value. Also I had to add an additional trick for GimpDisplay which we will now generate as such in libgimp PDB files, but still need to show as GimpObject on app/pdb/. As previously, only the new classes and the PDB generation for a first step.
2019-08-14 03:36:03 +08:00
type => 'GimpDisplay *',
const_type => 'GimpDisplay *',
app: split GimpDisplay in two classes: GimpDisplay and GimpDisplayImpl GimpDisplay contains only the ID logic and the "gimp" and "config" pointers, and lives in the core. GimpDisplayImpl is a subclass and contains all the actual display stuff. The subclass is only an implementation detail and doesn't appear in any API. Remove all hacks which pass displays as gpointer, GObject or GimpObject through the core, or even lookup its type by name, just use GimpDisplay.
2019-09-04 20:27:18 +08:00
app_type => 'GimpDisplay *',
app_const_type => 'GimpDisplay *',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
init_value => 'NULL',
libgimp: s/gimp_display_new_by_id/gimp_display_get_by_id/ GimpDisplay objects now also belongs to libgimp!
2019-08-15 16:14:38 +08:00
out_annotate => '(transfer none)',
app, libgimp: get rid of all ID GTypes and ID param specs Turn all ID param specs into object param specs (e.g. GimpParamImageID becomes GimpParamImage) and convert between IDs and objects in gimpgpparams.c directly above the the wire protocol, so all of app/, libgimp/ and plug-ins/ can deal directly with objects down to the lowest level and not care about IDs. Use the actual object param specs for procedure arguments and return values again instead of a plain g_param_spec_object() and bring back the none_ok parameter. This implies changing the PDB type checking functions to work on pure integers instead of IDs (one can't check whether object creation is possible if performing that check requires the object to already exist). For example gimp_foo_is_valid() becomes gimp_foo_id_is_valid() and is not involved in automatic object creation magic at the protocol level. Added wrappers which still say gimp_foo_is_valid() and take the respective objects. Adapted all code, and it all becomes nicer and less convoluted, even the generated PDB wrappers in app/ and libgimp/.
2019-08-29 17:25:35 +08:00
get_value_func => '$var = g_value_get_object ($value)',
pdb, libgimp: use GIMP_VALUES_GET,DUP_FOO() in the libgimp PDB wrappers
2019-09-04 08:49:33 +08:00
dup_value_func => '$var = GIMP_VALUES_GET_DISPLAY ($value)',
app, libgimp: get rid of all ID GTypes and ID param specs Turn all ID param specs into object param specs (e.g. GimpParamImageID becomes GimpParamImage) and convert between IDs and objects in gimpgpparams.c directly above the the wire protocol, so all of app/, libgimp/ and plug-ins/ can deal directly with objects down to the lowest level and not care about IDs. Use the actual object param specs for procedure arguments and return values again instead of a plain g_param_spec_object() and bring back the none_ok parameter. This implies changing the PDB type checking functions to work on pure integers instead of IDs (one can't check whether object creation is possible if performing that check requires the object to already exist). For example gimp_foo_is_valid() becomes gimp_foo_id_is_valid() and is not involved in automatic object creation magic at the protocol level. Added wrappers which still say gimp_foo_is_valid() and take the respective objects. Adapted all code, and it all becomes nicer and less convoluted, even the generated PDB wrappers in app/ and libgimp/.
2019-08-29 17:25:35 +08:00
set_value_func => 'g_value_set_object ($value, $var)',
pdb, libgimp: remove double API generation from PDB. All plug-ins got ported. Let's remove support for the old API with IDs instead of objects.
2019-09-03 19:31:27 +08:00
take_value_func => 'g_value_set_object ($value, $var)' },
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
image => { name => 'IMAGE',
app, libgimp: get rid of all ID GTypes and ID param specs Turn all ID param specs into object param specs (e.g. GimpParamImageID becomes GimpParamImage) and convert between IDs and objects in gimpgpparams.c directly above the the wire protocol, so all of app/, libgimp/ and plug-ins/ can deal directly with objects down to the lowest level and not care about IDs. Use the actual object param specs for procedure arguments and return values again instead of a plain g_param_spec_object() and bring back the none_ok parameter. This implies changing the PDB type checking functions to work on pure integers instead of IDs (one can't check whether object creation is possible if performing that check requires the object to already exist). For example gimp_foo_is_valid() becomes gimp_foo_id_is_valid() and is not involved in automatic object creation magic at the protocol level. Added wrappers which still say gimp_foo_is_valid() and take the respective objects. Adapted all code, and it all becomes nicer and less convoluted, even the generated PDB wrappers in app/ and libgimp/.
2019-08-29 17:25:35 +08:00
gtype => 'GIMP_TYPE_IMAGE',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
type => 'GimpImage *',
const_type => 'GimpImage *',
init_value => 'NULL',
libgimp: s/gimp_image_new_by_id()/gimp_image_get_by_id()/ This means that images' ownership is not given to caller in particular. libgimp will now keep a reference of all GimpImage-s it creates and return this same reference if called again. It also means that you can now compare images by pointer comparison (as 2 GimpImage objects representing the same image ID will be equal). Obviously as a side effect, gimp_image_list() is changed to (transfer container) as you must only free the container now, not the elements. Also various other functions creating new images are now (transfer none) too. Long-time plug-ins will have to be taken in consideration in a further step (we currently never free GimpImage for destroyed images in particular).
2019-08-15 16:01:08 +08:00
out_annotate => '(transfer none)',
app, libgimp: get rid of all ID GTypes and ID param specs Turn all ID param specs into object param specs (e.g. GimpParamImageID becomes GimpParamImage) and convert between IDs and objects in gimpgpparams.c directly above the the wire protocol, so all of app/, libgimp/ and plug-ins/ can deal directly with objects down to the lowest level and not care about IDs. Use the actual object param specs for procedure arguments and return values again instead of a plain g_param_spec_object() and bring back the none_ok parameter. This implies changing the PDB type checking functions to work on pure integers instead of IDs (one can't check whether object creation is possible if performing that check requires the object to already exist). For example gimp_foo_is_valid() becomes gimp_foo_id_is_valid() and is not involved in automatic object creation magic at the protocol level. Added wrappers which still say gimp_foo_is_valid() and take the respective objects. Adapted all code, and it all becomes nicer and less convoluted, even the generated PDB wrappers in app/ and libgimp/.
2019-08-29 17:25:35 +08:00
get_value_func => '$var = g_value_get_object ($value)',
pdb, libgimp: use GIMP_VALUES_GET,DUP_FOO() in the libgimp PDB wrappers
2019-09-04 08:49:33 +08:00
dup_value_func => '$var = GIMP_VALUES_GET_IMAGE ($value)',
app, libgimp: get rid of all ID GTypes and ID param specs Turn all ID param specs into object param specs (e.g. GimpParamImageID becomes GimpParamImage) and convert between IDs and objects in gimpgpparams.c directly above the the wire protocol, so all of app/, libgimp/ and plug-ins/ can deal directly with objects down to the lowest level and not care about IDs. Use the actual object param specs for procedure arguments and return values again instead of a plain g_param_spec_object() and bring back the none_ok parameter. This implies changing the PDB type checking functions to work on pure integers instead of IDs (one can't check whether object creation is possible if performing that check requires the object to already exist). For example gimp_foo_is_valid() becomes gimp_foo_id_is_valid() and is not involved in automatic object creation magic at the protocol level. Added wrappers which still say gimp_foo_is_valid() and take the respective objects. Adapted all code, and it all becomes nicer and less convoluted, even the generated PDB wrappers in app/ and libgimp/.
2019-08-29 17:25:35 +08:00
set_value_func => 'g_value_set_object ($value, $var)',
take_value_func => 'g_value_set_object ($value, $var)',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
headers => [ qw("core/gimpimage.h") ] },
item => { name => 'ITEM',
app, libgimp: get rid of all ID GTypes and ID param specs Turn all ID param specs into object param specs (e.g. GimpParamImageID becomes GimpParamImage) and convert between IDs and objects in gimpgpparams.c directly above the the wire protocol, so all of app/, libgimp/ and plug-ins/ can deal directly with objects down to the lowest level and not care about IDs. Use the actual object param specs for procedure arguments and return values again instead of a plain g_param_spec_object() and bring back the none_ok parameter. This implies changing the PDB type checking functions to work on pure integers instead of IDs (one can't check whether object creation is possible if performing that check requires the object to already exist). For example gimp_foo_is_valid() becomes gimp_foo_id_is_valid() and is not involved in automatic object creation magic at the protocol level. Added wrappers which still say gimp_foo_is_valid() and take the respective objects. Adapted all code, and it all becomes nicer and less convoluted, even the generated PDB wrappers in app/ and libgimp/.
2019-08-29 17:25:35 +08:00
gtype => 'GIMP_TYPE_ITEM',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
type => 'GimpItem *',
const_type => 'GimpItem *',
init_value => 'NULL',
libgimp: GimpItem now also belong to libgimp.
2019-08-15 18:12:25 +08:00
out_annotate => '(transfer none)',
app, libgimp: get rid of all ID GTypes and ID param specs Turn all ID param specs into object param specs (e.g. GimpParamImageID becomes GimpParamImage) and convert between IDs and objects in gimpgpparams.c directly above the the wire protocol, so all of app/, libgimp/ and plug-ins/ can deal directly with objects down to the lowest level and not care about IDs. Use the actual object param specs for procedure arguments and return values again instead of a plain g_param_spec_object() and bring back the none_ok parameter. This implies changing the PDB type checking functions to work on pure integers instead of IDs (one can't check whether object creation is possible if performing that check requires the object to already exist). For example gimp_foo_is_valid() becomes gimp_foo_id_is_valid() and is not involved in automatic object creation magic at the protocol level. Added wrappers which still say gimp_foo_is_valid() and take the respective objects. Adapted all code, and it all becomes nicer and less convoluted, even the generated PDB wrappers in app/ and libgimp/.
2019-08-29 17:25:35 +08:00
get_value_func => '$var = g_value_get_object ($value)',
pdb, libgimp: use GIMP_VALUES_GET,DUP_FOO() in the libgimp PDB wrappers
2019-09-04 08:49:33 +08:00
dup_value_func => '$var = GIMP_VALUES_GET_ITEM ($value)',
app, libgimp: get rid of all ID GTypes and ID param specs Turn all ID param specs into object param specs (e.g. GimpParamImageID becomes GimpParamImage) and convert between IDs and objects in gimpgpparams.c directly above the the wire protocol, so all of app/, libgimp/ and plug-ins/ can deal directly with objects down to the lowest level and not care about IDs. Use the actual object param specs for procedure arguments and return values again instead of a plain g_param_spec_object() and bring back the none_ok parameter. This implies changing the PDB type checking functions to work on pure integers instead of IDs (one can't check whether object creation is possible if performing that check requires the object to already exist). For example gimp_foo_is_valid() becomes gimp_foo_id_is_valid() and is not involved in automatic object creation magic at the protocol level. Added wrappers which still say gimp_foo_is_valid() and take the respective objects. Adapted all code, and it all becomes nicer and less convoluted, even the generated PDB wrappers in app/ and libgimp/.
2019-08-29 17:25:35 +08:00
set_value_func => 'g_value_set_object ($value, $var)',
take_value_func => 'g_value_set_object ($value, $var)',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
headers => [ qw("core/gimpitem.h") ] },
layer => { name => 'LAYER',
app, libgimp: get rid of all ID GTypes and ID param specs Turn all ID param specs into object param specs (e.g. GimpParamImageID becomes GimpParamImage) and convert between IDs and objects in gimpgpparams.c directly above the the wire protocol, so all of app/, libgimp/ and plug-ins/ can deal directly with objects down to the lowest level and not care about IDs. Use the actual object param specs for procedure arguments and return values again instead of a plain g_param_spec_object() and bring back the none_ok parameter. This implies changing the PDB type checking functions to work on pure integers instead of IDs (one can't check whether object creation is possible if performing that check requires the object to already exist). For example gimp_foo_is_valid() becomes gimp_foo_id_is_valid() and is not involved in automatic object creation magic at the protocol level. Added wrappers which still say gimp_foo_is_valid() and take the respective objects. Adapted all code, and it all becomes nicer and less convoluted, even the generated PDB wrappers in app/ and libgimp/.
2019-08-29 17:25:35 +08:00
gtype => 'GIMP_TYPE_LAYER',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
type => 'GimpLayer *',
const_type => 'GimpLayer *',
init_value => 'NULL',
libgimp: GimpItem now also belong to libgimp.
2019-08-15 18:12:25 +08:00
out_annotate => '(transfer none)',
app, libgimp: get rid of all ID GTypes and ID param specs Turn all ID param specs into object param specs (e.g. GimpParamImageID becomes GimpParamImage) and convert between IDs and objects in gimpgpparams.c directly above the the wire protocol, so all of app/, libgimp/ and plug-ins/ can deal directly with objects down to the lowest level and not care about IDs. Use the actual object param specs for procedure arguments and return values again instead of a plain g_param_spec_object() and bring back the none_ok parameter. This implies changing the PDB type checking functions to work on pure integers instead of IDs (one can't check whether object creation is possible if performing that check requires the object to already exist). For example gimp_foo_is_valid() becomes gimp_foo_id_is_valid() and is not involved in automatic object creation magic at the protocol level. Added wrappers which still say gimp_foo_is_valid() and take the respective objects. Adapted all code, and it all becomes nicer and less convoluted, even the generated PDB wrappers in app/ and libgimp/.
2019-08-29 17:25:35 +08:00
get_value_func => '$var = g_value_get_object ($value)',
pdb, libgimp: use GIMP_VALUES_GET,DUP_FOO() in the libgimp PDB wrappers
2019-09-04 08:49:33 +08:00
dup_value_func => '$var = GIMP_VALUES_GET_LAYER ($value)',
app, libgimp: get rid of all ID GTypes and ID param specs Turn all ID param specs into object param specs (e.g. GimpParamImageID becomes GimpParamImage) and convert between IDs and objects in gimpgpparams.c directly above the the wire protocol, so all of app/, libgimp/ and plug-ins/ can deal directly with objects down to the lowest level and not care about IDs. Use the actual object param specs for procedure arguments and return values again instead of a plain g_param_spec_object() and bring back the none_ok parameter. This implies changing the PDB type checking functions to work on pure integers instead of IDs (one can't check whether object creation is possible if performing that check requires the object to already exist). For example gimp_foo_is_valid() becomes gimp_foo_id_is_valid() and is not involved in automatic object creation magic at the protocol level. Added wrappers which still say gimp_foo_is_valid() and take the respective objects. Adapted all code, and it all becomes nicer and less convoluted, even the generated PDB wrappers in app/ and libgimp/.
2019-08-29 17:25:35 +08:00
set_value_func => 'g_value_set_object ($value, $var)',
take_value_func => 'g_value_set_object ($value, $var)',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
headers => [ qw("core/gimplayer.h") ] },
app, libgimp, pdb, plug-ins: new GimpTextLayer class in libgimp. Now text layers are proper types, which means that the binding API will also be nicer (e.g. `txt_layer.set_text('hello world')` in Python). This commit also adds the param specs allowing to create plug-in procedures with text layer parameters. Finally it fixes the few calls in file-pdf-save (apparently the only plug-in using specific text layer API right now) with explicit type conversion.
2022-09-30 22:21:47 +08:00
text_layer => { name => 'TEXT_LAYER',
gtype => 'GIMP_TYPE_TEXT_LAYER',
type => 'GimpTextLayer *',
const_type => 'GimpTextLayer *',
init_value => 'NULL',
out_annotate => '(transfer none)',
get_value_func => '$var = g_value_get_object ($value)',
dup_value_func => '$var = GIMP_VALUES_GET_TEXT_LAYER ($value)',
set_value_func => 'g_value_set_object ($value, $var)',
take_value_func => 'g_value_set_object ($value, $var)',
headers => [ qw("text/gimptextlayer.h") ] },
app, libgimp, pdb, plug-ins: new GimpGroupLayer class in libgimp. Also: - renaming gimp_layer_group_new() to gimp_group_layer_new() in order to keep the same name as in core code (i.e. GimpGroupLayer, not GimpLayerGroup). - renaming gimp_image_merge_layer_group() to gimp_group_layer_merge() - new functions: gimp_procedure_add_group_layer_argument(), gimp_procedure_add_group_layer_aux_argument() and gimp_procedure_add_group_layer_return_value(). This can be tested, e.g. in Python with these calls: ```py i = Gimp.get_images()[0] g = Gimp.GroupLayer.new(i, "hello") i.insert_layer(g, None, 1) g2 = Gimp.GroupLayer.new(i, "world") i.insert_layer(g2, g, 1) g.merge() ``` This was work started long ago, stored in an old stash which I finally finish now! :-)
2024-07-06 23:24:11 +08:00
group_layer => { name => 'GROUP_LAYER',
gtype => 'GIMP_TYPE_GROUP_LAYER',
type => 'GimpGroupLayer *',
const_type => 'GimpGroupLayer *',
init_value => 'NULL',
out_annotate => '(transfer none)',
get_value_func => '$var = g_value_get_object ($value)',
dup_value_func => '$var = GIMP_VALUES_GET_GROUP_LAYER ($value)',
set_value_func => 'g_value_set_object ($value, $var)',
take_value_func => 'g_value_set_object ($value, $var)',
headers => [ qw("core/gimpgrouplayer.h") ] },
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
channel => { name => 'CHANNEL',
app, libgimp: get rid of all ID GTypes and ID param specs Turn all ID param specs into object param specs (e.g. GimpParamImageID becomes GimpParamImage) and convert between IDs and objects in gimpgpparams.c directly above the the wire protocol, so all of app/, libgimp/ and plug-ins/ can deal directly with objects down to the lowest level and not care about IDs. Use the actual object param specs for procedure arguments and return values again instead of a plain g_param_spec_object() and bring back the none_ok parameter. This implies changing the PDB type checking functions to work on pure integers instead of IDs (one can't check whether object creation is possible if performing that check requires the object to already exist). For example gimp_foo_is_valid() becomes gimp_foo_id_is_valid() and is not involved in automatic object creation magic at the protocol level. Added wrappers which still say gimp_foo_is_valid() and take the respective objects. Adapted all code, and it all becomes nicer and less convoluted, even the generated PDB wrappers in app/ and libgimp/.
2019-08-29 17:25:35 +08:00
gtype => 'GIMP_TYPE_CHANNEL',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
type => 'GimpChannel *',
const_type => 'GimpChannel *',
init_value => 'NULL',
libgimp: GimpItem now also belong to libgimp.
2019-08-15 18:12:25 +08:00
out_annotate => '(transfer none)',
app, libgimp: get rid of all ID GTypes and ID param specs Turn all ID param specs into object param specs (e.g. GimpParamImageID becomes GimpParamImage) and convert between IDs and objects in gimpgpparams.c directly above the the wire protocol, so all of app/, libgimp/ and plug-ins/ can deal directly with objects down to the lowest level and not care about IDs. Use the actual object param specs for procedure arguments and return values again instead of a plain g_param_spec_object() and bring back the none_ok parameter. This implies changing the PDB type checking functions to work on pure integers instead of IDs (one can't check whether object creation is possible if performing that check requires the object to already exist). For example gimp_foo_is_valid() becomes gimp_foo_id_is_valid() and is not involved in automatic object creation magic at the protocol level. Added wrappers which still say gimp_foo_is_valid() and take the respective objects. Adapted all code, and it all becomes nicer and less convoluted, even the generated PDB wrappers in app/ and libgimp/.
2019-08-29 17:25:35 +08:00
get_value_func => '$var = g_value_get_object ($value)',
pdb, libgimp: use GIMP_VALUES_GET,DUP_FOO() in the libgimp PDB wrappers
2019-09-04 08:49:33 +08:00
dup_value_func => '$var = GIMP_VALUES_GET_CHANNEL ($value)',
app, libgimp: get rid of all ID GTypes and ID param specs Turn all ID param specs into object param specs (e.g. GimpParamImageID becomes GimpParamImage) and convert between IDs and objects in gimpgpparams.c directly above the the wire protocol, so all of app/, libgimp/ and plug-ins/ can deal directly with objects down to the lowest level and not care about IDs. Use the actual object param specs for procedure arguments and return values again instead of a plain g_param_spec_object() and bring back the none_ok parameter. This implies changing the PDB type checking functions to work on pure integers instead of IDs (one can't check whether object creation is possible if performing that check requires the object to already exist). For example gimp_foo_is_valid() becomes gimp_foo_id_is_valid() and is not involved in automatic object creation magic at the protocol level. Added wrappers which still say gimp_foo_is_valid() and take the respective objects. Adapted all code, and it all becomes nicer and less convoluted, even the generated PDB wrappers in app/ and libgimp/.
2019-08-29 17:25:35 +08:00
set_value_func => 'g_value_set_object ($value, $var)',
take_value_func => 'g_value_set_object ($value, $var)',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
headers => [ qw("core/gimpchannel.h") ] },
drawable => { name => 'DRAWABLE',
app, libgimp: get rid of all ID GTypes and ID param specs Turn all ID param specs into object param specs (e.g. GimpParamImageID becomes GimpParamImage) and convert between IDs and objects in gimpgpparams.c directly above the the wire protocol, so all of app/, libgimp/ and plug-ins/ can deal directly with objects down to the lowest level and not care about IDs. Use the actual object param specs for procedure arguments and return values again instead of a plain g_param_spec_object() and bring back the none_ok parameter. This implies changing the PDB type checking functions to work on pure integers instead of IDs (one can't check whether object creation is possible if performing that check requires the object to already exist). For example gimp_foo_is_valid() becomes gimp_foo_id_is_valid() and is not involved in automatic object creation magic at the protocol level. Added wrappers which still say gimp_foo_is_valid() and take the respective objects. Adapted all code, and it all becomes nicer and less convoluted, even the generated PDB wrappers in app/ and libgimp/.
2019-08-29 17:25:35 +08:00
gtype => 'GIMP_TYPE_DRAWABLE',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
type => 'GimpDrawable *',
const_type => 'GimpDrawable *',
init_value => 'NULL',
libgimp: GimpItem now also belong to libgimp.
2019-08-15 18:12:25 +08:00
out_annotate => '(transfer none)',
app, libgimp: get rid of all ID GTypes and ID param specs Turn all ID param specs into object param specs (e.g. GimpParamImageID becomes GimpParamImage) and convert between IDs and objects in gimpgpparams.c directly above the the wire protocol, so all of app/, libgimp/ and plug-ins/ can deal directly with objects down to the lowest level and not care about IDs. Use the actual object param specs for procedure arguments and return values again instead of a plain g_param_spec_object() and bring back the none_ok parameter. This implies changing the PDB type checking functions to work on pure integers instead of IDs (one can't check whether object creation is possible if performing that check requires the object to already exist). For example gimp_foo_is_valid() becomes gimp_foo_id_is_valid() and is not involved in automatic object creation magic at the protocol level. Added wrappers which still say gimp_foo_is_valid() and take the respective objects. Adapted all code, and it all becomes nicer and less convoluted, even the generated PDB wrappers in app/ and libgimp/.
2019-08-29 17:25:35 +08:00
get_value_func => '$var = g_value_get_object ($value)',
pdb, libgimp: use GIMP_VALUES_GET,DUP_FOO() in the libgimp PDB wrappers
2019-09-04 08:49:33 +08:00
dup_value_func => '$var = GIMP_VALUES_GET_DRAWABLE ($value)',
app, libgimp: get rid of all ID GTypes and ID param specs Turn all ID param specs into object param specs (e.g. GimpParamImageID becomes GimpParamImage) and convert between IDs and objects in gimpgpparams.c directly above the the wire protocol, so all of app/, libgimp/ and plug-ins/ can deal directly with objects down to the lowest level and not care about IDs. Use the actual object param specs for procedure arguments and return values again instead of a plain g_param_spec_object() and bring back the none_ok parameter. This implies changing the PDB type checking functions to work on pure integers instead of IDs (one can't check whether object creation is possible if performing that check requires the object to already exist). For example gimp_foo_is_valid() becomes gimp_foo_id_is_valid() and is not involved in automatic object creation magic at the protocol level. Added wrappers which still say gimp_foo_is_valid() and take the respective objects. Adapted all code, and it all becomes nicer and less convoluted, even the generated PDB wrappers in app/ and libgimp/.
2019-08-29 17:25:35 +08:00
set_value_func => 'g_value_set_object ($value, $var)',
take_value_func => 'g_value_set_object ($value, $var)',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
headers => [ qw("core/gimpdrawable.h") ] },
selection => { name => 'SELECTION',
app, libgimp: get rid of all ID GTypes and ID param specs Turn all ID param specs into object param specs (e.g. GimpParamImageID becomes GimpParamImage) and convert between IDs and objects in gimpgpparams.c directly above the the wire protocol, so all of app/, libgimp/ and plug-ins/ can deal directly with objects down to the lowest level and not care about IDs. Use the actual object param specs for procedure arguments and return values again instead of a plain g_param_spec_object() and bring back the none_ok parameter. This implies changing the PDB type checking functions to work on pure integers instead of IDs (one can't check whether object creation is possible if performing that check requires the object to already exist). For example gimp_foo_is_valid() becomes gimp_foo_id_is_valid() and is not involved in automatic object creation magic at the protocol level. Added wrappers which still say gimp_foo_is_valid() and take the respective objects. Adapted all code, and it all becomes nicer and less convoluted, even the generated PDB wrappers in app/ and libgimp/.
2019-08-29 17:25:35 +08:00
gtype => 'GIMP_TYPE_SELECTION',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
type => 'GimpSelection *',
const_type => 'GimpSelection *',
init_value => 'NULL',
libgimp: GimpItem now also belong to libgimp.
2019-08-15 18:12:25 +08:00
out_annotate => '(transfer none)',
app, libgimp: get rid of all ID GTypes and ID param specs Turn all ID param specs into object param specs (e.g. GimpParamImageID becomes GimpParamImage) and convert between IDs and objects in gimpgpparams.c directly above the the wire protocol, so all of app/, libgimp/ and plug-ins/ can deal directly with objects down to the lowest level and not care about IDs. Use the actual object param specs for procedure arguments and return values again instead of a plain g_param_spec_object() and bring back the none_ok parameter. This implies changing the PDB type checking functions to work on pure integers instead of IDs (one can't check whether object creation is possible if performing that check requires the object to already exist). For example gimp_foo_is_valid() becomes gimp_foo_id_is_valid() and is not involved in automatic object creation magic at the protocol level. Added wrappers which still say gimp_foo_is_valid() and take the respective objects. Adapted all code, and it all becomes nicer and less convoluted, even the generated PDB wrappers in app/ and libgimp/.
2019-08-29 17:25:35 +08:00
get_value_func => '$var = g_value_get_object ($value)',
pdb, libgimp: use GIMP_VALUES_GET,DUP_FOO() in the libgimp PDB wrappers
2019-09-04 08:49:33 +08:00
dup_value_func => '$var = GIMP_VALUES_GET_SELECTION ($value)',
app, libgimp: get rid of all ID GTypes and ID param specs Turn all ID param specs into object param specs (e.g. GimpParamImageID becomes GimpParamImage) and convert between IDs and objects in gimpgpparams.c directly above the the wire protocol, so all of app/, libgimp/ and plug-ins/ can deal directly with objects down to the lowest level and not care about IDs. Use the actual object param specs for procedure arguments and return values again instead of a plain g_param_spec_object() and bring back the none_ok parameter. This implies changing the PDB type checking functions to work on pure integers instead of IDs (one can't check whether object creation is possible if performing that check requires the object to already exist). For example gimp_foo_is_valid() becomes gimp_foo_id_is_valid() and is not involved in automatic object creation magic at the protocol level. Added wrappers which still say gimp_foo_is_valid() and take the respective objects. Adapted all code, and it all becomes nicer and less convoluted, even the generated PDB wrappers in app/ and libgimp/.
2019-08-29 17:25:35 +08:00
set_value_func => 'g_value_set_object ($value, $var)',
take_value_func => 'g_value_set_object ($value, $var)',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
headers => [ qw("core/gimpselection.h") ] },
layer_mask => { name => 'CHANNEL',
app, libgimp: get rid of all ID GTypes and ID param specs Turn all ID param specs into object param specs (e.g. GimpParamImageID becomes GimpParamImage) and convert between IDs and objects in gimpgpparams.c directly above the the wire protocol, so all of app/, libgimp/ and plug-ins/ can deal directly with objects down to the lowest level and not care about IDs. Use the actual object param specs for procedure arguments and return values again instead of a plain g_param_spec_object() and bring back the none_ok parameter. This implies changing the PDB type checking functions to work on pure integers instead of IDs (one can't check whether object creation is possible if performing that check requires the object to already exist). For example gimp_foo_is_valid() becomes gimp_foo_id_is_valid() and is not involved in automatic object creation magic at the protocol level. Added wrappers which still say gimp_foo_is_valid() and take the respective objects. Adapted all code, and it all becomes nicer and less convoluted, even the generated PDB wrappers in app/ and libgimp/.
2019-08-29 17:25:35 +08:00
gtype => 'GIMP_TYPE_LAYER_MASK',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
type => 'GimpLayerMask *',
const_type => 'GimpLayerMask *',
init_value => 'NULL',
libgimp: GimpItem now also belong to libgimp.
2019-08-15 18:12:25 +08:00
out_annotate => '(transfer none)',
app, libgimp: get rid of all ID GTypes and ID param specs Turn all ID param specs into object param specs (e.g. GimpParamImageID becomes GimpParamImage) and convert between IDs and objects in gimpgpparams.c directly above the the wire protocol, so all of app/, libgimp/ and plug-ins/ can deal directly with objects down to the lowest level and not care about IDs. Use the actual object param specs for procedure arguments and return values again instead of a plain g_param_spec_object() and bring back the none_ok parameter. This implies changing the PDB type checking functions to work on pure integers instead of IDs (one can't check whether object creation is possible if performing that check requires the object to already exist). For example gimp_foo_is_valid() becomes gimp_foo_id_is_valid() and is not involved in automatic object creation magic at the protocol level. Added wrappers which still say gimp_foo_is_valid() and take the respective objects. Adapted all code, and it all becomes nicer and less convoluted, even the generated PDB wrappers in app/ and libgimp/.
2019-08-29 17:25:35 +08:00
get_value_func => '$var = g_value_get_object ($value)',
pdb, libgimp: use GIMP_VALUES_GET,DUP_FOO() in the libgimp PDB wrappers
2019-09-04 08:49:33 +08:00
dup_value_func => '$var = GIMP_VALUES_GET_LAYER_MASK ($value)',
app, libgimp: get rid of all ID GTypes and ID param specs Turn all ID param specs into object param specs (e.g. GimpParamImageID becomes GimpParamImage) and convert between IDs and objects in gimpgpparams.c directly above the the wire protocol, so all of app/, libgimp/ and plug-ins/ can deal directly with objects down to the lowest level and not care about IDs. Use the actual object param specs for procedure arguments and return values again instead of a plain g_param_spec_object() and bring back the none_ok parameter. This implies changing the PDB type checking functions to work on pure integers instead of IDs (one can't check whether object creation is possible if performing that check requires the object to already exist). For example gimp_foo_is_valid() becomes gimp_foo_id_is_valid() and is not involved in automatic object creation magic at the protocol level. Added wrappers which still say gimp_foo_is_valid() and take the respective objects. Adapted all code, and it all becomes nicer and less convoluted, even the generated PDB wrappers in app/ and libgimp/.
2019-08-29 17:25:35 +08:00
set_value_func => 'g_value_set_object ($value, $var)',
take_value_func => 'g_value_set_object ($value, $var)',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
headers => [ qw("core/gimplayermask.h") ] },
libgimp, app, pdb: Rename GimpVectors to GimpPath This commit renames the GimpVectors object to GimpPath in both app/core and in libgimp. It also renames the files to gimppath.[ch] and updates the relevant build and translation files. There are still outstanding gimp_vectors_* () functions on the app side that need to be renamed in a subsequent commit.
2024-07-12 14:16:25 +08:00
path => { name => 'PATH',
gtype => 'GIMP_TYPE_PATH',
type => 'GimpPath *',
const_type => 'GimpPath *',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
init_value => 'NULL',
libgimp: GimpItem now also belong to libgimp.
2019-08-15 18:12:25 +08:00
out_annotate => '(transfer none)',
app, libgimp: get rid of all ID GTypes and ID param specs Turn all ID param specs into object param specs (e.g. GimpParamImageID becomes GimpParamImage) and convert between IDs and objects in gimpgpparams.c directly above the the wire protocol, so all of app/, libgimp/ and plug-ins/ can deal directly with objects down to the lowest level and not care about IDs. Use the actual object param specs for procedure arguments and return values again instead of a plain g_param_spec_object() and bring back the none_ok parameter. This implies changing the PDB type checking functions to work on pure integers instead of IDs (one can't check whether object creation is possible if performing that check requires the object to already exist). For example gimp_foo_is_valid() becomes gimp_foo_id_is_valid() and is not involved in automatic object creation magic at the protocol level. Added wrappers which still say gimp_foo_is_valid() and take the respective objects. Adapted all code, and it all becomes nicer and less convoluted, even the generated PDB wrappers in app/ and libgimp/.
2019-08-29 17:25:35 +08:00
get_value_func => '$var = g_value_get_object ($value)',
libgimp, app, pdb: Rename GimpVectors to GimpPath This commit renames the GimpVectors object to GimpPath in both app/core and in libgimp. It also renames the files to gimppath.[ch] and updates the relevant build and translation files. There are still outstanding gimp_vectors_* () functions on the app side that need to be renamed in a subsequent commit.
2024-07-12 14:16:25 +08:00
dup_value_func => '$var = GIMP_VALUES_GET_PATH ($value)',
app, libgimp: get rid of all ID GTypes and ID param specs Turn all ID param specs into object param specs (e.g. GimpParamImageID becomes GimpParamImage) and convert between IDs and objects in gimpgpparams.c directly above the the wire protocol, so all of app/, libgimp/ and plug-ins/ can deal directly with objects down to the lowest level and not care about IDs. Use the actual object param specs for procedure arguments and return values again instead of a plain g_param_spec_object() and bring back the none_ok parameter. This implies changing the PDB type checking functions to work on pure integers instead of IDs (one can't check whether object creation is possible if performing that check requires the object to already exist). For example gimp_foo_is_valid() becomes gimp_foo_id_is_valid() and is not involved in automatic object creation magic at the protocol level. Added wrappers which still say gimp_foo_is_valid() and take the respective objects. Adapted all code, and it all becomes nicer and less convoluted, even the generated PDB wrappers in app/ and libgimp/.
2019-08-29 17:25:35 +08:00
set_value_func => 'g_value_set_object ($value, $var)',
take_value_func => 'g_value_set_object ($value, $var)',
libgimp, app, pdb: Rename GimpVectors to GimpPath This commit renames the GimpVectors object to GimpPath in both app/core and in libgimp. It also renames the files to gimppath.[ch] and updates the relevant build and translation files. There are still outstanding gimp_vectors_* () functions on the app side that need to be renamed in a subsequent commit.
2024-07-12 14:16:25 +08:00
headers => [ qw("vectors/gimppath.h") ] },
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
pdb, app, libgimp, plug-ins: replace most PDB filenames/URIs by GFile and in an attack of madness, changes almost all file plug-in code to use GFile instead of filenames, which means passing the GFile down to the bottom and get its filename at the very end where it's actually needed.
2019-09-12 03:48:34 +08:00
file => { name => 'FILE',
gtype => 'G_TYPE_FILE',
type => 'GFile *',
const_type => 'GFile *',
init_value => 'NULL',
out_annotate => '(transfer full)',
get_value_func => '$var = g_value_get_object ($value)',
dup_value_func => '$var = GIMP_VALUES_DUP_FILE ($value)',
set_value_func => 'g_value_set_object ($value, $var)',
take_value_func => 'g_value_set_object ($value, $var)' },
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
parasite => { name => 'PARASITE',
gtype => 'GIMP_TYPE_PARASITE',
type => 'GimpParasite *',
const_type => 'const GimpParasite *',
init_value => 'NULL',
pdb, libgimp: annotate input arrays with (element-type foo)
2019-08-01 00:58:52 +08:00
out_annotate => '(transfer full)',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
get_value_func => '$var = g_value_get_boxed ($value)',
pdb, libgimp: use GIMP_VALUES_GET,DUP_FOO() in the libgimp PDB wrappers
2019-09-04 08:49:33 +08:00
dup_value_func => '$var = GIMP_VALUES_DUP_PARASITE ($value)',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
set_value_func => 'g_value_set_boxed ($value, $var)',
take_value_func => 'g_value_take_boxed ($value, $var)',
headers => [ qw("libgimpbase/gimpbase.h") ] },
PDB autogen stuff. Unfinished and undocumented -Yosh
1998-10-24 13:19:30 +08:00
pdb: add gimp_procedural_db_proc_argument() and _return_value() Which return proper GParamSpecs. Incuding some useless testing code in gimp_procedural_db_proc_info(), to make sure things work, will go away again soon.
2019-08-05 16:46:55 +08:00
param => { name => 'PARAM',
gtype => 'G_TYPE_PARAM_SPEC',
type => 'GParamSpec *',
const_type => 'GParamSpec *',
init_value => 'NULL',
out_annotate => '(transfer full)',
get_value_func => '$var = g_value_get_param ($value)',
pdb, libgimp: use GIMP_VALUES_GET,DUP_FOO() in the libgimp PDB wrappers
2019-09-04 08:49:33 +08:00
dup_value_func => '$var = GIMP_VALUES_DUP_PARAM ($value)',
pdb: add gimp_procedural_db_proc_argument() and _return_value() Which return proper GParamSpecs. Incuding some useless testing code in gimp_procedural_db_proc_info(), to make sure things work, will go away again soon.
2019-08-05 16:46:55 +08:00
set_value_func => 'g_value_set_param ($value, $var)',
take_value_func => 'g_value_take_param ($value, $var)' },
PDB autogen stuff. Unfinished and undocumented -Yosh
1998-10-24 13:19:30 +08:00
# Special cases
pdb: use guint for tatoo, guide, sample point, which they are and initialize GimpUnit with PIXEL instead of just 0.
2019-08-15 22:41:39 +08:00
enum => { name => 'ENUM',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
gtype => 'G_TYPE_ENUM',
Remove GIMP_TYPE_INT32 and GimpParamSpecInt32 Use gint and GParamSpecInt instead.
2019-08-15 20:04:56 +08:00
type => 'gint ',
const_type => 'gint ',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
init_value => '0',
get_value_func => '$var = g_value_get_enum ($value)',
pdb, libgimp: use GIMP_VALUES_GET,DUP_FOO() in the libgimp PDB wrappers
2019-09-04 08:49:33 +08:00
dup_value_func => '$var = GIMP_VALUES_GET_ENUM ($value)',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
set_value_func => 'g_value_set_enum ($value, $var)',
take_value_func => 'g_value_set_enum ($value, $var)' },
pdb: use guint for tatoo, guide, sample point, which they are and initialize GimpUnit with PIXEL instead of just 0.
2019-08-15 22:41:39 +08:00
boolean => { name => 'BOOLEAN',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
gtype => 'G_TYPE_BOOLEAN',
type => 'gboolean ',
const_type => 'gboolean ',
init_value => 'FALSE',
get_value_func => '$var = g_value_get_boolean ($value)',
pdb, libgimp: use GIMP_VALUES_GET,DUP_FOO() in the libgimp PDB wrappers
2019-09-04 08:49:33 +08:00
dup_value_func => '$var = GIMP_VALUES_GET_BOOLEAN ($value)',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
set_value_func => 'g_value_set_boolean ($value, $var)',
take_value_func => 'g_value_set_boolean ($value, $var)' },
pdb: use guint for tatoo, guide, sample point, which they are and initialize GimpUnit with PIXEL instead of just 0.
2019-08-15 22:41:39 +08:00
tattoo => { name => 'TATTOO',
gtype => 'G_TYPE_UINT',
type => 'guint ',
const_type => 'guint ',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
init_value => '0',
get_value_func => '$var = g_value_get_uint ($value)',
pdb, libgimp: use GIMP_VALUES_GET,DUP_FOO() in the libgimp PDB wrappers
2019-09-04 08:49:33 +08:00
dup_value_func => '$var = GIMP_VALUES_GET_UINT ($value)',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
set_value_func => 'g_value_set_uint ($value, $var)',
take_value_func => 'g_value_set_uint ($value, $var)' },
pdb: use guint for tatoo, guide, sample point, which they are and initialize GimpUnit with PIXEL instead of just 0.
2019-08-15 22:41:39 +08:00
guide => { name => 'GUIDE',
gtype => 'G_TYPE_UINT',
type => 'guint ',
const_type => 'guint ',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
init_value => '0',
get_value_func => '$var = g_value_get_uint ($value)',
pdb, libgimp: use GIMP_VALUES_GET,DUP_FOO() in the libgimp PDB wrappers
2019-09-04 08:49:33 +08:00
dup_value_func => '$var = GIMP_VALUES_GET_UINT ($value)',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
set_value_func => 'g_value_set_uint ($value, $var)',
take_value_func => 'g_value_set_uint ($value, $var)' },
pdb: use guint for tatoo, guide, sample point, which they are and initialize GimpUnit with PIXEL instead of just 0.
2019-08-15 22:41:39 +08:00
sample_point => { name => 'SAMPLE_POINT',
gtype => 'G_TYPE_UINT',
type => 'guint ',
const_type => 'guint ',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
init_value => '0',
get_value_func => '$var = g_value_get_uint ($value)',
pdb, libgimp: use GIMP_VALUES_GET,DUP_FOO() in the libgimp PDB wrappers
2019-09-04 08:49:33 +08:00
dup_value_func => '$var = GIMP_VALUES_GET_UINT ($value)',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
set_value_func => 'g_value_set_uint ($value, $var)',
take_value_func => 'g_value_set_uint ($value, $var)' },
core, pdb, plug-ins: Create GimpExportOptions class This patch creates a GimpExportOptions class in both libgimpbase and in libgimp. Currently it is a mostly empty object, but it will be added to after 3.0 to allow for additional export options (like resizing on export while leaving the original image intact) libgimp/gimpexport.c was removed, and most of its content was copied into libgimp/gimpexportoptions.c. gimp_export_image () was replaced with gimp_export_options_get_image () in all export plug-ins. GimpExportProcedure has a new function to set the default image capabilities for each plug-in on creation. It also sets up a new callback function, which allows the options to respond to user setting changes (such as toggling 'Save as Animation' in the GIF or WEBP Plug-in).
2024-05-07 02:38:12 +08:00
export_options => { name => 'EXPORT_OPTIONS',
gtype => 'GIMP_TYPE_EXPORT_OPTIONS',
type => 'GimpExportOptions *',
const_type => 'GimpExportOptions *',
init_value => 'NULL',
app, libgimp*, pdb, plug-ins: review and enhance MR !1549. - Fix annotations for gimp_export_options_get_image() to make it actually introspectable with the GimpImage being both input and output. Even though the logic doesn't change much (the input image may be overriden or not), it doesn't matter for introspection because images are handled centrally by libgimp and therefore must not be freed. Actually deleting the image from the central list of images though remains a manual action depending on code logic, not some automatic action to be handled by binding engines. - Add G_GNUC_WARN_UNUSED_RESULT to gimp_export_options_get_image() because ignoring the returned value is rarely a good idea (as you usually want to delete the image). - Remove gimp_export_options_new(): we don't need this constructor because at this point, the best is to tell plug-in developers to just pass NULL everywhere. This leaves us free to create a more useful default constructor if needed, in the future. Main description for GimpExportOptions has also been updated to say this. - Add a data_destroy callback for the user data passed in gimp_export_procedure_set_capabilities(). - Fixing annotations of 'export_options' object from pdb/pdb.pl: input args would actually be (nullable) and would not transfer ownership (calling code must still free the object). Return value's ownership on the other hand is fully transfered. - Add C and Python unit testing for GimpExportOptions and gimp_export_options_get_image() in particular. - Fix or improve various details. Note that I have also considered for a long time changing the signature of gimp_export_options_get_image() to return a boolean indicating whether `image` had been replaced (hence needed deletion) or not. This also meant getting rid of the GimpExportReturn enum. Right now it would work because there are no third case, but I was considering the future possibility that for instance we got some impossible conversion for some future capability. I'm not sure it would ever happen; and for sure, this is not desirable because it implies an export failure a bit late in the workflow. But just in case, let's keep the enum return value. It does not even make the using code that much more complicated (well just a value comparison instead of a simple boolean test).
2024-08-17 21:06:27 +08:00
in_annotate => '(nullable)',
out_annotate => '(transfer full)',
core, pdb, plug-ins: Create GimpExportOptions class This patch creates a GimpExportOptions class in both libgimpbase and in libgimp. Currently it is a mostly empty object, but it will be added to after 3.0 to allow for additional export options (like resizing on export while leaving the original image intact) libgimp/gimpexport.c was removed, and most of its content was copied into libgimp/gimpexportoptions.c. gimp_export_image () was replaced with gimp_export_options_get_image () in all export plug-ins. GimpExportProcedure has a new function to set the default image capabilities for each plug-in on creation. It also sets up a new callback function, which allows the options to respond to user setting changes (such as toggling 'Save as Animation' in the GIF or WEBP Plug-in).
2024-05-07 02:38:12 +08:00
get_value_func => '$var = g_value_get_object ($value)',
dup_value_func => '$var = g_value_dup_object (gimp_value_array_index ($value))',
set_value_func => 'g_value_set_object ($value, $var)',
take_value_func => 'g_value_set_object ($value, $var)',
headers => [ qw("libgimpbase/gimpbase.h") ] },
pdb: use guint for tatoo, guide, sample point, which they are and initialize GimpUnit with PIXEL instead of just 0.
2019-08-15 22:41:39 +08:00
unit => { name => 'UNIT',
pdb: "gtype", "dup_value_func" and "take_value_func" to all PDB types so we have the toolkit for generating proper GType-based code in libgimp. This commit changes no code yet.
2019-07-30 16:39:56 +08:00
gtype => 'GIMP_TYPE_UNIT',
Issue #8900 and #9923: reimplementing GimpUnit as a proper class. This fixes all our GObject Introspection issues with GimpUnit which was both an enum and an int-derived type of user-defined units *completing* the enum values. GIR clearly didn't like this! Now GimpUnit is a proper class and units are unique objects, allowing to compare them with an identity test (i.e. `unit == gimp_unit_pixel ()` tells us if unit is the pixel unit or not), which makes it easy to use, just like with int, yet adding also methods, making for nicer introspected API. As an aside, this also fixes #10738, by having all the built-in units retrievable even if libgimpbase had not been properly initialized with gimp_base_init(). I haven't checked in details how GIR works to introspect, but it looks like it loads the library to inspect and runs functions, hence triggering some CRITICALS because virtual methods (supposed to be initialized with gimp_base_init() run by libgimp) are not set. This new code won't trigger any critical because the vtable method are now not necessary, at least for all built-in units. Note that GimpUnit is still in libgimpbase. It could have been moved to libgimp in order to avoid any virtual method table (since we need to keep core and libgimp side's units in sync, PDB is required), but too many libgimpwidgets widgets were already using GimpUnit. And technically most of GimpUnit logic doesn't require PDB (only the creation/sync part). This is one of the reasons why user-created GimpUnit list is handled and stored differently from other types of objects. Globally this simplifies the code a lot too and we don't need separate implementations of various utils for core and libgimp, which means less prone to errors.
2024-07-26 02:55:21 +08:00
type => 'GimpUnit *',
const_type => 'GimpUnit *',
init_value => 'NULL',
pdb, libgimp: more docs and annotations
2019-08-05 21:31:12 +08:00
out_annotate => '(transfer none)',
Issue #8900 and #9923: reimplementing GimpUnit as a proper class. This fixes all our GObject Introspection issues with GimpUnit which was both an enum and an int-derived type of user-defined units *completing* the enum values. GIR clearly didn't like this! Now GimpUnit is a proper class and units are unique objects, allowing to compare them with an identity test (i.e. `unit == gimp_unit_pixel ()` tells us if unit is the pixel unit or not), which makes it easy to use, just like with int, yet adding also methods, making for nicer introspected API. As an aside, this also fixes #10738, by having all the built-in units retrievable even if libgimpbase had not been properly initialized with gimp_base_init(). I haven't checked in details how GIR works to introspect, but it looks like it loads the library to inspect and runs functions, hence triggering some CRITICALS because virtual methods (supposed to be initialized with gimp_base_init() run by libgimp) are not set. This new code won't trigger any critical because the vtable method are now not necessary, at least for all built-in units. Note that GimpUnit is still in libgimpbase. It could have been moved to libgimp in order to avoid any virtual method table (since we need to keep core and libgimp side's units in sync, PDB is required), but too many libgimpwidgets widgets were already using GimpUnit. And technically most of GimpUnit logic doesn't require PDB (only the creation/sync part). This is one of the reasons why user-created GimpUnit list is handled and stored differently from other types of objects. Globally this simplifies the code a lot too and we don't need separate implementations of various utils for core and libgimp, which means less prone to errors.
2024-07-26 02:55:21 +08:00
get_value_func => '$var = g_value_get_object ($value)',
dup_value_func => '$var = GIMP_VALUES_GET_UNIT ($value)',
set_value_func => 'g_value_set_object ($value, $var)',
take_value_func => 'g_value_set_object ($value, $var)',
headers => [ qw("libgimpbase/gimpbase.h") ] },
2.99 libgimp: add GimpResource, GimpBrush, GimpPropWidgetBrush So procedures can declare args and GimpProcedureDialog show chooser widgets Fix so is no error dialog on id_is_valid for resources Palette.pdb changes and testing Memory mgt changes Gradient pdb Font and Pattern tests Test brush, palette Cleanup, remove generator Rebase, edit docs, install test-dialog.py Whitespace, and fix failed distcheck Fix some clang-format, fix fail distcheck Fix distcheck Cleanup from review Jehan
2022-09-06 07:28:35 +08:00
Introduce a global ID space for GimpData/GimpResource objects Much like for images and items. Change the PDB to transmit IDs instead of names for brush, pattern etc. and refactor a whole lot of libgimp code to deal with it. modified: libgimp/gimpplugin-private.h
2023-05-31 22:12:04 +08:00
resource => { name => 'RESOURCE',
gtype => 'GIMP_TYPE_RESOURCE',
type => 'GimpResource *',
const_type => 'GimpResource *',
init_value => 'NULL',
app, libgimp, pdb: fix annotations for resources as return values. Resources are stored by the plug-in infrastructure and their memory should not be managed by plug-in code. My commit 4f69995b46 was crappy and modified a generated function. I was just too tired with all the heat in here, I guess!
2023-07-11 22:13:36 +08:00
out_annotate => '(transfer none)',
Introduce a global ID space for GimpData/GimpResource objects Much like for images and items. Change the PDB to transmit IDs instead of names for brush, pattern etc. and refactor a whole lot of libgimp code to deal with it. modified: libgimp/gimpplugin-private.h
2023-05-31 22:12:04 +08:00
get_value_func => '$var = g_value_get_object ($value)',
dup_value_func => '$var = GIMP_VALUES_GET_RESOURCE ($value)',
set_value_func => 'g_value_set_object ($value, $var)',
take_value_func => 'g_value_set_object ($value, $var)',
headers => [ qw("core/gimpresource.h") ] },
2.99 libgimp: add GimpResource, GimpBrush, GimpPropWidgetBrush So procedures can declare args and GimpProcedureDialog show chooser widgets Fix so is no error dialog on id_is_valid for resources Palette.pdb changes and testing Memory mgt changes Gradient pdb Font and Pattern tests Test brush, palette Cleanup, remove generator Rebase, edit docs, install test-dialog.py Whitespace, and fix failed distcheck Fix some clang-format, fix fail distcheck Fix distcheck Cleanup from review Jehan
2022-09-06 07:28:35 +08:00
brush => { name => 'BRUSH',
gtype => 'GIMP_TYPE_BRUSH',
type => 'GimpBrush *',
const_type => 'GimpBrush *',
init_value => 'NULL',
app, libgimp, pdb: fix annotations for resources as return values. Resources are stored by the plug-in infrastructure and their memory should not be managed by plug-in code. My commit 4f69995b46 was crappy and modified a generated function. I was just too tired with all the heat in here, I guess!
2023-07-11 22:13:36 +08:00
out_annotate => '(transfer none)',
2.99 libgimp: add GimpResource, GimpBrush, GimpPropWidgetBrush So procedures can declare args and GimpProcedureDialog show chooser widgets Fix so is no error dialog on id_is_valid for resources Palette.pdb changes and testing Memory mgt changes Gradient pdb Font and Pattern tests Test brush, palette Cleanup, remove generator Rebase, edit docs, install test-dialog.py Whitespace, and fix failed distcheck Fix some clang-format, fix fail distcheck Fix distcheck Cleanup from review Jehan
2022-09-06 07:28:35 +08:00
get_value_func => '$var = g_value_get_object ($value)',
dup_value_func => '$var = GIMP_VALUES_GET_BRUSH ($value)',
set_value_func => 'g_value_set_object ($value, $var)',
take_value_func => 'g_value_set_object ($value, $var)',
headers => [ qw("core/gimpbrush.h") ] },
Introduce a global ID space for GimpData/GimpResource objects Much like for images and items. Change the PDB to transmit IDs instead of names for brush, pattern etc. and refactor a whole lot of libgimp code to deal with it. modified: libgimp/gimpplugin-private.h
2023-05-31 22:12:04 +08:00
pattern => { name => 'PATTERN',
gtype => 'GIMP_TYPE_PATTERN',
type => 'GimpPattern *',
const_type => 'GimpPattern *',
2.99 libgimp: add GimpResource, GimpBrush, GimpPropWidgetBrush So procedures can declare args and GimpProcedureDialog show chooser widgets Fix so is no error dialog on id_is_valid for resources Palette.pdb changes and testing Memory mgt changes Gradient pdb Font and Pattern tests Test brush, palette Cleanup, remove generator Rebase, edit docs, install test-dialog.py Whitespace, and fix failed distcheck Fix some clang-format, fix fail distcheck Fix distcheck Cleanup from review Jehan
2022-09-06 07:28:35 +08:00
init_value => 'NULL',
app, libgimp, pdb: fix annotations for resources as return values. Resources are stored by the plug-in infrastructure and their memory should not be managed by plug-in code. My commit 4f69995b46 was crappy and modified a generated function. I was just too tired with all the heat in here, I guess!
2023-07-11 22:13:36 +08:00
out_annotate => '(transfer none)',
2.99 libgimp: add GimpResource, GimpBrush, GimpPropWidgetBrush So procedures can declare args and GimpProcedureDialog show chooser widgets Fix so is no error dialog on id_is_valid for resources Palette.pdb changes and testing Memory mgt changes Gradient pdb Font and Pattern tests Test brush, palette Cleanup, remove generator Rebase, edit docs, install test-dialog.py Whitespace, and fix failed distcheck Fix some clang-format, fix fail distcheck Fix distcheck Cleanup from review Jehan
2022-09-06 07:28:35 +08:00
get_value_func => '$var = g_value_get_object ($value)',
Introduce a global ID space for GimpData/GimpResource objects Much like for images and items. Change the PDB to transmit IDs instead of names for brush, pattern etc. and refactor a whole lot of libgimp code to deal with it. modified: libgimp/gimpplugin-private.h
2023-05-31 22:12:04 +08:00
dup_value_func => '$var = GIMP_VALUES_GET_PATTERN ($value)',
2.99 libgimp: add GimpResource, GimpBrush, GimpPropWidgetBrush So procedures can declare args and GimpProcedureDialog show chooser widgets Fix so is no error dialog on id_is_valid for resources Palette.pdb changes and testing Memory mgt changes Gradient pdb Font and Pattern tests Test brush, palette Cleanup, remove generator Rebase, edit docs, install test-dialog.py Whitespace, and fix failed distcheck Fix some clang-format, fix fail distcheck Fix distcheck Cleanup from review Jehan
2022-09-06 07:28:35 +08:00
set_value_func => 'g_value_set_object ($value, $var)',
take_value_func => 'g_value_set_object ($value, $var)',
Introduce a global ID space for GimpData/GimpResource objects Much like for images and items. Change the PDB to transmit IDs instead of names for brush, pattern etc. and refactor a whole lot of libgimp code to deal with it. modified: libgimp/gimpplugin-private.h
2023-05-31 22:12:04 +08:00
headers => [ qw("core/gimppattern.h") ] },
2.99 libgimp: add GimpResource, GimpBrush, GimpPropWidgetBrush So procedures can declare args and GimpProcedureDialog show chooser widgets Fix so is no error dialog on id_is_valid for resources Palette.pdb changes and testing Memory mgt changes Gradient pdb Font and Pattern tests Test brush, palette Cleanup, remove generator Rebase, edit docs, install test-dialog.py Whitespace, and fix failed distcheck Fix some clang-format, fix fail distcheck Fix distcheck Cleanup from review Jehan
2022-09-06 07:28:35 +08:00
gradient => { name => 'GRADIENT',
gtype => 'GIMP_TYPE_GRADIENT',
type => 'GimpGradient *',
const_type => 'GimpGradient *',
init_value => 'NULL',
app, libgimp, pdb: fix annotations for resources as return values. Resources are stored by the plug-in infrastructure and their memory should not be managed by plug-in code. My commit 4f69995b46 was crappy and modified a generated function. I was just too tired with all the heat in here, I guess!
2023-07-11 22:13:36 +08:00
out_annotate => '(transfer none)',
2.99 libgimp: add GimpResource, GimpBrush, GimpPropWidgetBrush So procedures can declare args and GimpProcedureDialog show chooser widgets Fix so is no error dialog on id_is_valid for resources Palette.pdb changes and testing Memory mgt changes Gradient pdb Font and Pattern tests Test brush, palette Cleanup, remove generator Rebase, edit docs, install test-dialog.py Whitespace, and fix failed distcheck Fix some clang-format, fix fail distcheck Fix distcheck Cleanup from review Jehan
2022-09-06 07:28:35 +08:00
get_value_func => '$var = g_value_get_object ($value)',
dup_value_func => '$var = GIMP_VALUES_GET_GRADIENT ($value)',
set_value_func => 'g_value_set_object ($value, $var)',
take_value_func => 'g_value_set_object ($value, $var)',
headers => [ qw("core/gimpgradient.h") ] },
palette => { name => 'PALETTE',
gtype => 'GIMP_TYPE_PALETTE',
type => 'GimpPalette *',
const_type => 'GimpPalette *',
init_value => 'NULL',
app, libgimp, pdb: fix annotations for resources as return values. Resources are stored by the plug-in infrastructure and their memory should not be managed by plug-in code. My commit 4f69995b46 was crappy and modified a generated function. I was just too tired with all the heat in here, I guess!
2023-07-11 22:13:36 +08:00
out_annotate => '(transfer none)',
2.99 libgimp: add GimpResource, GimpBrush, GimpPropWidgetBrush So procedures can declare args and GimpProcedureDialog show chooser widgets Fix so is no error dialog on id_is_valid for resources Palette.pdb changes and testing Memory mgt changes Gradient pdb Font and Pattern tests Test brush, palette Cleanup, remove generator Rebase, edit docs, install test-dialog.py Whitespace, and fix failed distcheck Fix some clang-format, fix fail distcheck Fix distcheck Cleanup from review Jehan
2022-09-06 07:28:35 +08:00
get_value_func => '$var = g_value_get_object ($value)',
dup_value_func => '$var = GIMP_VALUES_GET_PALETTE ($value)',
set_value_func => 'g_value_set_object ($value, $var)',
take_value_func => 'g_value_set_object ($value, $var)',
headers => [ qw("core/gimppalette.h") ] },
Introduce a global ID space for GimpData/GimpResource objects Much like for images and items. Change the PDB to transmit IDs instead of names for brush, pattern etc. and refactor a whole lot of libgimp code to deal with it. modified: libgimp/gimpplugin-private.h
2023-05-31 22:12:04 +08:00
font => { name => 'FONT',
gtype => 'GIMP_TYPE_FONT',
type => 'GimpFont *',
const_type => 'GimpFont *',
2.99 libgimp: add GimpResource, GimpBrush, GimpPropWidgetBrush So procedures can declare args and GimpProcedureDialog show chooser widgets Fix so is no error dialog on id_is_valid for resources Palette.pdb changes and testing Memory mgt changes Gradient pdb Font and Pattern tests Test brush, palette Cleanup, remove generator Rebase, edit docs, install test-dialog.py Whitespace, and fix failed distcheck Fix some clang-format, fix fail distcheck Fix distcheck Cleanup from review Jehan
2022-09-06 07:28:35 +08:00
init_value => 'NULL',
app, libgimp, pdb: fix annotations for resources as return values. Resources are stored by the plug-in infrastructure and their memory should not be managed by plug-in code. My commit 4f69995b46 was crappy and modified a generated function. I was just too tired with all the heat in here, I guess!
2023-07-11 22:13:36 +08:00
out_annotate => '(transfer none)',
2.99 libgimp: add GimpResource, GimpBrush, GimpPropWidgetBrush So procedures can declare args and GimpProcedureDialog show chooser widgets Fix so is no error dialog on id_is_valid for resources Palette.pdb changes and testing Memory mgt changes Gradient pdb Font and Pattern tests Test brush, palette Cleanup, remove generator Rebase, edit docs, install test-dialog.py Whitespace, and fix failed distcheck Fix some clang-format, fix fail distcheck Fix distcheck Cleanup from review Jehan
2022-09-06 07:28:35 +08:00
get_value_func => '$var = g_value_get_object ($value)',
Introduce a global ID space for GimpData/GimpResource objects Much like for images and items. Change the PDB to transmit IDs instead of names for brush, pattern etc. and refactor a whole lot of libgimp code to deal with it. modified: libgimp/gimpplugin-private.h
2023-05-31 22:12:04 +08:00
dup_value_func => '$var = GIMP_VALUES_GET_FONT ($value)',
2.99 libgimp: add GimpResource, GimpBrush, GimpPropWidgetBrush So procedures can declare args and GimpProcedureDialog show chooser widgets Fix so is no error dialog on id_is_valid for resources Palette.pdb changes and testing Memory mgt changes Gradient pdb Font and Pattern tests Test brush, palette Cleanup, remove generator Rebase, edit docs, install test-dialog.py Whitespace, and fix failed distcheck Fix some clang-format, fix fail distcheck Fix distcheck Cleanup from review Jehan
2022-09-06 07:28:35 +08:00
set_value_func => 'g_value_set_object ($value, $var)',
take_value_func => 'g_value_set_object ($value, $var)',
Introduce a global ID space for GimpData/GimpResource objects Much like for images and items. Change the PDB to transmit IDs instead of names for brush, pattern etc. and refactor a whole lot of libgimp code to deal with it. modified: libgimp/gimpplugin-private.h
2023-05-31 22:12:04 +08:00
headers => [ qw("text/gimpfont.h") ] }
PDB autogen stuff. Unfinished and undocumented -Yosh
1998-10-24 13:19:30 +08:00
);
# Split out the parts of an arg constraint
sub arg_parse {
my $arg = shift;
Bunch more stuff -Yosh
1999-03-18 07:08:08 +08:00
if ($arg =~ /^enum (\w+)(.*)/) {
my ($name, $remove) = ($1, $2);
my @retvals = ('enum', $name);
Stuff -Yosh
1999-03-28 14:36:11 +08:00
if ($remove && $remove =~ m@ \(no @) {
chop $remove; ($remove = substr($remove, 5)) =~ s/ $//;
Bunch more stuff -Yosh
1999-03-18 07:08:08 +08:00
push @retvals, split(/,\s*/, $remove);
}
return @retvals;
PDB autogen stuff. Unfinished and undocumented -Yosh
1998-10-24 13:19:30 +08:00
}
Stuff -Yosh
1999-04-27 12:33:41 +08:00
elsif ($arg =~ /^unit(?: \(min (.*?)\))?/) {
my @retvals = ('unit');
push @retvals, $1 if $1;
return @retvals;
}
allow the use of constants when specifying limits for a PDB type. 2007-07-05 Sven Neumann <sven@gimp.org> * tools/pdbgen/pdb.pl (arg_parse): allow the use of constants when specifying limits for a PDB type. * tools/pdbgen/pdb/channel.pdb * tools/pdbgen/pdb/image.pdb * tools/pdbgen/pdb/layer.pdb: use GIMP_MAX_IMAGE_SIZE as limit for image and drawable sizes. * tools/pdbgen/pdb/selection_tools.pdb: added missing include. * app/pdb/channel_cmds.c * app/pdb/image_cmds.c * app/pdb/layer_cmds.c * app/pdb/selection_tools_cmds.c: regenerated. svn path=/trunk/; revision=22870
2007-07-05 22:31:42 +08:00
elsif ($arg =~ /^(?:([+-.\dA-Z_][^\s]*) \s* (<=|<))?
More stuff -Yosh
1999-03-21 10:14:08 +08:00
\s* (\w+) \s*
allow the use of constants when specifying limits for a PDB type. 2007-07-05 Sven Neumann <sven@gimp.org> * tools/pdbgen/pdb.pl (arg_parse): allow the use of constants when specifying limits for a PDB type. * tools/pdbgen/pdb/channel.pdb * tools/pdbgen/pdb/image.pdb * tools/pdbgen/pdb/layer.pdb: use GIMP_MAX_IMAGE_SIZE as limit for image and drawable sizes. * tools/pdbgen/pdb/selection_tools.pdb: added missing include. * app/pdb/channel_cmds.c * app/pdb/image_cmds.c * app/pdb/layer_cmds.c * app/pdb/selection_tools_cmds.c: regenerated. svn path=/trunk/; revision=22870
2007-07-05 22:31:42 +08:00
(?:(<=|<) \s* ([+-.\dA-Z_][^\s]*))?
The enum parser, other stuff -Yosh
1999-03-20 07:04:16 +08:00
/x) {
Bug 620604 - Description of "histogram" procedure is slightly inaccurate Fix totally broken value ranges of integer PDB parameters. Magically, the bug was affecting only exactly the two cases mentioned in above bug report. * tools/pdbgen/pdb.pl (arg_parse): return <, <=, > and >= literally instead of applying a mapping that was originally meant for generated C code that would e.g. transform "0 <= int32 < 10" into "if (value < 0 || value >= 10) fail". This inversion of all operators is now wrong because PDB parameters have been turned into GParamSpecs which always need inclusive ranges as min and max values. * tools/pdbgen/pdbgen.pl (arrayexpand): generated array length type specs must be "0 <= int32", not "0 < int32". * tools/pdbgen/app.pl: when generating integer param specs, check if the value range is specified in terms of < instead of <=, and add/subtract 1, resuting in the inclusive range needed for integer GParamSpecs. * app/pdb/color-cmds.c: regenerated, fixing the two broken ranges mentioned in the bug report.
2010-06-06 01:26:06 +08:00
return ($3, $1, $2, $5, $4);
PDB autogen stuff. Unfinished and undocumented -Yosh
1998-10-24 13:19:30 +08:00
}
}
Lossa stuff -Yosh
1999-04-04 13:59:08 +08:00
1;