This topic describes resolutions or solutions in GainSeeker versions 8.5.0 and 8.5.1 and corrections to the Online User Guide.
On newer operating systems such as Windows 8.x or Windows 10, selecting an item (such as a standard) from a list sometimes generated an error message. This problem was caused by an operating system incompatibility with the supporting file ComCtl32.ocx, which has been updated in version 8.5. This issue has been resolved.
Traceability values should always be stored with all uppercase letters. This was not happening in some places where traceability values could be set. This issue has been resolved.
If you upgraded from a previous version of GainSeeker that was configured for segmented standard names, duplicating an SPC standard or a DMS standard would crash. This could happen in some modules such as System Administration, GainSeeker Charts, GainSeeker Inspections, PC Collect, and GainSeeker Utility. This issue has been resolved.
In GainSeeker Charts and the GainSeeker Utility module Note Manager, editing a bypassed DMS data record with Event = * did not always work correctly. This issue has been resolved.
When a module was loaded from the LaunchPad module and the Change Configuration function was used in the new module, it would not change the configuration. This issue is resolved.
When importing a Python library into a custom statistic script using the Import command, the script would throw an error when the custom statistic was accessed in the GainSeeker Charts module. This issue is resolved.
When selecting Inspection Editor from the Power Tools menu of SPC Designer, Planner, or SPC Data Entry, the Inspection Editor would ask for the password. This issue is resolved.
Several modules displayed the number -1.6E+98 instead of * for missing values or incomplete subgroups. This issue is resolved.
On a Dashboard Button control, editing the BackColorRegions property sometimes changed the Value for region comparisons property to the wrong value. Clicking OK would then save the new (wrong) value for this property. This issue has been resolved.
When using the TimerFileNameExport property of a dashboard to save a picture of the dashboard to a file, the dashboard picture did not save correctly if the dashboard window was minimized. This issue has been resolved.
GainSeeker now uses better methods to determine how many decimals to display on the x-axis and y-axis for Pareto charts. This reduces the number of extraneous decimal points that are displayed on these axes.
Numeric columns in a dashboard Grid are now right-justified automatically.
When the user tried to edit a data record and change or remove values from traceability fields 7 or higher, those changes were not stored. The Edit Data window appeared to accept the change, but examining the data record revealed that the traceability fields still contained their original values. This issue has been resolved.
When a desktop contained a dashboard, and that dashboard was deleted, editing the desktop would produce an error message and viewing the desktop would not display any messages to explain why the dashboard window was not opened. This issue has been resolved.
When toggling from Quick Filter to saved filters (e.g., while creating a dashboard), no saved filter was selected - not even the "All Data" filter. This could generate an error message when trying to save the dashboard or edit the filter setting again. This issue has been resolved.
Importing a dashboard that had been exported as a .dbx file would crash. This issue has been resolved.
Step 1 of the Variation Wizard now remembers the last settings you chose for Traceability used in analysis – which traceability fields you checked (or cleared) and which are set to Discrete or Continuous.
When a standard had the range chart type set to Sigma, and the range of all the data values was 0 (no variation), the control limits and R-Bar were not calculated correctly. This issue is resolved.
The Multiple Data Table would sometimes show the x-bar column in the wrong location if the subgroup size was greater than one. When this happened, the x-bar column would be displayed in the middle of the data columns. This issue is resolved.
When two or more dashboard grids were on the same dashboard with the same retrieval settings but the data was being grouped differently, the data grouping for one of the grids was incorrect. This issue is resolved.
When drawing a dashboard grid and setting the Rows Defined by value to a traceability field that is not one of the first six traceability fields, the dashboard grid was empty. This issue is resolved.
When using the Dynamic Text control on a dashboard and selecting to display the current Part Number and Process, the control actually displayed "[Part Number/Process]" instead of the current values. This issue is resolved.
When choosing a background image for a dashboard and choosing to Center the image, an error was displayed. This issue is resolved.
The axis labels on DPU and DPU Cost charts have been updated to be more accurate.
When a custom statistic was displayed in a Chart Title field of a GainSeeker chart using the FORMAT option, an incorrect value was returned. This issue is resolved.
When set up to use a fiscal calendar, retrievals using the Previous Month option did not always retrieve the correct dates. This issue is resolved.
When using External Data to import DMS Data into the GainSeeker Charts module, and then choosing to save that data, the data was stored under the first Part Number in the Standards list instead of the Part Number that was imported. This issue is resolved.
The Start Python window is more readable and unused buttons have been removed.
Using the ConnectString command line argument or selecting the database connection at run-time did not work correctly. Either an error occurred or the wrong database connection was used. This issue has been resolved.
If an inspection contained multiple Numeric Input tests, and one of those tests generated a real-time failure note, then notes were automatically added to the other Numeric Input tests - even if they did not have real-time failures. This issue has been resolved.
When you create controls with the Python disp command and render them using the Python disp.show() command in an inspection, the controls were disabled. This issue is resolved.
When PC Collect was launched in DEBUG mode and an inspection name was also specified on the command line, an extra debug window was displayed. This issue is resolved.
Importing an inspection that had been exported as a .cpx file would crash. This issue has been resolved.
When using the retrspc.filter or retrdms.filter commands with a named filter, the data would not be retrieved correctly. Using a quick filter worked correctly. This issue is resolved.
When creating a new Python script and giving it a name, if the name was more than 40 characters the script would not be stored. This issue has been resolved.
Previously when setting the Standard for a Numeric Input test on an Inspection via a script with the PRE load, the data entry constant for that standard was not used. This issue has been resolved.
If the user clicked Cancel when creating a new Python script, GainSeeker would edit the script that was highlighted in the list. This issue has been resolved.
When writing custom code, the code completion tool displayed several commands that were not intended for use by Python script writers. This issue has been resolved.
The Python commands inspect.GetDMSStandard and inspect.cursubi.defectlist(idx).defectsmodified are no longer available.
When resizing the Python design editor, sometimes the text of the controls would not display correctly. This issue is resolved.
When accessing the list of Python Designs, GainSeeker displayed a separate error message for each Python Design it couldn't open because the Design had been created by a newer version of GainSeeker. Now when GainSeeker can't open a "newer" version of a Python Design, it displays one message that includes all of the Python Designs that could not be opened.
When a Python formula executed the inspect.setnextinspection('name") command in GainSeeker 8.5.0, data on that sub-inspection was not stored. This issue has been resolved in service pack 8.5.1 of the PC Collect module which has been distributed to all GainSeeker 8.5.0 users.
The Standard Utility failed to work properly when the SPC Part Number or the DMS Process contained a single quote character ('). Functions that failed include duplicating a standard, importing a standard, and deleting data – for either SPC or DMS. This issue has been resolved.
Previously, the Priority List Editor did not work correctly when setting the priority list of a GainSeeker User or Group when the name of the User or Group contained more than 20 characters. This issue has been resolved.
When importing DMS data the total imported records count sometimes was incorrect. Records would not be counted if they included a defect that did not exist, even though the record was imported. This issue is resolved.
When executing a SELECT query in the SQL Utility function, the query would sometimes return “The statement executed successfully” instead of returning the results of the query. This would happen if there was no space after the keyword SELECT and before the next word or line of text. This issue is resolved.
Role settings are no longer used with the following template commands: EXIT, SHUTDOWN, CHAIN_P, CHAIN_T, CHAIN_S, LOGOUT, TIMER_RUN. These commands can be executed regardless of the rights setting in the role.
When selecting standards on Planner Wizard Step 2, the window that displays the list of standards now remembers its last position. This is useful when you want to view the row Label (from the template) while selecting the standard for that row.
Topics for the template commands IF, Bitand symbol (&), Bitor symbol (|), Less Than symbol (<), and Greater Than symbol (>), have been updated with example methods for ensuring that BitOR and BitAND work as expected with the results of < and > comparisons.
Documentation for the Python commands inspect.cursubi.defectlist(idx).defects and inspect.update() has been updated.
Documentation for how to enter OEE data has been updated.