Problem with transparency when generating PNG images.
Posted: Tue Nov 28, 2006 4:32 am
Hi,
I've only recently upgraded to TeeChart Professional 7 (with source code), and have run into what appears to be a bug. Here's some background: my application saves .png and .tee files of charts. The .png files are then embedded within reports displayed using a Web browser window in my application, but I allow the user to edit these images by clicking on them in the browser. This triggers an editing dialog which operates on the corresponding .tee file. This all works fine. The problem I'm seeing occurs with charts which include a TColorBandTool with a transparency of 80, which I use to create backgrounds on these charts. When the user saves a chart to png format from the dialog, these color bands use solid color, not transparency.
Since I have the source code version, I've been able to look into this a bit, and I found that removing the line in CustomTeePanel.NonBufferDraw which sets IKeepBitmap to true corrects the problem.
Is this a known bug? Should I try to provide you with a simpler example?
Thanks,
Eric Zurcher
CSIRO Plant Industry
Canberra, Australia
I've only recently upgraded to TeeChart Professional 7 (with source code), and have run into what appears to be a bug. Here's some background: my application saves .png and .tee files of charts. The .png files are then embedded within reports displayed using a Web browser window in my application, but I allow the user to edit these images by clicking on them in the browser. This triggers an editing dialog which operates on the corresponding .tee file. This all works fine. The problem I'm seeing occurs with charts which include a TColorBandTool with a transparency of 80, which I use to create backgrounds on these charts. When the user saves a chart to png format from the dialog, these color bands use solid color, not transparency.
Since I have the source code version, I've been able to look into this a bit, and I found that removing the line in CustomTeePanel.NonBufferDraw which sets IKeepBitmap to true corrects the problem.
Is this a known bug? Should I try to provide you with a simpler example?
Thanks,
Eric Zurcher
CSIRO Plant Industry
Canberra, Australia