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 1158 - Examples\Visual Studio .NET\Vc++ sample
Summary: Examples\Visual Studio .NET\Vc++ sample
Status: RESOLVED FIXED
Alias: None
Product: ActiveX TeeChart
Classification: Unclassified
Component: Examples Demo (show other bugs)
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Steema Issue Manager
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-05 23:40 EST by Shinobu Nagai
Modified: 2015-04-16 11:42 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 Shinobu Nagai 2015-03-05 23:40:50 EST 
Is it possible run the Examples\Visual Studio .NET\Vc++ sample included in the latest version (v2014.0.0.3) at your end?
If so, which VS version did you use? Dod you open either solution or project file?
Comment 1 sandra pazos 2015-03-06 11:16:16 EST 
Hello Nagai,

There is necessary include the seriespointeritem class in the dragging project. We have already fixed the problem. Meantime, you can include the seriespointeritem.cpp and seriespointeritem.h files in the Dragging.vcproj. 

Thanks in advance,
Comment 2 Shinobu Nagai 2015-04-15 22:42:18 EDT 
Hello,

We downloaded and installed the latest version (v2015.0.0.0).

This issue exists in v2015, as well. Status is represented as RESOLVED FIXED.
If .NET\Vc++ sample can be executed correctly at your end, could you tell me the VS version and the exact steps to run it without any error?

Thank you in advance,
Comment 3 sandra pazos 2015-04-16 11:42:37 EDT 
Hello Nagai,

Sorry, the bug wasn't fixed for the latest TeeChart Activex version v2015.0.0.0. Now, I confirm you the bug is already fixed for next maintenance release. 

Thanks in advance, 
regards.