2017-05-09 04:02:37 +08:00
|
|
|
/* GIMP - The GNU Image Manipulation Program
|
|
|
|
* Copyright (C) 1995-1997 Spencer Kimball and Peter Mattis
|
|
|
|
*
|
|
|
|
* gimplayerstack.c
|
|
|
|
* Copyright (C) 2017 Ell
|
|
|
|
*
|
|
|
|
* This program is free software: you can redistribute it and/or modify
|
|
|
|
* it under the terms of the GNU General Public License as published by
|
|
|
|
* the Free Software Foundation; either version 3 of the License, or
|
|
|
|
* (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
|
2018-07-12 05:27:07 +08:00
|
|
|
* along with this program. If not, see <https://www.gnu.org/licenses/>.
|
2017-05-09 04:02:37 +08:00
|
|
|
*/
|
|
|
|
|
|
|
|
#include "config.h"
|
|
|
|
|
|
|
|
#include <gdk-pixbuf/gdk-pixbuf.h>
|
|
|
|
#include <gegl.h>
|
|
|
|
|
|
|
|
#include "core-types.h"
|
|
|
|
|
|
|
|
#include "gimplayer.h"
|
|
|
|
#include "gimplayerstack.h"
|
|
|
|
|
|
|
|
|
|
|
|
/* local function prototypes */
|
|
|
|
|
|
|
|
static void gimp_layer_stack_constructed (GObject *object);
|
|
|
|
|
|
|
|
static void gimp_layer_stack_add (GimpContainer *container,
|
|
|
|
GimpObject *object);
|
|
|
|
static void gimp_layer_stack_remove (GimpContainer *container,
|
|
|
|
GimpObject *object);
|
|
|
|
static void gimp_layer_stack_reorder (GimpContainer *container,
|
|
|
|
GimpObject *object,
|
|
|
|
gint new_index);
|
|
|
|
|
app: add GimpFilter::active property; move ::visible to GimpItem
Add an "active" property to GimpFilter, which replaces its
"visible" property. The new property assumes the lower-level role
"visible" had -- controlling whether the filter has any effect as
part of its parent filter-stack.
Add a "visible" property to GimpItem, separate from the "active"
property, which assumes the higher-level role "visible" had --
controlling whether the item is considered "visible", as per the
GUI. By default, the item's "visible" property is bound to the
filter's "active" property, so that changes in visibility directly
affect the filter's "activeness"; this binding can be controlled
using the new gimp_item_bind_visible_to_active() function.
This distinction is currently necessary for floating selections.
Floating selection layers must not be active in their parent stack,
regardless of their visibility, in particular, so that their mode
node doesn't hide the entire backdrop when their composite mode
excludes the backdrop (i.e., when it's dst-atop or src-in).
Instead, their visibility should affect the activeness of the
floating-selection filter of the drawable they're attached to.
This is handled by the next commit.
2017-12-06 02:46:50 +08:00
|
|
|
static void gimp_layer_stack_layer_active (GimpLayer *layer,
|
2017-05-09 04:02:37 +08:00
|
|
|
GimpLayerStack *stack);
|
|
|
|
static void gimp_layer_stack_layer_excludes_backdrop (GimpLayer *layer,
|
|
|
|
GimpLayerStack *stack);
|
|
|
|
|
|
|
|
static void gimp_layer_stack_update_backdrop (GimpLayerStack *stack,
|
|
|
|
GimpLayer *layer,
|
app: add GimpFilter::active property; move ::visible to GimpItem
Add an "active" property to GimpFilter, which replaces its
"visible" property. The new property assumes the lower-level role
"visible" had -- controlling whether the filter has any effect as
part of its parent filter-stack.
Add a "visible" property to GimpItem, separate from the "active"
property, which assumes the higher-level role "visible" had --
controlling whether the item is considered "visible", as per the
GUI. By default, the item's "visible" property is bound to the
filter's "active" property, so that changes in visibility directly
affect the filter's "activeness"; this binding can be controlled
using the new gimp_item_bind_visible_to_active() function.
This distinction is currently necessary for floating selections.
Floating selection layers must not be active in their parent stack,
regardless of their visibility, in particular, so that their mode
node doesn't hide the entire backdrop when their composite mode
excludes the backdrop (i.e., when it's dst-atop or src-in).
Instead, their visibility should affect the activeness of the
floating-selection filter of the drawable they're attached to.
This is handled by the next commit.
2017-12-06 02:46:50 +08:00
|
|
|
gboolean ignore_active,
|
2017-05-09 04:02:37 +08:00
|
|
|
gboolean ignore_excludes_backdrop);
|
|
|
|
static void gimp_layer_stack_update_range (GimpLayerStack *stack,
|
|
|
|
gint first,
|
|
|
|
gint last);
|
|
|
|
|
|
|
|
|
|
|
|
G_DEFINE_TYPE (GimpLayerStack, gimp_layer_stack, GIMP_TYPE_DRAWABLE_STACK)
|
|
|
|
|
|
|
|
#define parent_class gimp_layer_stack_parent_class
|
|
|
|
|
|
|
|
|
|
|
|
static void
|
|
|
|
gimp_layer_stack_class_init (GimpLayerStackClass *klass)
|
|
|
|
{
|
|
|
|
GObjectClass *object_class = G_OBJECT_CLASS (klass);
|
|
|
|
GimpContainerClass *container_class = GIMP_CONTAINER_CLASS (klass);
|
|
|
|
|
|
|
|
object_class->constructed = gimp_layer_stack_constructed;
|
|
|
|
|
|
|
|
container_class->add = gimp_layer_stack_add;
|
|
|
|
container_class->remove = gimp_layer_stack_remove;
|
|
|
|
container_class->reorder = gimp_layer_stack_reorder;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
gimp_layer_stack_init (GimpLayerStack *stack)
|
|
|
|
{
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
gimp_layer_stack_constructed (GObject *object)
|
|
|
|
{
|
|
|
|
GimpContainer *container = GIMP_CONTAINER (object);
|
|
|
|
|
|
|
|
G_OBJECT_CLASS (parent_class)->constructed (object);
|
|
|
|
|
2018-02-12 05:23:10 +08:00
|
|
|
gimp_assert (g_type_is_a (gimp_container_get_children_type (container),
|
|
|
|
GIMP_TYPE_LAYER));
|
2017-05-09 04:02:37 +08:00
|
|
|
|
app: add GimpFilter::active property; move ::visible to GimpItem
Add an "active" property to GimpFilter, which replaces its
"visible" property. The new property assumes the lower-level role
"visible" had -- controlling whether the filter has any effect as
part of its parent filter-stack.
Add a "visible" property to GimpItem, separate from the "active"
property, which assumes the higher-level role "visible" had --
controlling whether the item is considered "visible", as per the
GUI. By default, the item's "visible" property is bound to the
filter's "active" property, so that changes in visibility directly
affect the filter's "activeness"; this binding can be controlled
using the new gimp_item_bind_visible_to_active() function.
This distinction is currently necessary for floating selections.
Floating selection layers must not be active in their parent stack,
regardless of their visibility, in particular, so that their mode
node doesn't hide the entire backdrop when their composite mode
excludes the backdrop (i.e., when it's dst-atop or src-in).
Instead, their visibility should affect the activeness of the
floating-selection filter of the drawable they're attached to.
This is handled by the next commit.
2017-12-06 02:46:50 +08:00
|
|
|
gimp_container_add_handler (container, "active-changed",
|
|
|
|
G_CALLBACK (gimp_layer_stack_layer_active),
|
2017-05-09 04:02:37 +08:00
|
|
|
container);
|
|
|
|
gimp_container_add_handler (container, "excludes-backdrop-changed",
|
|
|
|
G_CALLBACK (gimp_layer_stack_layer_excludes_backdrop),
|
|
|
|
container);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
gimp_layer_stack_add (GimpContainer *container,
|
|
|
|
GimpObject *object)
|
|
|
|
{
|
|
|
|
GimpLayerStack *stack = GIMP_LAYER_STACK (container);
|
|
|
|
|
|
|
|
GIMP_CONTAINER_CLASS (parent_class)->add (container, object);
|
|
|
|
|
|
|
|
gimp_layer_stack_update_backdrop (stack, GIMP_LAYER (object), FALSE, FALSE);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
gimp_layer_stack_remove (GimpContainer *container,
|
|
|
|
GimpObject *object)
|
|
|
|
{
|
|
|
|
GimpLayerStack *stack = GIMP_LAYER_STACK (container);
|
2017-05-13 03:34:28 +08:00
|
|
|
gboolean update_backdrop;
|
|
|
|
gint index;
|
2017-05-09 04:02:37 +08:00
|
|
|
|
app: add GimpFilter::active property; move ::visible to GimpItem
Add an "active" property to GimpFilter, which replaces its
"visible" property. The new property assumes the lower-level role
"visible" had -- controlling whether the filter has any effect as
part of its parent filter-stack.
Add a "visible" property to GimpItem, separate from the "active"
property, which assumes the higher-level role "visible" had --
controlling whether the item is considered "visible", as per the
GUI. By default, the item's "visible" property is bound to the
filter's "active" property, so that changes in visibility directly
affect the filter's "activeness"; this binding can be controlled
using the new gimp_item_bind_visible_to_active() function.
This distinction is currently necessary for floating selections.
Floating selection layers must not be active in their parent stack,
regardless of their visibility, in particular, so that their mode
node doesn't hide the entire backdrop when their composite mode
excludes the backdrop (i.e., when it's dst-atop or src-in).
Instead, their visibility should affect the activeness of the
floating-selection filter of the drawable they're attached to.
This is handled by the next commit.
2017-12-06 02:46:50 +08:00
|
|
|
update_backdrop = gimp_filter_get_active (GIMP_FILTER (object)) &&
|
2017-05-13 03:34:28 +08:00
|
|
|
gimp_layer_get_excludes_backdrop (GIMP_LAYER (object));
|
|
|
|
|
|
|
|
if (update_backdrop)
|
|
|
|
index = gimp_container_get_child_index (container, object);
|
2017-05-09 04:02:37 +08:00
|
|
|
|
|
|
|
GIMP_CONTAINER_CLASS (parent_class)->remove (container, object);
|
2017-05-13 03:34:28 +08:00
|
|
|
|
|
|
|
if (update_backdrop)
|
|
|
|
gimp_layer_stack_update_range (stack, index, -1);
|
2017-05-09 04:02:37 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
gimp_layer_stack_reorder (GimpContainer *container,
|
|
|
|
GimpObject *object,
|
|
|
|
gint new_index)
|
|
|
|
{
|
|
|
|
GimpLayerStack *stack = GIMP_LAYER_STACK (container);
|
2017-05-13 03:34:28 +08:00
|
|
|
gboolean update_backdrop;
|
2017-05-09 04:02:37 +08:00
|
|
|
gint index;
|
|
|
|
|
app: add GimpFilter::active property; move ::visible to GimpItem
Add an "active" property to GimpFilter, which replaces its
"visible" property. The new property assumes the lower-level role
"visible" had -- controlling whether the filter has any effect as
part of its parent filter-stack.
Add a "visible" property to GimpItem, separate from the "active"
property, which assumes the higher-level role "visible" had --
controlling whether the item is considered "visible", as per the
GUI. By default, the item's "visible" property is bound to the
filter's "active" property, so that changes in visibility directly
affect the filter's "activeness"; this binding can be controlled
using the new gimp_item_bind_visible_to_active() function.
This distinction is currently necessary for floating selections.
Floating selection layers must not be active in their parent stack,
regardless of their visibility, in particular, so that their mode
node doesn't hide the entire backdrop when their composite mode
excludes the backdrop (i.e., when it's dst-atop or src-in).
Instead, their visibility should affect the activeness of the
floating-selection filter of the drawable they're attached to.
This is handled by the next commit.
2017-12-06 02:46:50 +08:00
|
|
|
update_backdrop = gimp_filter_get_active (GIMP_FILTER (object)) &&
|
2017-05-13 03:34:28 +08:00
|
|
|
gimp_layer_get_excludes_backdrop (GIMP_LAYER (object));
|
2017-05-09 04:02:37 +08:00
|
|
|
|
2017-05-13 03:34:28 +08:00
|
|
|
if (update_backdrop)
|
2017-05-09 04:02:37 +08:00
|
|
|
index = gimp_container_get_child_index (container, object);
|
|
|
|
|
|
|
|
GIMP_CONTAINER_CLASS (parent_class)->reorder (container, object, new_index);
|
|
|
|
|
2017-05-13 03:34:28 +08:00
|
|
|
if (update_backdrop)
|
2017-05-09 04:02:37 +08:00
|
|
|
gimp_layer_stack_update_range (stack, index, new_index);
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
/* public functions */
|
|
|
|
|
|
|
|
GimpContainer *
|
|
|
|
gimp_layer_stack_new (GType layer_type)
|
|
|
|
{
|
|
|
|
g_return_val_if_fail (g_type_is_a (layer_type, GIMP_TYPE_LAYER), NULL);
|
|
|
|
|
|
|
|
return g_object_new (GIMP_TYPE_LAYER_STACK,
|
|
|
|
"name", g_type_name (layer_type),
|
|
|
|
"children-type", layer_type,
|
|
|
|
"policy", GIMP_CONTAINER_POLICY_STRONG,
|
|
|
|
NULL);
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
/* private functions */
|
|
|
|
|
|
|
|
static void
|
app: add GimpFilter::active property; move ::visible to GimpItem
Add an "active" property to GimpFilter, which replaces its
"visible" property. The new property assumes the lower-level role
"visible" had -- controlling whether the filter has any effect as
part of its parent filter-stack.
Add a "visible" property to GimpItem, separate from the "active"
property, which assumes the higher-level role "visible" had --
controlling whether the item is considered "visible", as per the
GUI. By default, the item's "visible" property is bound to the
filter's "active" property, so that changes in visibility directly
affect the filter's "activeness"; this binding can be controlled
using the new gimp_item_bind_visible_to_active() function.
This distinction is currently necessary for floating selections.
Floating selection layers must not be active in their parent stack,
regardless of their visibility, in particular, so that their mode
node doesn't hide the entire backdrop when their composite mode
excludes the backdrop (i.e., when it's dst-atop or src-in).
Instead, their visibility should affect the activeness of the
floating-selection filter of the drawable they're attached to.
This is handled by the next commit.
2017-12-06 02:46:50 +08:00
|
|
|
gimp_layer_stack_layer_active (GimpLayer *layer,
|
|
|
|
GimpLayerStack *stack)
|
2017-05-09 04:02:37 +08:00
|
|
|
{
|
|
|
|
gimp_layer_stack_update_backdrop (stack, layer, TRUE, FALSE);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
gimp_layer_stack_layer_excludes_backdrop (GimpLayer *layer,
|
|
|
|
GimpLayerStack *stack)
|
|
|
|
{
|
|
|
|
gimp_layer_stack_update_backdrop (stack, layer, FALSE, TRUE);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
gimp_layer_stack_update_backdrop (GimpLayerStack *stack,
|
|
|
|
GimpLayer *layer,
|
app: add GimpFilter::active property; move ::visible to GimpItem
Add an "active" property to GimpFilter, which replaces its
"visible" property. The new property assumes the lower-level role
"visible" had -- controlling whether the filter has any effect as
part of its parent filter-stack.
Add a "visible" property to GimpItem, separate from the "active"
property, which assumes the higher-level role "visible" had --
controlling whether the item is considered "visible", as per the
GUI. By default, the item's "visible" property is bound to the
filter's "active" property, so that changes in visibility directly
affect the filter's "activeness"; this binding can be controlled
using the new gimp_item_bind_visible_to_active() function.
This distinction is currently necessary for floating selections.
Floating selection layers must not be active in their parent stack,
regardless of their visibility, in particular, so that their mode
node doesn't hide the entire backdrop when their composite mode
excludes the backdrop (i.e., when it's dst-atop or src-in).
Instead, their visibility should affect the activeness of the
floating-selection filter of the drawable they're attached to.
This is handled by the next commit.
2017-12-06 02:46:50 +08:00
|
|
|
gboolean ignore_active,
|
2017-05-09 04:02:37 +08:00
|
|
|
gboolean ignore_excludes_backdrop)
|
|
|
|
{
|
app: add GimpFilter::active property; move ::visible to GimpItem
Add an "active" property to GimpFilter, which replaces its
"visible" property. The new property assumes the lower-level role
"visible" had -- controlling whether the filter has any effect as
part of its parent filter-stack.
Add a "visible" property to GimpItem, separate from the "active"
property, which assumes the higher-level role "visible" had --
controlling whether the item is considered "visible", as per the
GUI. By default, the item's "visible" property is bound to the
filter's "active" property, so that changes in visibility directly
affect the filter's "activeness"; this binding can be controlled
using the new gimp_item_bind_visible_to_active() function.
This distinction is currently necessary for floating selections.
Floating selection layers must not be active in their parent stack,
regardless of their visibility, in particular, so that their mode
node doesn't hide the entire backdrop when their composite mode
excludes the backdrop (i.e., when it's dst-atop or src-in).
Instead, their visibility should affect the activeness of the
floating-selection filter of the drawable they're attached to.
This is handled by the next commit.
2017-12-06 02:46:50 +08:00
|
|
|
if ((ignore_active || gimp_filter_get_active (GIMP_FILTER (layer))) &&
|
2017-05-09 04:02:37 +08:00
|
|
|
(ignore_excludes_backdrop || gimp_layer_get_excludes_backdrop (layer)))
|
|
|
|
{
|
|
|
|
gint index;
|
|
|
|
|
|
|
|
index = gimp_container_get_child_index (GIMP_CONTAINER (stack),
|
|
|
|
GIMP_OBJECT (layer));
|
|
|
|
|
2017-05-13 03:51:36 +08:00
|
|
|
gimp_layer_stack_update_range (stack, index + 1, -1);
|
2017-05-09 04:02:37 +08:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
gimp_layer_stack_update_range (GimpLayerStack *stack,
|
|
|
|
gint first,
|
|
|
|
gint last)
|
|
|
|
{
|
|
|
|
GList *iter;
|
|
|
|
|
2018-01-22 22:55:47 +08:00
|
|
|
g_return_if_fail (first >= 0 && last >= -1);
|
2017-05-09 04:02:37 +08:00
|
|
|
|
|
|
|
/* if the range is reversed, flip first and last; note that last == -1 is
|
|
|
|
* used to update all layers from first onward.
|
|
|
|
*/
|
|
|
|
if (last >= 0 && last < first)
|
|
|
|
{
|
|
|
|
gint temp = first;
|
|
|
|
|
|
|
|
first = last + 1;
|
|
|
|
last = temp + 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
iter = gimp_item_stack_get_item_iter (GIMP_ITEM_STACK (stack));
|
|
|
|
|
|
|
|
for (iter = g_list_nth (iter, first);
|
|
|
|
iter && first != last;
|
|
|
|
iter = g_list_next (iter), first++)
|
|
|
|
{
|
|
|
|
GimpItem *item = iter->data;
|
|
|
|
|
app: add GimpFilter::active property; move ::visible to GimpItem
Add an "active" property to GimpFilter, which replaces its
"visible" property. The new property assumes the lower-level role
"visible" had -- controlling whether the filter has any effect as
part of its parent filter-stack.
Add a "visible" property to GimpItem, separate from the "active"
property, which assumes the higher-level role "visible" had --
controlling whether the item is considered "visible", as per the
GUI. By default, the item's "visible" property is bound to the
filter's "active" property, so that changes in visibility directly
affect the filter's "activeness"; this binding can be controlled
using the new gimp_item_bind_visible_to_active() function.
This distinction is currently necessary for floating selections.
Floating selection layers must not be active in their parent stack,
regardless of their visibility, in particular, so that their mode
node doesn't hide the entire backdrop when their composite mode
excludes the backdrop (i.e., when it's dst-atop or src-in).
Instead, their visibility should affect the activeness of the
floating-selection filter of the drawable they're attached to.
This is handled by the next commit.
2017-12-06 02:46:50 +08:00
|
|
|
if (gimp_filter_get_active (GIMP_FILTER (item)))
|
2017-05-09 04:02:37 +08:00
|
|
|
{
|
app: maintain drawable bounding box separately from its logical boundary
Maintain the bounding box of drawables (i.e., the bounds of their
actual rendered content) separately from their logical boundary (as
shown in the UI).
The bounding box is calculated through the new
GimpDrawable::get_bounding_box() virtual function, which has a
corresponding gimp_drawable_get_bounding_box() function; the
default implementation simply returns the drawable's logical
boundary. The bounding box is specified in drawable coordinates,
i.e., it's not affected by the drawable's offset.
The bounding box is recalculated through
gimp_drawable_update_bounding_box(), which should be called
whenever a change may affect the bounding box (for example, when
setting a new buffer, as done implicitly by GimpDrawable's
::set_buffer() implementation, or when a drawable filter's
properties change, as will be done by GimpDrawableFilter in a
following commit). When the bounding box changes, the affected
regions of the drawable are updated, and the
GimpDrawable::bounding-box-changed signal is emitted.
When gimp_drawable_update() is called with negative width/height
values, the entire drawable's bounding box is updated, rather than
only its logical boundary.
Likewise, GimpDrawableStack and GimpLayerStack are adapted to use
the bounding box, instead of the logical bounds, when updating the
drawable's area.
2019-08-02 02:52:40 +08:00
|
|
|
GeglRectangle bounding_box;
|
2017-05-09 04:02:37 +08:00
|
|
|
|
app: maintain drawable bounding box separately from its logical boundary
Maintain the bounding box of drawables (i.e., the bounds of their
actual rendered content) separately from their logical boundary (as
shown in the UI).
The bounding box is calculated through the new
GimpDrawable::get_bounding_box() virtual function, which has a
corresponding gimp_drawable_get_bounding_box() function; the
default implementation simply returns the drawable's logical
boundary. The bounding box is specified in drawable coordinates,
i.e., it's not affected by the drawable's offset.
The bounding box is recalculated through
gimp_drawable_update_bounding_box(), which should be called
whenever a change may affect the bounding box (for example, when
setting a new buffer, as done implicitly by GimpDrawable's
::set_buffer() implementation, or when a drawable filter's
properties change, as will be done by GimpDrawableFilter in a
following commit). When the bounding box changes, the affected
regions of the drawable are updated, and the
GimpDrawable::bounding-box-changed signal is emitted.
When gimp_drawable_update() is called with negative width/height
values, the entire drawable's bounding box is updated, rather than
only its logical boundary.
Likewise, GimpDrawableStack and GimpLayerStack are adapted to use
the bounding box, instead of the logical bounds, when updating the
drawable's area.
2019-08-02 02:52:40 +08:00
|
|
|
bounding_box = gimp_drawable_get_bounding_box (GIMP_DRAWABLE (item));
|
|
|
|
|
|
|
|
bounding_box.x += gimp_item_get_offset_x (item);
|
|
|
|
bounding_box.y += gimp_item_get_offset_y (item);
|
2017-05-09 04:02:37 +08:00
|
|
|
|
|
|
|
gimp_drawable_stack_update (GIMP_DRAWABLE_STACK (stack),
|
app: maintain drawable bounding box separately from its logical boundary
Maintain the bounding box of drawables (i.e., the bounds of their
actual rendered content) separately from their logical boundary (as
shown in the UI).
The bounding box is calculated through the new
GimpDrawable::get_bounding_box() virtual function, which has a
corresponding gimp_drawable_get_bounding_box() function; the
default implementation simply returns the drawable's logical
boundary. The bounding box is specified in drawable coordinates,
i.e., it's not affected by the drawable's offset.
The bounding box is recalculated through
gimp_drawable_update_bounding_box(), which should be called
whenever a change may affect the bounding box (for example, when
setting a new buffer, as done implicitly by GimpDrawable's
::set_buffer() implementation, or when a drawable filter's
properties change, as will be done by GimpDrawableFilter in a
following commit). When the bounding box changes, the affected
regions of the drawable are updated, and the
GimpDrawable::bounding-box-changed signal is emitted.
When gimp_drawable_update() is called with negative width/height
values, the entire drawable's bounding box is updated, rather than
only its logical boundary.
Likewise, GimpDrawableStack and GimpLayerStack are adapted to use
the bounding box, instead of the logical bounds, when updating the
drawable's area.
2019-08-02 02:52:40 +08:00
|
|
|
bounding_box.x, bounding_box.y,
|
|
|
|
bounding_box.width, bounding_box.height);
|
2017-05-09 04:02:37 +08:00
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|