This topic describes resolutions or solutions in GainSeeker versions 9.3 - 9.3.2 and corrections to the Online User Guide.
When using a remote deployment tool to install the GainSeeker client in silent mode, the client was not successfully installed. This issue has been resolved. (Issue: GAIN-4158)
In the GainSeeker Charts module, GainSeeker Inspections module, and PC Collect module, initially logging in as a user without permission to use the Setup menu and then using the File menu to log in as a user with permission to use the Setup menu would fail to display the Setup menu. This issue has been resolved. (Issue: GAIN-4132)
In the GainSeeker Charts module, GainSeeker Inspections module, and Dynamic Reports 2 module, performing some functions could display an error message such as "Desktop applications are required to opt in to all earlier accessibility improvements to get the later improvements." For example, this could occur when clicking the TextAlign property for a Dynamic Text control on a Dashboard. GainSeeker now installs the files GSCharts.exe.config , IEdit.exe.config , and RWriter.exe.config to the folder where GainSeeker executable files are installed. This issue has been resolved. (Issue: GAIN-4175)
In the GainSeeker Charts module, if you changed the Varying subgroup size setting for a chart and then saved that chart in a desktop, opening that desktop would fail to apply that setting to the chart. This issue has been resolved. (Issue: GAIN-4076)
In the GainSeeker Charts module, editing an SPC data record from the Monitor Table or Multiple Data Table would sometimes display the Description from one of the other SPC standards retrieved for the table. This issue has been resolved. (Issue: GAIN-4108)
In the GainSeeker Charts module, if you used Edit/Open to apply a different date period or filter to a dashboard containing an SPC or DMS chart control, right-clicking one of these chart controls and choosing Chart would correctly generate a chart window with the new date period or filter. However, changing the date period or filter for this new chart window would display the original date period or filter stored in the dashboard, and changing any other settings for the chart window would re-retrieve data for the original date period or filter stored in the dashboard. This issue has been resolved. (Issue: GAIN-4063)
In the GainSeeker Charts module, right-clicking on a Dashboard Grid to view data and then delete a range of data would prompt the user twice to confirm that this data range should be deleted. This issue has been resolved. (Issue: GAIN-4172)
In the GainSeeker Charts module with Server Edition, using command line arguments to display a dashboard as a Slideshow and export HTML on a timer would sometimes export an image of an empty dashboard control. This could especially happen for dashboard controls that process a large amount of data, such as Big Data Analytics DMS, Big Data Analytics SPC, Paired Sample Grid, or Defect Trend Wizard, which might not have finished refreshing before the next timer was triggered. This issue has been resolved. (Issue: GAIN-4109)
In the GainSeeker Charts module, memory leak issues when constantly refreshing chart windows and/or dashboard windows would use increasing amounts of memory until the charts were closed or the module ran out of memory. This issue has been resolved. (Issue: GAIN-4020)
In the GainSeeker Inspections module, memory leak issues when repeatedly opening and closing the Script Design window and debugging scripts in an inspection would use increasing amounts of memory until the module was closed or ran out of memory. This issue has been resolved. (Issue: GAIN-4079)
In the GainSeeker Inspections module, when an inspection had the InspectionScript property set to a Python script, exporting that inspection would fail to include that inspection script in the resulting .cpz file. This issue has been resolved. (Issue: GAIN-4150)
In the PC Collect module, an SPC side panel chart linked to a Numeric Input test whose NoValue property is set to DoNotStore would fail to refresh when the sub-inspection was Submitted. This issue has been resolved. (Issue: GAIN-4142)
In the PC Collect module, opening a sub-inspection with many DMS tests such as Defect List or Pass/Fail could display the error "Error creating window handle", especially if that sub-inspection was opened repeatedly. This issue has been resolved. (Issue: GAIN-4167)
In the GainSeeker Utility module, when using the Standard Utility to duplicate SPC standards, using the Change all Part Number descriptions feature and including a single quote in the new description would display the message that new standards were successfully created but would actually fail to create the new SPC standards. This issue has been resolved. (Issue: GAIN-4140)
In the GainSeeker Utility module, when using the Standard Utility to duplicate SPC standards, using the Change all Part Number descriptions feature and entering a value that is longer than the description field can actually store would display the message that new standards were successfully created but would actually fail to create the new SPC standards. This issue has been resolved. (Issue: GAIN-4140)
In the System Administration module, copying a configuration always set the table name for the Python scripts table to HSISCRIPTS, even if the configuration being copied was set to use a different name for this table. This issue has been resolved. (Issue: GAIN-4146)
When using GainSeeker on an Oracle database, if the System Administration module specified table names with lowercase characters, the Table Creation Utility failed to recognize when these tables and indexes already existed and would erroneously try to create them again. The Tables and File Paths window also erroneously marked tables as "missing" even though they actually existed. This issue has been resolved. (Issue: GAIN-4145)
When using GainSeeker on an Oracle database, if the System Administration module specified table names with no lowercase characters for HSIRPT or HSISCRIPTS, the Table Creation Utility failed to create indexes for these tables. This issue has been resolved. (Issue: GAIN-4148)
When viewing a report in the Legacy Dynamic Reports module, clicking the File menu, pointing to Send to, and then clicking Image would create the image file in the Temp folder but failed to open that image file. This option (Image) has been removed from the Send to group on the File menu. To send the current report to an image file, you should use the Save file as button on the toolbar. This issue has been resolved. (Issue: GAIN-4121)
In the .Launch module, creating a new GainSeeker Item and setting the Connection to Select connection at runtime would generate an error message and would display an invalid ConnectString parameter. These issues have been resolved. (Issue: GAIN-4127)
In the PC Collect module, using the Language menu, command line,
or Language setting for the GainSeeker user to set the language to
Spanish would force this module to use a comma as the decimal symbol,
which prevented GainSeeker from storing any new or changed database
records that contained decimal values.
Similarly, GainSeeker was unable to store new or changed records when
displaying PC Collect in French - either using the methods described
previously, or running PC Collect on a workstation with the Windows
display language set to French (which by default sets the Windows
regional settings to use a comma as the decimal symbol).
GainSeeker now uses a period for the decimal symbol, regardless of
the Windows display language or Windows regional settings. These issues
have been resolved. (Issue: GAIN-4141)
With the system-wide setting for Computer identification set to MAC Address, one GainSeeker workstation with multiple network access methods (for example, both wired and wireless network access) could erroneously use two GainSeeker licenses if the user would sometimes run both a legacy module (such as SPC or DMS Charts and Reports, Enterprise Dashboard, or SPC or DMS Data Entry) and a current module (such as LaunchPad, GainSeeker Charts, or PC Collect). This issue has been resolved.
If any defect name contained a backslash or curly brace symbol, it was not written correctly when sent to an .rtf document. This issue has been resolved.
When sending the Master list of defects to an .rtf document, the sort order of defects in the resulting document did not always match the sort order of defects displayed in GainSeeker. This issue has been resolved.
With Database Connections set to Select connection at runtime, selecting a connection that used a Trusted Connection sometimes failed to apply that trusted connection. This issue has been resolved.
When working with default reports for SPC or DMS charts, creating a new report with the same name as an existing report and choosing to replace the existing report did not always work correctly. For some report types, the new report was never created. For others, the old report was never deleted and the list of default reports then contained two reports with the same name. These issues have been resolved.
When selecting a default report for any of the Statistics under... settings, selecting the blank row at the top of the list did not function as desired. In System Administration, this failed to change the default report. In GainSeeker Charts, this forced the user to select a default report (again) when printing or sending the chart. This blank row has been removed from the list of default reports for all of the Statistics under... settings. This issue has been resolved.
When drawing an OEE Detail chart for data without any defects, the chart would display the message "No Defects" instead of displaying OEE Detail information. This issue has been resolved.
When grouping by a traceability field (either first-level or second-level grouping) on an OEE chart, OEE Availability chart, OEE Performance chart, OEE Quality chart, OEE Combined chart, or OEE Detail chart, if that chart retrieved data where that traceability field was blank, the charts would not display the appropriate OEE value for the blank traceability value, and the OEE Detail chart would display a blank row for the blank traceability value. This issue has been resolved.
On an OEE chart with primary grouping set to Day, applying a second-level grouping by Hour generated the error "System.InvalidOperationException: dtLong cannot be less than zero". This issue has been resolved.
When a dashboard contained a Dashboard Grid control with the rows sorted by any column except Part Number, the sort would be reversed each time the data for that control was refreshed (either manually or with a timer). This issue has been resolved.
When drawing several new SPC charts at the same time, some chart windows such as Control Chart or Monitor Table would erroneously display a blank statistics list area below the chart when generated with another chart that always displays statistics below the chart (such as Process Capability chart, Combined Control Chart, Combination Chart, or Performance Chart). This issue has been resolved.
When a Monitor Table chart did not find any monitor data to display on the chart, the chart window was not labeled to indicate the reason why no rows were displayed. This chart now displays the message "No monitor data to display." This issue has been resolved.
When generating new charts for one SPC standard, a Monitor Table chart was erroneously labeled "No Chart Available" instead of "No data found". This issue has been resolved.
When a Monitor Table did not display any data rows, the right-click menu erroneously displayed commands such as Find, Edit, Delete, and Legend which are only appropriate when the table contains some data. Similarly, the Options menu would erroneously contain the Scaling command. These issues have been resolved.
Drawing charts for one or more standards that contained an asterisk (*) would generate an error. This issue has been resolved.
When applying a custom format to a statistic that contained a symbol such as % or $ (e.g., in a dashboard control or on a chart title), GainSeeker failed to apply the custom format. This issue has been resolved.
The right-click menu for an OEE Detail chart erroneously displayed a "Legend" command, even though there is no legend for this chart. This issue has been resolved.
For OEE charts, the Chart Overrides setting "Labels and Titles > Display limit and chart axis labels > Never display labels" failed to correctly remove the limit labels and axis labels. This issue has been resolved.
When data records were stored with date/time stamps that showed time to more places (seconds or hundredths of seconds) than the "Show time to" setting (minutes or seconds) for the current GainSeeker configuration, editing a range of data would generate an error. This issue has been resolved.
When creating a new DMS chart and selecting all DMS processes or all DMS standards, choosing a Pareto chart from the left-hand list erroneously created one chart analyzing all of the selected values, instead of the intended behavior of creating one chart for each process or standard. Additionally, changing the chart to group Pareto bars by a different value would simply display "No Chart Available" on the chart window. These issues have been resolved.
When creating a new DMS Statistics Table chart and selecting all DMS processes or all DMS standards, the resulting table contained only one row analyzing all of the selected values, instead of the intended behavior of creating one row of statistics for each process or standard. This issue has been resolved.
When saving or opening a desktop, the "Display limit and chart axis labels" setting did not always match the original chart windows saved in the desktop. This issue has been resolved.
Creating a stored filter for multiple standards, processes, and/or date/time values would sometimes generate the error "System.AccessViolationException: 'Attempted to read or write protected memory. This is often an indication that other memory is corrupt.'" This issue has been resolved.
When a DMS Statistics Table was displayed for more than 20 standards or processes, changing the statistics report format or saving this chart in a Desktop could cause the GainSeeker Charts module to crash or shut down unexpectedly. This issue has been resolved.
When a shortcut to launch the GainSeeker Charts module included the "Silent" parameter to suppress any error message, this module would also disable the "Show Toolbar" and "Show Start Buttons" settings on the Desktop menu. These settings were saved for the current computer and used the next time this module was opened, so to the end user it appeared that the toolbar and start buttons would sometimes disappear. Starting this module with the "Silent" parameter no longer saves changes to these settings. This issue has been resolved.
When the Operator Note markers were displayed with a higher priority than Failure Note markers, data records with failure notes were erroneously displaying the Operator Note marker instead of the Failure Note marker. This issue has been resolved.
Opening a dashboard with a Dashboard Grid control that was configured with a Cell display format or Colors defined by setting could generate the error "The given key was not present in the dictionary". This issue has been resolved.
When saving a dashboard to file, the file type options listed and the default file type selected would changed based on how many graphical controls (dial gage, bar gage, chart, or image) the dashboard contained. This issue has been resolved.
On an Oracle database, using the File menu to view Report Properties would generate the error "Input string was not in a correct format." This issue has been resolved.
If GainSeeker was configured to automatically display the list of Inspections, Planned Inspections, or Python scripts each time the GainSeeker Inspections module was started, this module would erroneously display "CurUser" at the bottom of the window instead of displaying the name of the currently logged-in GainSeeker user. This issue has been resolved.
In some cases, editing and debugging inspections with Python
scripts could generate "Out of Memory" errors. This module
has been improved to address this issue.
If "Out of Memory" errors continue, you can try to keep the
Python script editor open and switch between scripts, minimizing the
number of times you need to load and unload the script editor. You
can also close and re-open the GainSeeker Inspections module more
often to free up memory.
In some cases, when running an inspection with an OnChange Python script in debug mode, it became impossible for the user to close the inspection window. This issue has been resolved.
When displaying the list of defects for a Pass/Fail test, the sort order in which those defects were listed could be different from other defect lists in GainSeeker. This issue has been resolved.
If the last test on a sub-inspection was a Text test, that test could erroneously get the focus if the inspector tabbed to it or if the previous test was a Numeric Input and the inspector entered the last data value and pressed Enter. This issue has been resolved.
If the sub-inspection contained a Date/Time test, changing any portion of that Date/Time (day, month, etc.) just before submitting the sub-inspection would sometimes fail to apply that last change when storing the data for that sub-inspection. This issue has been resolved.
Sending real-time failure emails via Microsoft Outlook did not correctly attach the data table to the email. This issue has been resolved.
For each chart included in a real-time failure email, sending the email via SMTP would attach a file to the email, but sending real-time failure emails via Microsoft Outlook would attach a file and embed its contents in the body of the email. Outlook emails for real-time failures have now been modified to match SMTP emails. This issue has been resolved.
Running a sub-inspection with a Numeric Input test could sometimes generate the error "An error occurred while performing real-time checks - Specified cast is not valid." This issue has been resolved.
When an Inspection contained multiple sub-inspections, it was possible to select one sub-inspection and then select another while the first sub-inspection was still loading. This caused the last sub-inspection you clicked on to load instead of the desired one. This issue has been resolved.
When using the File menu to Start File Import, the PC Collect module would crash if the user did not have access to the file path. GainSeeker now displays an appropriate message instead of crashing if the user cannot access the file. This issue has been resolved.
If two sub-inspections both displayed a multiple-retrieval chart on the side panel, and the list of standards for one sub-inspection chart was a subset of the list of standards for the other sub-inspection chart, the two charts would sometimes be erroneously combined on a single chart. This issue has been resolved.
Using the Python cmdargs.getargstring() command to print the command line argument string would erroneously print it twice. This issue has been resolved.
An invalid date in the GP_VALUE column could generate an error message such as "Index was outside the bounds of the array". This issue has been resolved.
Importing a Python script would set the Last Edit Date to 1/1/0001 12:00:00AM and leave the Last Editor empty. GainSeeker now displays the computer date and time when the script was imported as the Last Edit Date, and it shows the name of the GainSeeker user who imported the script as the Last Editor. This issue has been resolved.
In the PC Collect module, when calling inspect.sidepanel.selectitem() to select a side panel tab that was still being drawn, GainSeeker could generate a "Sequence contains no elements" error. This issue has been resolved.
In the PC Collect module, using inspect.cursubi.ni().celllabels to change the data cell labels for a Numeric Input test did not work correctly if the only change to the list of cell labels was the order in which they would be displayed. This issue has been resolved.
The commands file.exceltopdf(), file.htmltopdf(), file.xls.read(), and textevaluator.loadset() failed to find the specified file name if it was provided with an uppercase filename extension. This issue has been resolved.
Setting the inspect.cursubi.defectlist(idx).defects property to a list with more defects than the current list would generate an "Index was out of range" error. This issue has been resolved.
When using file.xls.getrow() or file.xls.getcell(isNumeric=False) to read a .csv file, any cell that contained a number with a symbol (local currency symbol, percent sign, fraction, or scientific notation) would erroneously be returned as a date/time. This issue has been resolved.
The command dataspc.rtf.filter did not filter data when Quick Filter contents were specified. This issue has been resolved.
GainSeeker would generate an error if a script tried to use retrdms.external.settrace() or retrspc.external.settrace() to set a traceability value for a traceability index higher than the maximum traceability field defined for the current configuration. Now attempts to set traceability values for indexes higher than the maximum defined for the current configuration will be ignored. This issue has been resolved.
Changing the Print title / Company name, Chart title 2, Chart title 3, or Control data grid header items could sometimes generate an error. This issue has been resolved.
When selecting a default DMS report format for "Statistics under Data Table", GainSeeker would display a list of SPC report formats. This issue has been resolved.
Saving Import/Export/Delete settings with a Quick Filter did not correctly save the contents of the Quick Filter. This issue has been resolved.
When standards or processes were selected for Import/Export/Delete, loading Settings failed to de-select those standards or processes before selecting only the items from the Settings file. This issue has been resolved.
When importing a file of data with multiple standards, Show Status would erroneously show the status of data to import for all of the standards in the file instead of only the standards you selected. This issue has been resolved.
When exporting or importing data, the green progress bar sometimes failed to indicate that 100% of the data had been processed. This issue has been resolved.
When importing data records that were stored with date/time stamps that showed time to more places (seconds or hundredths of seconds) than the "Show time to" setting (minutes or seconds) for the current GainSeeker configuration, responding to a prompt about duplicate records with the option to "replace for all" would generate an error. This issue has been resolved.
Using the SQL Utility "SQL Assistant" to delete a DMS defect would generate the error "System.NullReferenceException: Object reference not set to an instance of an object." This issue has been resolved.
With the cursor in the 'Maximum number of rows to retrieve' chart setting field or the 'Timer length' global setting field, pressing an 'Accept' or 'Go' button on a mobile device (or pressing Enter on a desktop browser) would erroneously redirect the browser window to a different web page. These actions have been corrected to simply submit the current form. This issue has been resolved.
For control charts, the x-axis was erroneously labeled 0 through (n-1) instead of 1 through n. This issue has been resolved.
Documentation for the file.xls.getcelldt() Python command erroneously indicated that file.xls.setcell() can be used to set a datetime cell. Documentation for both commands has been updated to reflect that file.xls.setcell() cannot be used to set a datetime cell. This issue has been resolved.
Documentation for the disp.addbtn Python command did not specify that a maximum of three buttons can be displayed on the form. This issue has been resolved.
Documentation for template commands Q_EXECUTE and Q_START, and for the SQL Utility (and Legacy SQL Utility), only referenced the execution of stored procedures that do not return a result set, but GainSeeker is actually able to capture the result set of a stored procedure if the query executing that stored procedure has been written correctly for the database. This issue has been resolved.
Documentation for the WindowState= shortcut parameter erroneously stated that any number other than 1 or 2 would open the program's main window in sized (normal) mode. This issue has been resolved.