This topic describes resolutions or solutions in GainSeeker version 9.4 and corrections to the Online User Guide.
|
Contents [Hide] |
Some activities were not logged to Audit Trail under certain conditions. These issues have been resolved. (Issue: GAIN-4203)
Activities that logged to Audit Trail did not always format the "Key" field in the same way. This issue has been resolved. (Issue: GAIN-4204)
When grouping an OEE chart or DPU chart by Day/Shift, the x-axis erroneously displayed the shifts in alphabetical order instead of displaying them in the same order as the Shift sequence configuration setting. This issue has been resolved. (Issue: GAIN-4208)
When grouping an OEE chart or DPU chart by Minutes, the current configuration's Start of work day setting was erroneously applied to the chart. This issue has been resolved. (Issue: GAIN-4211)
When displaying an OEE Detail Table, percentage values and cost values sometimes displayed too many decimal places. Percentage values are now rounded to two decimal places, and cost values display the number of decimal places configured by the retrieval setting Number of decimals for a cost value. This issue has been resolved. (Issue: GAIN-4202)
When displaying an OEE chart or DPU chart with two levels of grouping - first by traceability and then by any time increment less than an hour (from 1 Minute to 30 Minutes), the Legend for second-level grouping incorrectly displayed every time group as 00:00. The Legend now displays the second-level time groups correctly. This issue has been resolved. (Issue: GAIN-4195)
When displaying a Monitor Table, Paired Sample Chart or its associated Paired Sample Data window, if the chart setting Show statistics list under chart was enabled, an empty box was displayed below the chart (or grid) because no statistics lists are affiliated with these windows. These windows now ignore this chart setting. These issues have been resolved. (Issues: GAIN-4207 and GAIN-4210)
When an SPC Data Table is populated with External Data, using the right-click menu or Options menu to generate a Pareto chart of that data generated an "Object reference not set to an instance of an object" error. This issue has been resolved. (Issue: GAIN-4198)
When a chart window displayed the "No Chart Available" message, attempting to print this chart window would generate the error message "Object reference not set to an instance of an object". This issue has been resolved. (Issue: GAIN-4237)
When splitting a Multiple Charts chart into individual charts, not all chart settings chosen when creating the Multiple Charts were correctly applied to the split charts. This issue has been resolved. (Issue: GAIN-4239)
When brushing a chart while it was refreshing because of a refresh timer, GainSeeker Charts would occasionally crash or shut down unexpectedly. This issue has been resolved. (Issue: GAIN-4252)
When a dashboard displayed a chart control with a chart skin applied, right-clicking on that control and choosing Chart to generate a new chart window failed to apply the same chart skin to the new chart. This issue has been resolved. (Issue: GAIN-4253)
When launching GainSeeker Charts with the command line parameter daterange=3,2,6 , this module erroneously applied the date range "one quarter ending today" instead of the intended date range "6 months ending today". This issue has been resolved. (Issue: GAIN-4325)
When debugging a Python script, hitting a breakpoint in a script that was not displayed in the left-hand Script List (because e.g. a search filtered out that script) would cause the GainSeeker Inspections module to crash or shut down unexpectedly. This issue has been resolved. (Issue: GAIN-4199)
Running a Python script on a sub-inspection with a traceability test set to SPC Event, Cause, Action Taken, or DMS Event would erroneously clear these tests' values unless they were explicitly set in the script. This issue has been resolved. (Issue: GAIN-4219)
After changing the configuring setting for the user-defined label "Sample size" to display a longer label, the Defect List test failed to reduce this label's font size so the longer label might fit the space provided. This issue has been resolved. (Issue: GAIN-4231)
On a Numeric Input test using a Device Profile, the Device Profile could occasionally be triggered twice in a row for the same data cell and then not triggered at all for the next data cell - especially if the Device Profile ran very quickly. This issue has been resolved. (Issue: GAIN-4284)
An invisible or disabled Numeric Input test inside a block of contiguous Numeric Input tests with the TabDirection property set to "Down" would stop the sub-inspection from advancing to the next cell in this block that was visible and enabled. This issue has been resolved. (Issue: GAIN-4321)
On an inspection with the EnterKeyBehavior property set to "TabSubmit", on a sub-inspection where a Numeric Input test was the last test, entering a value in the last cell of that test and then pressing the ENTER key failed to Submit the sub-inspection. This issue has been resolved. (Issue: GAIN-4316)
A Rating test or Pass/Fail test would always use the sub-inspection's ForceNote property, even if the test's own ForceNote property was not set to "Use Sub-Inspection Settings". This issue has been resolved. (Issue: GAIN-4299)
Using a Python script to change the label of a Numeric Input test did not update the label that was used when entering a note for that test. This issue has been resolved. (Issue: GAIN-4222)
Executing a Python script that set the values of a Numeric Input test to null would prevent any Device Profiles from being triggered for that test. In addition, that test's vertical size was not updated, its tab direction was not updated, and its real-time failures were not recalculated. These issues have been resolved. (Issue: GAIN-4268)
Executing a Python script that first set the values of a Numeric Input test to null and then accessed that test's .subgroupcomplete property would crash with the error "Object reference not set to an instance of an object". This issue has been resolved. (Issue: GAIN-4269)
When sending files as attachments with the email.send() command, GainSeeker would not release its lock on the file until the application was closed, instead of releasing the lock after the email was sent. This issue has been resolved. (Issue: GAIN-4191)
When a script to read an Excel file executed file.xls.getcell.() to read a cell that is merged with other cells - or executed file.xls.getrow() to read a row that contained a cell that is merged with other cells - and that merged cell's Number Format was not set to "General", and that cell's value could not be parsed as a number, GainSeeker would display a "PartialMergedCell" error. This issue has been resolved. (Issue: GAIN-4308)
When setting Tables and File Paths, changing a file path and selecting the first path in the list would generate the following Unhandled Exception error message: "The given key was not present in the dictionary." This issue has been resolved. (Issue: GAIN-4247)
Creating a new user and setting its configuration before clicking Submit failed to set that user to any configuration except "Default Settings Configuration". This issue has been resolved. (Issue: GAIN-4328)
In the Audit Trail utility, when defining the Audit Filter by the Audit Type column, the pre-defined list of Values did not include many audit types such as Dashboard, Desktop, Inspection, or Python Script. This list has been updated to include all audit types that may be logged to the Audit Trail. This issue has been resolved. (Issue: GAIN-4188)
When using the Standard Utility to duplicate standards, using
the Replace function to search
for a text string that was not contained in some of the selected standards
and then choosing "Replace" when prompted for duplicates
would delete those existing standards.
This utility could also delete existing standards when using the Replace function if both the Replace and With
boxes were left blank, if the Replace
and With boxes contained the
same value, or if the Replace
box was left blank and the With
box contained only whitespace (such as spaces). Similarly, existing
standards could also be deleted when using the Append
function with the Add to end
box left blank (or containing only whitespace).
These issues have been resolved. (Issue:
GAIN-4337)