This topic describes resolutions or solutions in GainSeeker version 8.7 and corrections to the Online User Guide.
|
Contents [Hide] |
Beginning with this version of GainSeeker, the MariaDB database is not supported for use as the GainSeeker database.
While editing a saved filter with several filter conditions (enough to display a vertical scrollbar), adding a new filter condition would display the new filter condition incorrectly. This issue has been resolved.
Deleting all defects from a DMS data record did not reset the "Sum Defects" field for that record. For instructions on checking your system for DMS data records where the actual defect counts do not add up to the value in the "Sum Defects" field, click here. This issue has been resolved.
When a numeric field is empty, such as an SPC specification limit field when no limit is present, GainSeeker stores a special value in that field (and not the number 0). When workstations were upgraded from Oracle database client version 11 to version 12c, some GainSeeker modules such as SPC Data Entry, SPC Charts and Reports, and DMS Charts and Reports were no longer able to read this special value correctly, and a number was displayed instead of a blank. This issue has been resolved.
When editing an SPC standard, the Limits tab did not format limit values based on the Decimal Places setting on the General tab. This issue has been resolved.
Creating charts sometimes generated the error message "System.ArgumentException: String cannot be of zero length. Parameter name: oldValue". This issue has been resolved.
When Previous Variation Wizard was used to launch multiple chart windows, some functions such as Duplicate Chart did not work correctly. This issue has been resolved.
When using the GainSeeker Charts module to delete or create standards and/or processes, the lists of standards and processes for a New SPC Chart or a New DMS Chart would not be updated until the next time the user launched or logged in to the GainSeeker Charts module. This issue has been resolved.
On a Dashboard grid of DMS data where Rows defined by was a traceability field, right-clicking on a cell in the grid and choosing View data would incorrectly indicate that no data existed for that cell. This issue has been resolved.
When displaying a Dashboard grid of DMS data where the Cell Display Format property was used to format the data, GainSeeker would sometimes generate an error message. This issue has been resolved.
When creating a chart from a dashboard, the default chart skin was not applied. This issue has been resolved.
Refreshing custom statistics on a timer - especially when displayed on a dashboard grid - would eventually crash the GainSeeker Charts module due to a memory leak. This issue has been resolved.
When a web browser was added to a Python dashboard control and the dashboard was set to refresh on a timer, the GainSeeker Charts module would eventually run out of memory. This issue has been resolved.
When editing data and setting the Update Monitor Info checkbox, the monitor information did not always get updated. This would happen when a value was entered in traceability field 7 or higher so that an auxiliary record needed to be created. This issue has been resolved.
When displaying a DPU chart, if the high date retrieved was one of the last two days of the calendar year, GainSeeker would generate an "out of memory" error message. This issue has been resolved.
When displaying a Process Capability chart and choosing to show the data values, the system would halt unexpectedly if no specification limits where set for one of the standards being displayed. This issue has been resolved.
When opening a dashboard with changes, if the dashboard contained only DMS retrievals, the filter area indicated erroneously that SPC filters were present. This issue has been resolved.
When opening a dashboard with changes, selecting a retrieval with a colon in the name would generate an error message. This issue has been resolved.
Creating or changing a Device Profile always saved the Parity setting as "None", regardless of the Parity setting chosen by the user. This issue has been resolved.
When copying a test and pasting it into a sub-inspection, the new test appeared to be selected but was not selected on the Property grid. Also, clicking the arrow buttons to move the new test up or down in the list would generate an error message. These issues have been resolved.
When adding SPC charts to an inspection, the Maximum count for retrieval setting was initially set to "Not Set" instead of the system default value for this setting. This issue has been resolved.
A Traceability test is supposed to be filled with one of these values (in order): the value set in a Planned Inspection (if used), the value of the TraceabilityPrep test property (if set), the value set previously in the same inspection (e.g. in a previous sub-inspection), or the value remembered from a previous inspection.
However, when the EntryRestricted property of a Traceability test was set to True, the wrong order was used to determine which of these potential prefill values would be used, and the wrong value was sometimes used to prefill that test - or no value was prefilled even though a value had been set (e.g. in the Planned Inspection). This issue has been resolved.
In a sub-inspection with a Formula test where the FormulaMode property was set to OnChange, when the user clicked one of the buttons for a Pass/Fail test, the color for that button would disappear while the mouse hovered over that button. This issue has been resolved.
To set up a scheduled task that would run a Python script in PC Collect, the 'working folder' or 'Start in' location had to designate the GainSeeker installation folder (not in quotation marks). Beginning with GainSeeker version 8.7, this working folder is not required for such a scheduled task to function properly.
In previous versions, setting multiple email addresses in the CheckFailureResponse property of an Inspection failed to send an email when the AutoSendRTFEmail property was set to True. This issue has been resolved.
Setting the Device Profile of a numeric input via Python would not actually enable/disable the device profile functionality. This issue has been resolved.
In previous versions, connection errors could occur if the device profile was disabled in a Formula test where the FormulaMode property was set to Pre. Inspection data entry now waits to establish serial port connections until the user enters the first cell in a Numeric Input test. This issue has been resolved.
In a Numeric Input test, no subgroup failure messages were displayed when the subgroup generated a real-time failure. This issue has been resolved.
If a single inspection with many numeric inputs was running for a significant amount of time, the PC Collect module would eventually crash. This issue has been resolved.
When a SQL Query Python Action was set to Use saved connection, editing that Python Action would sometimes show the wrong Saved Connection. This issue has been resolved.
Creating or changing a Serial Setup Action always saved the Parity setting as "None", regardless of the Parity setting chosen by the user. This issue has been resolved.
The Python debugger failed to stop at breakpoints that were inserted after the debugger was started. This issue has been resolved.
The Add Control button was missing from the Display Form Python Action. This issue has been resolved.
When importing data, the count of records being imported was wrong when duplicate records were detected. This issue has been resolved.
In the Administration module, on the Configurations tab, the options for "Copy" and "Compare with..." did not copy or compare all configuration items. This issue has been resolved.
The Dynamic Reports module sometimes used the wrong version of the ADO.Net driver for the MySQL database. This issue has been resolved.
Documentation of the Python variable cancelsubmit has been expanded, and the example script for this variable has been corrected.
The example script for the Python command disp.newdatepicker has been corrected.
Documentation and sample code for the template command LIST_OPT 14 has been corrected.