php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #33467 ImageCreate function now acts oddly - WHY?
Submitted: 2005-06-24 17:17 UTC Modified: 2005-06-24 23:23 UTC
From: m02041952 at yahoo dot com Assigned: pajoye (profile)
Status: Not a bug Package: GD related
PHP Version: 5.0.4 OS: win98
Private report: No CVE-ID: None
 [2005-06-24 17:17 UTC] m02041952 at yahoo dot com
Description:
------------
I feel unhappy because 'enhancements' performed from ImageCreate to ImageCreateTrueColor. Now I have problems that appears to be impossible of solving.
 
I was obligued to move to ICtrueColor because my pictures suddenly lost all its colors from day to night. In desperation I discovered that some genious had 'increased' GD functions.
 
First at all, have you measured file size of your ImageCreateTrueColor 'thumbnails'?  . Ok, for me they increased from 2 or 3 Kb (previous ImageCreate) to some 15 to 20 Kb each one (new ImageCreateTrueColor function), so my 'thumbnails albums' which should show some 25-50 tiny pictures in a flash, became unavailable for non-adsl users. I remember old fashioned days when my album opened thumbnails like pop-corns, all of them whth perfect colors. 
 
Second, I have zoom commands on these thumbnails. Previously zoom worked fine with ImageCreate because it performed task of reducing kb traffic between server and client, but with ImageCreateTrueColor now this traffic has INCREASED, because a true color image transmit several times more bits than even original image stored in server. 
 
Third, now I can't any more produce thumbnails of images from some sizes. I am still trying to figure out what the hell this problem could be, but with previous ImageCreate function images of 1200 x 1300 or so was created instantly with no problem. Now browser just shows users an 'incorrect image' icon instead. I don't know where the problem is, my images have not changed at all.
 
I want to say to people who develops GD that many (maybe ten thousands) users probably use these functions in their albums, then you can't just change functions performance / behaviour and say 'hi, use this new command instead now' with no previous analisys of performance and impact on actual systems. 
 
The correct way of making these changes is by letting untouched functions that are well stablished in the market (like previous imagecreate) and to develop new ones. 
 
Why you destroyed old ImageCreate to make the new function ImageCreateTrueColor? . I can't understand this
 
Thanks very much for your attention.
 
Miguel  - Brazil   Jun 2005.




Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2005-06-24 23:23 UTC] pajoye@php.net
Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to report
a bug at http://bugs.php.net/how-to-report.php

We did not destroy anything. Both exists.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Fri May 03 23:01:30 2024 UTC