Bugs Newly Fixed in 8.5.1 SR1



Analysis

NLFit

JIRA Summary Details
ORG-2723 Script After Fitting did not work in SR0. Script After Fitting allows the user to define a script to run after a fit is completed. This feature failed in SR0 for built-in and user-defined functions when defined on either the Code tab of the Nonlinear Curve Fit (NLFit) dialog, or in a Fitting Function (FDF) file. Script After Fitting has been fixed in SR1.
ORG-2707 If a user-defined fitting function (FDF file) was not in the same category as specified in the .opj, Change Parameter did not work. This occurred when users shared .opj and FDF file on different Origin installations. (Typical scenario: User A creates a user-defined FDF under a specific category and an .opj with a fitting using that function, then shares these files with User B. User B does not place the FDF file into the same category as User A, and tries to Change Parameters. This fails because Origin can not find the FDF file.) This has been fixed in SR1 so that Origin automatically locates the FDF file.

Multiple Peaks Fit

JIRA Summary Details
ORG-2853 In SR0, Origin (standard) users could not run the Multiple Peak Fit tool. When Origin (standard) users tried to use the Multiple Peak Fit tool, this error appeared in the script window: "failed to find object during method call. Origin C error(24) in X-Function code." This did not occur in OriginPro. The Multiple Peak Fit tool is functional in Origin 8.5.1 SR1.

Integration

JIRA Summary Details
ORG-2751 In SR0, the absolute area calculated with the Integrate gadget was incorrect. When Absolute Area was calculated with the Integrate gadget, the result was identical to the Mathematical Area. This has been fixed in SR1 so that the correct Absolute Area is calculated and displayed.

Others

JIRA Summary Details
ORG-2969 Recalculate was not being triggered in cases where the input was a second-generation linked cell. After an analysis or fitting, a report table is created in a graph. This table has an intermediate table associated with it. Most cells in the intermediate table are links to a hierarchy result sheet. Users may copy cells from this intermediate table, paste them into another worksheet, and perform further calculations (e.g., Set Column Value) with this linked data. In SR0, recalculating the original analysis or fit did not trigger an update in these chained calculations.
ORG-2240 In SR0, hidden tables were not deleted when a user deleted a fit operation from a graph. After an analysis or fitting, a report table is created in a graph. This table has an intermediate table associated with it. When a user deletes the analysis or fitting, the associated table should be deleted with it. In SR0, this table was not deleted with the analysis or fitting.
ORG-2240 In SR0, no report table was being placed on the graph when Recalculate mode was set to None. When doing analysis in a Graph window, if the Recalculate Mode was set to None, no report table was created on the graph after the analysis.

Graphing

JIRA Summary Details
ORG-196 Users were unable to copy and paste break settings from one axis to another. When users copied break settings from one axis and pasted the formatting onto another axis, the break settings were not being carried over to the destination axis. (To reproduce in SR0: Right-click on an axis with customized break settings, select Copy Format: All. Then right-click another axis, or an axis in another graph, and click Paste Format. Observe that break settings are not pasted.) This has been fixed in SR1.
ORG-2542 Users were unable to copy and paste customized tick positions from one axis to another. When users copied customized tick positions and pasted the formatting onto another axis, the customized tick settings were not carried over to the destination axis. (To reproduce in SR0: Right-click on an axis with custom tick positions, select Copy Format: All. Then right-click another axis, or an axis in another graph, and click Paste Format. Observe that custom tick positions are not pasted.) This has been fixed in SR1.
ORG-1418 Wrong direction of dual color grid lines for X Grid Lines Only or Y Grid Lines Only in Wire Frame Surface. When X Grid Lines Only or Y Grid Lines Only was selected in the Wire Frame tab of the Plot Details dialog, the Second Color grid lines were displayed in the wrong direction. This resulted in the display of both X and Y grid lines when the user wanted only X or Y grid lines.
ORG-1418 Dual-color was not working when a graph layer contained more than just a single wireframe plot. When a graph layer contained more than just a single wireframe plot (for example, a wireframe plot and a 3D scatter plot, or two wireframe plots), the second-color grid lines were not displayed. Dual-color plots now display properly with more than just one wireframe plot in a layer.

Gadgets

