Hello. I've had a couple problems with using AX7 in Visual Studio .NET 2003(VC++). Firstly, after I insert the ActiveX control in the resource editor, if I go to the "Series" tab, I get an access violation:
Access violation at address 0F506804 in module 'TeeChart7.ocx'. Read of address 0000001C.
Secondly, I have the ActiveX control in a CAxDialogImpl<> class, and for some reason, the window isn't being destroyed properly-- only when the Teechart activeX control is on it(other activex controls work fine).
Any ideas?
Thanks.
--
Derek
Problems with AX7 with ATL7/VS .NET 2003
Hi Derek,
does this happens using the latest TeeChart Pro ActiveX v7.06 (available on our web site) ?
I've test it here and it seems to work fine. If you still having problems with the latest version, please post a simple example into the news://www.steema.net/steema.public.attachments newsgroup with the steps we should do to reproduce them.
does this happens using the latest TeeChart Pro ActiveX v7.06 (available on our web site) ?
I've test it here and it seems to work fine. If you still having problems with the latest version, please post a simple example into the news://www.steema.net/steema.public.attachments newsgroup with the steps we should do to reproduce them.
Pep Jorge
http://support.steema.com
http://support.steema.com
Pep wrote:Hi Derek,
does this happens using the latest TeeChart Pro ActiveX v7.06 (available on our web site) ?
I've test it here and it seems to work fine. If you still having problems with the latest version, please post a simple example into the news://www.steema.net/steema.public.attachments newsgroup with the steps we should do to reproduce them.
I downloaded the version posted in the Client Access area right before posting, so it seemed to happen with that. I didn't restart VS.NET 2003, nor reboot, so I'm not sure if that would affect it...
I'm considering using the IDispatch interface(with a CDispatchPtr class I use to make things easy) and saving graphs to temporary files(or possibly streaming it). This way I can offer graph creation for my product through the product's API. This would make the two problems above a non-issue to me. I wrote a prototype and it seems to work fine, so my only concern going forward would be any potential performance problems using this method, which I'll have to address when I get to that.
Thanks.
--
Derek