| Author |
 Topic  |
|
|
Frank_H
Germany
Posts |
 Posted - 12/11/2005 : 8:18:59 PM
|
Hi,
I just spent a few hour with Curve_bspline. Although my problem is now solved, I still would like to understand it - and perhaps spare others a few hours.
When using
Curve_bspline(sourceCrv,destCrv)
to fit a spline to some data and then plot destCrv, everything went well. But then I added some further processing of destCrv, and the results seemed to implicate, that destCrv was not changed by Curve_bspline. But still it plotted fine in the test. Finally (after hours :-( ) I added
destCrv.Update(TRUE)
and suddenly it worked!
Does this mean, that Curve_bspline does not actully work as an OriginC command but is instead invoking a LabTalk command without updating the OriginC copy of the curve?
Cheers,
Frank |
|
|
cpyang
USA
1406 Posts |
Posted - 12/14/2005 : 10:39:06 AM
|
Hi Frank,
Looks like this is a bug. A tracking number 8408 has been assigned for this to be fixed.
You are correct that Curve_bspline is making use of old LabTalk commands internally. In the next version of Origin, most of these data processing functions are calling a new DLL based on NAG functions and all the passing of data will be via vectors so the process will be very clear and will not have these type of problems resulted from OriginC trying to use old LabTalk codes.
CP
|
 |
|
|
Frank_H
Germany
Posts |
Posted - 12/14/2005 : 1:22:58 PM
|
Hi CP
I am really looking forward to Origin 8! Seems it will solve a lot of issues raised by the current implementation of OriginC.
Frank |
|
|
| |
Topic |
|
|
|
Curve_bspline driving me mad