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

53 lines
1.7 KiB
C
Raw Normal View History

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
/* LIBGIMP - The GIMP Library
* Copyright (C) 1995-2000 Peter Mattis and Spencer Kimball
*
* gimptextlayer.h
* Copyright (C) 2022 Jehan
*
* This library is free software: you can redistribute it and/or
* modify it under the terms of the GNU Lesser General Public
* License as published by the Free Software Foundation; either
* version 3 of the License, or (at your option) any later version.
*
* This library 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
* Lesser General Public License for more details.
*
* You should have received a copy of the GNU Lesser General Public
* License along with this library. If not, see
* <https://www.gnu.org/licenses/>.
*/
#if !defined (__GIMP_H_INSIDE__) && !defined (GIMP_COMPILATION)
#error "Only <libgimp/gimp.h> can be included directly."
#endif
#ifndef __GIMP_TEXT_LAYER_H__
#define __GIMP_TEXT_LAYER_H__
G_BEGIN_DECLS
/* For information look into the C source or the html documentation */
libgimp: some object's header cleanup. Using G_DECLARE_*() macros everywhere, aligning functions, including the parent class header…
2024-07-07 04:45:53 +08:00
#include <libgimp/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
#define GIMP_TYPE_TEXT_LAYER (gimp_text_layer_get_type ())
G_DECLARE_FINAL_TYPE (GimpTextLayer, gimp_text_layer, GIMP, TEXT_LAYER, GimpLayer)
GimpTextLayer * gimp_text_layer_get_by_id (gint32 layer_id);
GimpTextLayer * gimp_text_layer_new (GimpImage *image,
const gchar *text,
app, libgimp, pdb: gimp_text_layer_new() now uses GimpFont. This function is not perfect and in particular doesn't seem usable with binding because of GimpUnit being some weird mix between an enum and some kind of class. So this will have to be fixed too. See #8900.
2023-09-14 01:24:10 +08:00
GimpFont *font,
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
gdouble size,
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
GimpUnit *unit) G_GNUC_WARN_UNUSED_RESULT;
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
G_END_DECLS
#endif /* __GIMP_TEXT_LAYER_H__ */