JIRA Summary Details
ORG-2872 Gadget unresponsive when copying layer. When users copied a layer containing a gadget and pasted into the same graph, then clicked the gadget's context menu, there was no response. (To reproduce in SR0, import the sample data file Gaussian.dat. Select column B and plot it as a line graph. In Origin’s main menu, click Gadgets, then Quick Fit, and then Peak–Gauss. Right-click the layer and select Copy. Click the right-triangle button. Observe this error in the Script Window: TreeNode does not exist, access denied.) This has been fixed in SR1 so that clicking the right-triangle button brings up a context menu.
ORG-2836 In SR0, the label on top of a gadget (such as Quick Peaks) did not move with the ROI if it was restored from a deleted layer. The label associated with a gadget did not move with ROI when it was restored from a deleted layer. (To reproduce in SR0, select one layer of a multi-layer graph. In Origin's main menu, click Gadgets, and then click Quick Peaks. Click OK to accept the default settings. Now delete the layer with the ROI. Click Undo to bring the layer back. Move the ROI around and observe that the "peak(s) found" label has become disassociated with the ROI.) This has been fixed in SR1 so that the label remains associated with the ROI.

Statistics

JIRA Summary Details
ORG-2918 Failure to output Mean Comparison table by Change Parameters in ANOVA analysis. In SR0, users could not generate a Mean Comparison table using the Change Parameters dialog in an existing ANOVA result. This has been fixed in SR1.

Workbook

JIRA Summary Details
ORG-2761 In SR0, Chained Set Column Value calculations failed to be triggered. Example:
User wants to set up a worksheet template with columns A, B, C, and D.
Columns A and B are for new data imported.
Column C's Set Column Values formula is a fixed value, and there is a Before Formula Script so Recalculation Mode can be set to Auto.
Column D is dependent on Column B and C and Recalculation Mode is set to Auto.

In SR0, if the user imported data into columns A and B, column D's Set Column Value would fail to automatically execute.

ORG-2734 Worksheet selection display has been improved in SR1. When the user selected a row or column, then dragged to expand the selection, the screen seemed to flash. This was annoying and uncomfortable for the user, and has been fixed in SR1.

Import and Export

JIRA Summary Details
ORG-2733 When users chose to import from Excel, Excel was launched before Origin's Excel import dialog appeared. In cases where the file was very large, a "Server Busy" dialog appeared, confusing users and complicating the import. Even with small files, this behavior was often problematic, especially if Excel had been installed on the system but not yet used. This has been fixed in SR1 so that Excel is not launched until after the user clicks the OK button on the import dialog.

LabTalk

JIRA Summary Details
ORG-2926 In SR0, LabTalk interpolation notation gave incorrect values when executed in a loop using a range variable. To recreate in SR0, fill three columns with row numbers, random numbers, row numbers, and then run the following code:
loop(i,1,2) {range a=(1,$(i+1));a(1)=};

This has been fixed in SR1

ORG-3572 In Origin 8.5, passing argument by reference in user defined LT function does not work Example:
newbook;
string fname$=system.path.program$+"\Samples\Curve Fitting\Gaussian.dat";
impASC;
Function int GetMinMax(range rr, ref double min, ref double max) {
  stats rr;
  min = stats.min;
  max = stats.max;
  return stats.N;
}

double y1,y2;
int nn = getminmax(1:end,y1, y2);
type "Worksheet has $(nn) points, min=$(y1), max=$(y2)";

This has been fixed from Origin 8.51 SR0

Licensing

JIRA Summary Details
ORG-2826 Dongle failed to be recognized after upgrading from 8.5 SR1 to 8.5.1 SR0. The dongle was not being recognized after users upgraded from 8.5 SR1 to 8.5.1 SR0. This necessitated a manual workaround which is no longer required in 8.5.1 SR1.

Miscellaneous

JIRA Summary Details
ORG-2849 Dialog positions continually changed each time they were opened if the taskbar was docked on the left side of the screen. This occurred when the Windows task bar was docked on the left side of the screen with autohide turned off. Each time the user opened certain dialogs (Export Graphs, for example), the dialog box shifted further to the left, eventually moving off the screen. The only workaround was to turn the task bar's autohide off. This has been fixed in SR1 so that dialog boxes appear in the same locations each time they are opened, regardless of the task bar's position.
ORG-2779 Running Origin from the command line with -ocw, OC workspace was empty. Example: User saves an OriginC workspace file (*.ocw) in Code Builder with OC files included, then runs Origin from the command line with this syntax: Origin85.exe -ocw c:\test\STARTUP.OCW.

All OC files included in *.OCW should be compiled automatically and functions should be ready to be used. This failed in SR0.

ORG-2848 Origin crashed when using the Copy Page or Send Graph to PowerPoint command when graph data originated in Excel. When users opened data in Origin that originated in Excel, then generated a graph and selected Copy Page or Send Graph to Powerpoint, Origin crashed. This has been fixed in SR1.