Problem with internal TeeChart free notificaitions
Six months ago, Jim Bennett posted here saying there was "a problem with the
internal Teechart free notifications" ... "for some of the series which
reference other series, such as the function series classes".
I've just encountered the same problem with RB7, D7, TChart Pro 5.03, and a
trend line series function. TChart 6 has been released since then, but this
problem is not listed as having been fixed. (I haven't actually tried
version 6.)
So, is Ed Dressel's solution mentioned in the same thread (put a TppImage in
the report, save the chart to WMF, load it to the image) still the best
available, as far as we know?
(I also posted to the teechart newsgroup 5 days ago, but haven't had a
response there yet.)
Thanks.
Mike Carroll
Sigma Data Systems, Inc.
internal Teechart free notifications" ... "for some of the series which
reference other series, such as the function series classes".
I've just encountered the same problem with RB7, D7, TChart Pro 5.03, and a
trend line series function. TChart 6 has been released since then, but this
problem is not listed as having been fixed. (I haven't actually tried
version 6.)
So, is Ed Dressel's solution mentioned in the same thread (put a TppImage in
the report, save the chart to WMF, load it to the image) still the best
available, as far as we know?
(I also posted to the teechart newsgroup 5 days ago, but haven't had a
response there yet.)
Thanks.
Mike Carroll
Sigma Data Systems, Inc.
This discussion has been closed.
Comments
problem in their source is still there.
Cheers,
Jim Bennett
Digital Metaphors
http://www.digital-metaphors.com
info@digital-metaphors.com
rigamarole of copying it to an image. Decided instead to ignore access
violations in the destructor of the data module that attempts to free the
report & the chart it contains. Leaks memory, maybe? Don't really want to
know.
Dirty old world.
Mike Carroll
gets freed, but object1 holds a reference to object2 but isn't notified
when object2 gets freed. So when object1 references object2, it AV's because
the reference is now bad because object2 was freed. The free notificatin
relationship we spoke of would allow object1 to get notified that object2
was freed so object1 could nil its reference to object2 so it would know not
to make calls on object2:)
Cheers,
Jim Bennett
Digital Metaphors
http://www.digital-metaphors.com
info@digital-metaphors.com