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 2628 - Access Violation upon close if chart in Main VCL app and also in DLL's VCL form; TInvertFilter error upon load with more complex program
Summary: Access Violation upon close if chart in Main VCL app and also in DLL's VCL fo...
Status: RESOLVED WORKSFORME
Alias: None
Product: VCL TeeChart
Classification: Unclassified
Component: Chart (show other bugs)
Version: unspecified
Hardware: PC Windows
: --- blocker
Target Milestone: ---
Assignee: Steema Issue Manager
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-08-18 11:31 EDT by Tammy Woodard
Modified: 2023-08-18 15:03 EDT (History)
1 user (show)

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

Attachments
Code to test the error upon close when calling a chart inside a DLL (102.84 KB, application/x-zip-compressed)
2023-08-18 11:32 EDT, Tammy Woodard 		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 Tammy Woodard 2023-08-18 11:31:53 EDT 
Re: 'A class named TInvertFilter already exists' error in TeeChart Pro 2022.35

Post by TWoodard » 18 Aug 2023 14:59
I have the same problem. I believe the problem is caused by having a TChart in your main program and having one in a DLL that your program calls. I'm not sure exactly.

I have a huge program that has this problem and it has been driving me crazy. This program also has a COM object in the main app and has charts in the main app and in the DLLs.

I created a pared down program that barely has any code. It has a main program (VCL form) with a TChart on it, and a Dll that contains a VCL form with a chart on it. It now doesn't have this exact problem (the TInvertFilter already exists problem), but it does create an Access Violation upon close. Here are the circumstances where it occurs:

1. If the main program does not have a chart on it, the error does not occur.
2. If the main program *does* have a chart on it, but when you call the DLL, you don't show the DLL's chart (you do something minor like a showmessage instead), then no error occurs.
3. If the main program has a chart on it, and you call the DLL to show its chart. You can close that DLL's chart, then close the main app, and then you will get an Access Violation... every time.

I installed the latest TeeChart Std downloaded today and I still have this problem. I previously was using the TeeChart that came with Rad11.3 Delphi, but couldn't access tech support or the forum unless I bought it directly from Steema. So I bought it, and downloaded the latest and now I just need to get some help on this (guidance or bug fix).

Change: 
-I was just gathering up the stuff to attach and I have a program that does not have a chart on the main app (the exe), but does still have the A/V error when closing if you call a chart in on a VCL form in a DLL.  I'll attach that.

Thanks,

Tammy
Comment 1 Tammy Woodard 2023-08-18 11:32:40 EDT 
Created attachment 1054 [details]
Code to test the error upon close when calling a chart inside a DLL
Comment 2 Tammy Woodard 2023-08-18 15:03:37 EDT 
Now that I have posted a detailed description of my problem and created pared down projects, I re-read the original response to the original question and decided to look at it all again.

Indeed, removing all Runtime Packages listed in the Compiler Options of the DLL and the EXE (not sure if it was necessary in both, but definitely was necessary in the DLL), I was able to run it without getting that TInvertFilter Error or the error upon crash.

I hadn't added any Runtime Packages myself and I had created very basic projects with barely anything in them, so it is surprising that there are so many packages added automatically.  I haven't isolated which particular package causes the conflict, but am happy to report that I am able to move forward now and work on the details of the chart.

I am using RAD11.3 in a Windows Environment.  Everything is up to date.