Hi Sandra,
yes, this overlaoded function works. One should not expect too much performance loss. And yes, the effort to change my code is acceptable for me, too.
But I still think the .Value property should be the same for source and destination series after applying the .assign methods...
Best regards
Uli
Series.Assign and Series.AssignValues problem
-
Narcís
- Site Admin
- Posts: 14730
- Joined: Mon Jun 09, 2003 4:00 am
- Location: Banyoles, Catalonia
- Contact:
Re: Series.Assign and Series.AssignValues problem
Hi Uli,
Excellent! I'm glad to hear that.yes, this overlaoded function works. One should not expect too much performance loss. And yes, the effort to change my code is acceptable for me, too.
As demonstrated here, Assign makes an exact copy of one series to the other. ValueList.Values is a public public array. It was designed primarily for internal use only but was made public for advanced users of TeeChart. The length of this property is not guaranteed to be the same length as the ValueList.Count property. We think it is this ambivalence which is causing the problem discussed on this thread.But I still think the .Value property should be the same for source and destination series after applying the .assign methods...
Best Regards,
| Narcís Calvet / Development & Support Steema Software Avinguda Montilivi 33, 17003 Girona, Catalonia Tel: 34 972 218 797 http://www.steema.com |
      |
| Instructions - How to post in this forum |
Re: Series.Assign and Series.AssignValues problem
Hi Narcis,
Best regards
Uli
OK, when this is your intention... But to reduce such ambivalency a little bit a hint to such limitations in the TeeChart help would be valuable.ValueList.Values is a public public array. It was designed primarily for internal use only but was made public for advanced users of TeeChart. The length of this property is not guaranteed to be the same length as the ValueList.Count property. We think it is this ambivalence which is causing the problem discussed on this thread.
Best regards
Uli