Closed (won't fix)
Project:
ImageCache Actions
Version:
6.x-1.5
Component:
Canvas Actions Module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
22 Apr 2009 at 20:57 UTC
Updated:
18 Mar 2016 at 18:33 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
dman commentedUm, what am I looking at here?
Are you using canvas to a background texture under the image?
Or are you setting the canvas background and expecting the image to get a fixed size but be a transparent jpeg?
transparent jpeg?
Comment #2
soupp commentedOh, right. The idea is to fill empty part of the image with background.
The compiled image size is 250x250 which should contain say 250x150 jpeg (resized in prev. imagecache action) + background to underlay empty 100px.
And of course there are no transparent jpegs, this part i know :)
Comment #3
soupp commentedAnd here is the screenshot of the preset.
Comment #4
dman commentedYes, I've been able to replicate.
It comes from a fairly recent change where I use imageapi_crop to handle the cases where a background image is bigger or smaller than the foreground.
Currently this can be avoided by commenting out one line in
canvasactions.inc:canvasactions_canvas2file_image()the crop was there to avoid extra processing on the per-pixel algorithm. Assigning a huge background (which is the only way to avoid tiling) was meaning that even small pictures took ages to process.
I'll try to find another way that doesn't use imageapi_crop. Or get imageapi to respect transparency.
Comment #5
soupp commenteddman, thank you for clarification and the magnificent module of course! I'll play with your hint on local, we'll see how it goes.
Comment #6
fietserwinD6 EOL. This module's D6 issues already haven't received any attention for over a year. Closing them all unconditionally now.