This topic describes resolutions or solutions in GainSeeker version 8.5.2 and corrections to the Online User Guide.
In a Terminal Server environment when the Computer Identification setting was set to "Workstation PhysID setting plus session id", the session id was not being used. This could cause an extra GainSeeker license to be used in some cases. This issue has been resolved.
When the Table Creation Utility (TCUtil) created a new SPC Note table such as "VNOTE_DEPT2", the last column for notes was created to be 228 long instead of 238 characters long. This could cause the Note Manager utility to crash with some databases. These issues have been resolved as follows:
The Note Manager has been updated to function correctly when the last column for notes is either 228 characters or 238 characters.
The Table Creation Utility has been updated to create all note columns at 238 characters long.
If you edited an existing SPC data record without a note, entering a new note and saving it would update the data record to reflect that a note existed, but the actual note text was not stored. This could occur when editing from the GainSeeker Charts module or the PC Collect module. This issue has been resolved.
If you used the PC Collect or GainSeeker Charts module to edit an existing SPC data record with subgroup size greater than 1, saving any changes to that record would erroneously change the subgroup size for that data record to 1. All values originally stored for the subgroup are still stored in GainSeeker, and analysis in the PC Collect, GainSeeker Charts, and Dynamic Reports modules is not affected because of the ability to analyze varying subgroup sizes based on the number of data values stored. The PC Collect and GainSeeker Charts modules have been updated so that editing a data record does not change its subgroup size. This issue has been resolved.
If you used the PC Collect or GainSeeker Charts module to edit an existing SPC data record with subgroup size greater than eight, and if traceability fields seven and higher were displayed but empty, editing one of the first six traceability fields and saving the change could delete the VDAT_AUX portion of the data record (data fields nine and higher and traceability fields 7 and higher). The PC Collect and GainSeeker Charts modules have been updated so that editing a data record does not delete the VDAT_AUX portion of that record. This issue has been resolved.
Using the File menu to save a dashboard as a .jpg file did not work correctly if the dashboard was minimized. Saving a dashboard as a .jpg file while the GainSeeker Charts module was minimized (e.g., when parameters were added to the shortcut that launched the module) also did not work correctly. These issues have been resolved.
Some charts incorrectly placed all of the x-axis tick marks and x-axis labels on the left side of the chart, instead of spacing them evenly across the bottom of the entire chart. This issue has been resolved.
Right-clicking on most dashboard controls and choosing options such as "View data" or "Chart" always displayed a message that no data was found - even when that control had retrieved data to display charts, statistics, etc. This issue has been resolved.
When assigned to a Role that password-protected the ability to add and edit Python scripts, a User could create a new Python Design if the list of Python Designs for Dashboards was empty. This issue has been resolved.
When assigned to a Role that password-protected the ability to add and edit Python scripts, a User who tried to open and view a dashboard was prompted to enter the password - even though they were not attempting to edit the Python Design. This issue has been resolved.
Some GainSeeker statistics and labels did not display correctly on chart titles and dashboard controls. This could especially happen for statistics such as "Mean" (for DMS) which is automatically changed to u-bar, p-bar, etc. This issue has been resolved.
When editing the GainSeeker statistics and labels for chart titles and dashboard controls, sometimes the statistics were not highlighted correctly and this made it difficult to select the statistic you wanted to edit. This issue has been resolved.
When using command line parameters to create charts and send them via email, the email window was displayed but the user still needed to click a button. The GainSeeker Charts module will now automatically send the email under these conditions. This issue has been resolved.
When using command line parameters to automatically print charts, dashboards, or desktops, the print window was displayed but the user still needed to click a button. The GainSeeker Charts module will now automatically print under these conditions. This issue has been resolved.
When using command line parameters to create multiple charts and print them, GainSeeker only printed the last chart created. The GainSeeker Charts module will now correctly print all of the charts that were created from command line parameters. This issue has been resolved.
When displaying a chart, sometimes the labels on the X-axis would overwrite the title of the X-axis. The GainSeeker Charts module now correctly calculates the amount of space needed for these two items so that they will not overlap. This issue has been resolved.
When a desktop contained a control chart that displayed dates and/or times on the X-axis, opening that desktop did not correctly read the Display date format setting - even though this setting had been correctly saved in the desktop. The result was that when the desktop was opened, this chart always displayed the X-axis date/time stamps using the default format. This issue has been resolved.
On a Pareto chart, choosing Sort By from the right-click menu or the Options menu displayed the main settings window instead of displaying the Sort By options. This issue has been resolved.
When designing a dashboard, using a custom DMS statistic that referenced the data's date/time stamp would display an error. This issue has been resolved.
When drawing a Performance Chart with no data, an error was displayed. This issue has been resolved.
When the Event column was displayed on a DMS Data Table, and that Data Table was saved in a desktop, opening that desktop did not display that Event column. This issue has been resolved.
When generating a DMS chart for multiple consecutive date ranges (such as 4 reports at 1 week per report), setting the "Method to handle DPU across processes" setting to "Additive" could generate an "Index out of bounds" error. This issue has been resolved.
When an SPC standard contained a Data Entry constant, and that standard was set for a Numeric Input test by the Inspection or by a Planned Inspection, opening the sub-inspection that contained this Numeric Input test would sometimes highlight the entire Data Entry constant instead of placing the cursor at the end of the constant. This made it easy for the data entry user to replace the Data Entry constant with the numbers they were typing, instead of appending those numbers to the end of the Data Entry constant. PC Collect has been updated so that the cursor is automatically placed at the end of the Data Entry constant (if it exists for the selected standard). This issue has been resolved.
When an SPC standard with a subgroup size of 2 or more contained a Data Entry constant, and a Numeric Input test was used to enter data for that standard, typing additional numbers after that Data Entry constant and then pressing the ENTER key would sometimes trigger the Submit button instead of moving the cursor to the next cell in the subgroup. This could happen because all of the cells for the subgroup were automatically prefilled with the Data Entry constant, and the PC Collect module took this to mean that all of these cells contained data. PC Collect has been updated so that pressing the ENTER key will move the cursor to the next cell in the subgroup, and it will only trigger the Submit button if the cursor is in the last cell of the last test in the sub-inspection. This issue has been resolved.
With Enable right-click menu on charts disabled, the user could still double-click a Data Table row to edit the data for that row. This function is now disabled if Enable right-click menu on charts is disabled. This issue has been resolved.
When a sub-inspection contained a Numeric Input test, any SPC Cause or SPC Action Taken selected by the data entry user was not being stored with the rest of the SPC data record. This issue has been resolved.
When the name of the Inspection contained a single quote ('), the Unique ID and associated information was not saved. A user could still enter data, but the list of Unique IDs was always blank. This issue has been resolved.
A user who double-clicked directly on a Formula test was able to create and edit Python Designs - even when assigned to a Role that restricted the ability to add and edit Python scripts. This issue has been resolved.
The commands datadms.getdefectcnt(index), datadms.ncu , datadms.samplesize , and datadms.sumdefects all refer to counts but returned floating point numbers with a decimal point. These commands now return integer values. This issue has been resolved.
The command traceability.getlabel(idx) would incorrectly return a "Not Set" label in some cases. This happened when the following traceability field (idx + 1) was configured to be hidden. This issue has been resolved.
Copying a configuration would copy all non-default Table names except for Control Table (default name: HSICT) and Inspection Unique Identifier (default name: INSPECTIONUID). This function has been corrected to copy all non-default Table names. This issue has been resolved.
The Import/Export Data utility allowed the user to import and export data, regardless of the permissions assigned to that user's Role. This issue has been resolved.
The Open Desktop window now displays
the Last Used date for each
desktop. You can sort the list of desktops by this column to determine
which desktops are no longer being used.
This feature was released with GainSeeker 8.5.0 but was omitted from
the Online User Guide.