After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 343804 - Scaling with lanczos not wirking with alpha channel
Scaling with lanczos not wirking with alpha channel
Status: RESOLVED FIXED
Product: GIMP
Classification: Other
Component: General
git master
Other All
: Normal major
: ---
Assigned To: GIMP Bugs
GIMP Bugs
: 344200 346590 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-06-04 10:04 UTC by B. Pedersen
Modified: 2006-07-05 08:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description B. Pedersen 2006-06-04 10:04:35 UTC 
Please describe the problem:
Scaling an image with alpha-channel give only a black image if using lanczos. 

Steps to reproduce:
1. Create an image with alpha channel
2. scale with lanczos
3. 


Actual results:
Instead of the scaled-down image you see only a black image.

Expected results:


Does this happen every time?
Yes

Other information:
Comment 1 weskaggs 2006-06-04 22:27:28 UTC 
I can confirm this, using either "Scale Image" or "Scale Layer" from the menu.  It doesn't happen when I use the Scale Layer tool, with interpolation set to Lanczos.  I think this must have shown up quite recently.
Comment 2 weskaggs 2006-06-05 22:47:22 UTC 
Looks like in code cleanups committed on 4-28-06, Sven accidentally changed a couple of variables from gdouble to gint, thereby causing this problem.  Fixed in cvs, unfortunately not quite in time for the 2.3.9 release.  Thanks for pointing this out.

2006-06-05  Bill Skaggs  <weskaggs@primate.ucdavis.edu>

	* app/paint-funcs/scale-funcs.c (scale_region_lanczos):
	fix variable declarations accidentally changed from gdouble
	to gint in revision 1.7; fixes bug #343804.
Comment 3 Sven Neumann 2006-06-07 20:01:59 UTC 
*** Bug 344200 has been marked as a duplicate of this bug. ***
Comment 4 Sven Neumann 2006-07-05 08:23:04 UTC 
*** Bug 346590 has been marked as a duplicate of this bug. ***