This topic describes resolutions or solutions in GainSeeker versions 8.6.0 and 8.6.1 and corrections to the Online User Guide.
|
Contents [Hide] |
MINITAB versions 17.3 and later will no longer open files with the .txm filename extension. However, MINITAB can still open the file if it is renamed with the filename extension .txt. If GainSeeker finds MINITAB version 17.3 or later, it now sends the data to MINITAB as a .txt file.
When running both new and legacy applications in a Citrix or Terminal Services environment, GainSeeker would sometimes use two concurrent licenses instead of just one. This issue is resolved.
When adding multiple new Events with the Add New button and hitting Cancel with the last Event, the Event list does not show the new entries until you exit and come back in. This issue is resolved.
On chart titles, some characters were erroneously removed and formatting was not always applied correctly. This issue is resolved.
When editing DMS standards, the Fill List button would only retrieve a list of standards if the Part Number begins with box was left blank. This issue has been resolved.
In the Settings for an SPC retrieval - e.g., on the Settings tab for a new chart - if the user applied different limits in the Standard Overrides group of settings, the only way to re-apply whatever limits were set in the standard was to click Restore Defaults and reset everything on the Settings tree. Right-clicking that limit and selecting Use default value now provides a much better method for accomplishing this task.
The DMS Dashboard control did not allow the user to delete data. This issue has been resolved.
In the Dashboard Grid, setting a column to display the "DMS Mean" sometimes did not function correctly. This issue has been resolved.
When drawing control charts and using an angle for the X-axis labels, some of the labels would run off the window. This issue has been resolved.
When importing a dashboard that included three or more filters, two of those filters could have different names within GainSeeker but point to the same supporting text file. The same could occur when the imported dashboard contained three or more statistic list formats or three or more statistical filters. This issue has been resolved.
When saving a desktop of DMS data where all the data contained less than 9 unique defects per record, and then opening the desktop where the data has more than 9 unique defects per record, no data was retrieved. This issue has been resolved.
When displaying a date and/or time column in a dashboard grid, the column did not always sort correctly. The column was sorted alphabetically instead of by date. This issue has been resolved.
In a multi-row statistical filter, the last operation was treated as an OR instead of using the actual operation listed (AND or OR). This issue has been resolved.
When retrieving data for a standard with no gate or specification limits set and using the standardized coding method for varying subgroup sizes, the retrieval would give an error. This issue is resolved.
On the Dashboard Grid when using the "Rows grouped by" setting, the columns did not always sort correctly. This issue has been resolved.
When using a Dashboard Grid with a Last Traceability column (e.g. Last Shift), no data was found. This issue is resolved.
When importing a Dashboard with an embedded Python script, if a script with that name already existed, the system would ask if you want to overwrite the existing script. However, the existing script was never overwritten and remained unchanged. This issue is resolved.
When the GainSeeker Inspections module was configured to display the TestID on test buttons, changing the TestID property of a test did not immediately update the TestID that was displayed on the button for that test. This issue has been resolved.
In a sub-inspection with very long list of tests, when the user clicked on a test to edit it, the list of tests would automatically scroll the list so that the test being edited was shown at the bottom of the window (if possible). This sometimes made it difficult to double-click a Formula test in order to edit the Python script for that test. This issue has been resolved.
When Inspections used scripts, some special characters contained in the script - such as foreign language accents, greater than symbol, less than symbol and the ampersand symbol - were not stored correctly. This issue has been resolved.
When assigning charts to be displayed with a sub-inspection, if all standards were selected, the inspection was stored with no standards selected. This issue is resolved.
In some cases, opening a Planned Inspection would remove the Process. If the Planned Inspection was stored without re-selecting the Process, the Process would be reset to a blank Process. This issue is resolved.
It was discovered that if you copy and paste a sub-inspection that is configured to chart one or more numeric input standards, you will need to re-select the standards for these charts in the new copy of the sub-inspection. This is because the numeric input tests in the new sub-inspection will have different TestIDs from those in the original sub-inspection. A reminder message will now be displayed when you copy and paste such a sub-inspection, and documentation has been added to the topic on SPC Chart options in inspections.
The Mobile Preview button displayed the icon for a broken image instead of showing an example of the sub-inspection as it would be displayed on a mobile device. This issue has been resolved.
When a TestID was named for a Numeric Input test, configuring SPC Charts for that sub-inspection still showed the default TestID number for this test instead of the name of the TestID. This issue has been resolved.
When creating or editing an inspection, Comments tests were not being saved. Also, any Traceability tests where the BarcodeAllowed property was set to True were not being saved. This issue has been resolved in service pack 8.6.1 of the GainSeeker Inspections module which has been distributed to all GainSeeker 8.6.0 users.
On workstations with Office 2016 installed, loading a Word document in the side panel would sometimes cause an error message to appear or the system to become unresponsive. Removing support for Microsoft PowerPoint files in inspections has resolved the issue.
When PC Collect ran a long series of sub-inspections that included many tests and charts, it would eventually generate an error message due to memory leaks. This issue has been resolved.
A sub-inspection that was configured to display charts would not show the charts until the sub-inspection was launched for the second time. This issue has been resolved.
If a sub-inspection that stored multiple DMS records was also configured to display a chart or data table for that DMS standard or process, and the date period for the chart was "8 hours ending now" or "24 hours ending now", the chart sometimes failed to immediately display all of the new records. This was especially true if the "Show time to" configuration setting was set to minutes or seconds, because the time stamps for multiple data records using the same standard are incremented by that amount of time and this sometimes incremented a few minutes or seconds into the future. This module has been updated to account for this possibility when charting data.
Sometimes this module would become unresponsive if the user left an inspection open for several minutes without interacting with that inspection. This issue has been resolved.
Real-time failures for Runs were always calculated based on Control limits, regardless of the Run values based on configuration setting. This issue has been resolved.
When the inspection used the inspect.cursubi.selectsidepanel Python command in an OnChange script and the data entry user would use the TAB key to move from one Numeric Input to another Numeric Input on a sub-inspection, the subsequent Numeric Input would lose the focus. This issue is resolved.
An Inspection that displayed DMS charts on a sub-inspection would sometimes generate an error if the AutoLoadSubInspection property was set for that sub-inspection and the Inspection was started from the Run button in Inspection Editor. This issue is resolved.
When opening a Planned Inspection, the Inspection Viewer window would initially open in a very wide window. The Inspection Viewer now opens in a normal-sized window.
When running a Planned Inspection, not all traceability would get filled correctly with the values set in the Planned Inspection. This would happen when the ClearValue property of the Traceability test was set to ClearAfterCurrentSubInspection. This issue has been resolved.
The form displayed by disp commands such as disp.show sometimes ignored the specified height width of the bottom-most or right-most component. This issue has been resolved.
In previous versions, the Python command datadms.eventdms returned the 1-digit event code instead of the full event description. This issue is resolved in version 8.6 and later but any existing scripts that use this command will need to be edited to reflect this correction.
The tcp[x].connect command would not connect to a TCP device unless that device was registered in the Domain Name System (DNS). This command now allows connections to any TCP device. This issue has been resolved.
In previous versions, the y axis title on the Python line chart (linechart.yaxistitle) would display at the edge of the window and was not always completely visible. This issue is resolved.
In previous versions you could not reference the value of a custom statistic when creating a new custom statistic. This issue is resolved.
In previous versions, the Python disp. command ignored the .width and .height properties of form controls. This issue is resolved.
The following file.xls Python commands did not interpret the Column correctly when using the "name" parameter instead of the "row" and "column" parameters: .getcell, .getcelldt, .getcolumn, .getcolumndt. The column was incorrectly identified as one greater than the desired column. This issue is resolved in version 8.6 and later but any existing scripts that use these commands with the "name" parameter will need to be edited to reflect this correction.
When importing or exporting data, the Open/Save dialog did not default to the Import/Export file path that was set for the configuration. This issue has been resolved.
With the Audit Trail configured to require the user to enter a reason for changes, using the Note Manager to edit data would apply the first reason entered to all consecutive changes until the user exited the GainSeeker Utility. This issue has been resolved.
When importing standards, the GainSeeker Utility did not allow a standard to be created if the Lower Range Gate was below the Lower Reasonable Limit or if the Upper Range Gate was above the Upper Reasonable Limit. This issue has been resolved.
The real-time failure checks for "2of3 outside 2 standard deviations" and "4of5 outside 1 standard deviation" did not report correctly if the good point was on the opposite side of the mean. This issue has been resolved.
When using the DEFECTCREATE template command and sending in a blank string, a blank defect would be created. Making the call several times would cause several blank defects to be created. This issue is resolved.
When importing a new version of a template and overwriting the previous template, an error was generated if the two templates did not contain the same number of template rows. This issue has been resolved.
In previous versions of SPC Designer, if the network dropped and you attempt to save a template, the template file was stored with a size of zero bytes. GainSeeker now will not close the Designer window if it cannot successfully create the file. In this case, it also writes the template file to the GainSeeker temp folder or the local Windows temp folder if the former folder is on the network.
Under certain conditions, a report format could be saved as an empty string. To resolve this issue, this module has been modified to prevent the report format from being saved if the updated format is an empty string.
If a Dynamic Report contained GainSeeker charts, those charts did not use the default chart titles set in the configuration. This issue has been resolved.
When setting up a shortcut to launch the GainSeeker Charts module, open a desktop or dashboard, and send it via e-mail, the components of this window did not display correctly. This issue has been resolved.
When setting up a shortcut to launch the GainSeeker Charts module and open a desktop or dashboard, selecting the Prompt at startup check box erroneously set the command line argument to Prompt=1 (incorrect, though it does work) instead of Prompt (correct). This issue has been resolved.
In previous versions, some of the windows had information that was cut off and did not fully display. This issue has been resolved.
The topic Flow Chart Analysis of Non-Normal Data has been updated for the current version of GainSeeker.
Topics that referenced the option to convert a Pervasive database from File mode to Database mode - including installation instructions - have been updated to reflect that the current version of GainSeeker requires the use of Database mode when using a Pervasive database.
The topic Python command: Miscellaneous has been updated to correct syntax errors and update sample code.