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 2155

Summary: Marks.Style:=smsLabel doesnt't work correctly
Product: VCL TeeChart Reporter: Jens Werschmoeller <jenswerschmoeller+steema>
Component: ChartAssignee: Steema Issue Manager <issuemanager>
Status: RESOLVED INVALID    
Severity: blocker CC: marc, yeray
Priority: ---    
Version: 26.181203   
Target Milestone: ---   
Hardware: PC   
OS: Windows   
Chart Series: --- Delphi / C++ Builder RAD IDE Version:
Attachments: Example Chart-Komponent-File

Description Jens Werschmoeller 2019-02-13 13:53:16 EST
Created attachment 885 [details]
Example Chart-Komponent-File

Currently, the new TeeChart version seems to automatically update the structure of existing DFM files to the new version. The use of the labels seems to be broken. It is currently not possible for me to use chart series with the display of labels.

I attach the used DFM file once. If this file is opened in the chart editor once and saved again, the display of the labels, which previously worked perfectly, no longer works.

The problem is a showstopper in use. I cannot currently make any adjustments to the chart component without breaking the correct showing of labels!
Comment 1 Jens Werschmoeller 2019-03-11 09:08:50 EDT
Whats the state? 
I pay every year for support and here is for critical bugs no support anyway. 

The issue is very uncomfortable for me, so that i couldn't go forward in the next release.
Comment 2 marc meumann 2020-09-25 06:59:08 EDT
Without an example project it is difficult to appreciate the problem that is occurring, the dfm is long. 

With respect to the incorrect saving of certain properties, please could you state exactly what behaviour is not as expected/required.

Temporary workaround:
We assume that it is the Axis Labels that are not responding to requirements. An interim workaround would be to copy the dfm code to an init procedure to be called at startup.
Comment 3 yeray alonso 2022-09-16 07:01:42 EDT
I'm closing this as "invalid" because we weren't able to reproduce the problem.
I'll be pleased to reopen it if we get a project we can run as-is to reproduce it.