RSS/Atom feed Twitter
Site is read-only, email is disabled

Light and Shadow - Drop Shadow an Bevel

This discussion is connected to the gimp-docs-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

2 of 2 messages available
Toggle history

Please log in to manage your subscriptions.

Light and Shadow - Drop Shadow an Bevel Ulf-D. Ehlert 30 Sep 20:48
  Light and Shadow - Drop Shadow an Bevel Sven Neumann 01 Oct 08:18
Ulf-D. Ehlert
2007-09-30 20:48:16 UTC (about 17 years ago)

Light and Shadow - Drop Shadow an Bevel

Hi,

did anybody ever use this filter? It should "add a drop shadow to a layer, and optionally bevel it", but it seems to do nothing useful.

According to the source code, this filter

1. creates a copy of the drawable, 2. fills it with white,
3. blurs this plain white layer (does this make sense?), 4. uses this plain white layer as a bump map (or this?), 5. inverts it.

The result is a black layer below the drawable, optionally moved by the Diplacement options (without resizing the image).

Do I miss something? How is this filter to be used?

Ulf

Sven Neumann
2007-10-01 08:18:16 UTC (about 17 years ago)

Light and Shadow - Drop Shadow an Bevel

Hi,

On Sun, 2007-09-30 at 20:48 +0200, Ulf-D. Ehlert wrote:

did anybody ever use this filter? It should "add a drop shadow to a layer, and optionally bevel it", but it seems to do nothing useful.

According to the source code, this filter

1. creates a copy of the drawable, 2. fills it with white,
3. blurs this plain white layer (does this make sense?),

Doesn't seem to make any sense to me.

4. uses this plain white layer as a bump map (or this?), 5. inverts it.

The result is a black layer below the drawable, optionally moved by the Diplacement options (without resizing the image).

I have the impression that this Python script can serve as an example for scripting GIMP with Python but that seems to be about the only use that it has. We should probably not install it in a stable release then. Could you perhaps open a bug report for this issue so that we can sort it out quickly before the 2.4.0 release?

Sven