Steema Issues Database

Note: This database is for bugs and wishes only. For technical support help, if you are a customer please visit our online forums;
otherwise you can use StackOverflow.
Before using this bug-tracker we recommend a look at this document, Steema Bug Fixing Policy.



Bug 910 - Grid3D Style=Strong not exported/imported
Summary: Grid3D Style=Strong not exported/imported
Status: RESOLVED FIXED
Alias: None
Product: .NET TeeChart
Classification: Unclassified
Component: Exporting (show other bugs)
Version: TeeChart.NET 2014 4.1.2014.02060
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Steema Issue Manager
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-05 04:37 EDT by sdgr
Modified: 2014-10-14 07:08 EDT (History)
2 users (show)

See Also:
Chart Series: Surface 3D
Delphi / C++ Builder RAD IDE Version:

Attachments
Sample project (16.51 KB, application/x-zip-compressed)
2014-09-05 04:37 EDT, sdgr 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description sdgr 2014-09-05 04:37:09 EDT 
Created attachment 286 [details]
Sample project

Hi,
I created a sample solution to demonstrate.
The Series Grid 3D Palette Style=Strong doesn't get saved when I export my chart and later on import it again.
All other styles like Grayscale, Rainbox,... gets saved.

After saving a chart with Series Grid 3d Palette Style=Strong, importing it again sets the Style=Pale.

Is there something else that prevents to set the Style to Strong?

Thanks for your help.
Stefan.
Comment 1 sdgr 2014-09-05 04:45:06 EDT 
This was already reported in Bug 668 and resolved.
I am afraid this is not fixed yet.
I am using version 4.1.2014.8122.
Comment 2 christopher ireland 2014-10-14 07:08:44 EDT 
Apologies for this slip. It does seems that that particular revision has disappeared from our VCS. I have added it in again. In the meantime you will be able to use the workaround I mentioned in the previous bug report. Again, apologies for this error on our part.