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 1155 - TabOrder not found when exporting a TChart and Importing to a TQRChart
Summary: TabOrder not found when exporting a TChart and Importing to a TQRChart
Status: RESOLVED NOTABUG
Alias: None
Product: VCL TeeChart
Classification: Unclassified
Component: Export (show other bugs)
Version: 150120
Hardware: PC Windows
: Lowest trivial
Target Milestone: ---
Assignee: Steema Issue Manager
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-02 06:59 EST by yeray alonso
Modified: 2015-05-11 09:12 EDT (History)
1 user (show)

See Also:
Chart Series: ---
Delphi / C++ Builder RAD IDE Version:

Attachments
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 yeray alonso 2015-03-02 06:59:44 EST 
A customer is trying move a TChart to a TQRChart.
If I do this I get an error saying "TabOrder not found":

var tmpStream: TMemoryStream;
begin
  tmpStream:=TMemoryStream.Create;
  SaveChartToStream(Chart1, tmpStream);

  tmpStream.Position:=0;
  LoadChartFromStream(TCustomDBChart(QRDBChart1), tmpStream);
  QRDBChart1.Parent:=QuickRep1;

Using CloneChart works fine.
Comment 1 david berneda 2015-05-11 09:12:40 EDT 
TabOrder cannot be made published in TQRChart or TQRDBChart.
For this property (and also any other properties not supported by QR controls), using LoadChartFromStreamCheck solves the problem.

function TForm1.SkipErrors(const Message: string): Boolean;
begin
  result:=True; // <-- True means: continue reading, ignore the exception(s)
end;

...
  LoadChartFromStreamCheck(TCustomDBChart(QRDBChart1), tmpStream, SkipErrors);


"SkipErrors" is a local function that returns True to avoid the exception and continue loading the chart.

Note: Running inside the IDE with debugging will still stop the application when the exception happens, pressing F9 (run) again will continue as expected.

Running "without debugging" will not stop at all.