This topic describes resolutions or solutions in GainSeeker versions 8.8 and 8.8.1 and corrections to the Online User Guide.
|
Contents [Hide] |
On an External Data chart window with some Settings - Retrieval/configuration or Standard overrides - set to non-default values, changing those settings back to their default values does not actually update the chart. This issue will be resolved in the next release of GainSeeker.
When a traceability field was hidden, some GainSeeker features would display that field but hide an adjacent field. This issue has been resolved.
When displaying the Monitor Table chart, setting "Maximum count for retrieval" to 0 always returned no data instead of removing the maximum count from the retrieval. This issue has been resolved.
When a DPU chart with second level grouping was displayed, changing the grouping would erroneously display some of the date and time statistics as "NA". These statistics are often displayed on chart subtitles and statistics reports. This issue has been resolved.
When a traceability field was hidden, any traceability fields that followed it were not applied correctly when sorting Pareto bars by traceability or when grouping data records by traceability on a Paired Sample chart or Multiple Data Table. This issue has been resolved.
When a drilling into a bar on a Pareto chart and sorting the drill-down Pareto chart by Part Number or Process, if the user drilled into one of those Part Number or Process bars by any other category and then refreshed the resulting chart, that chart would display "No Chart Available" to indicate that no data was found. This issue has been resolved.
When an External Data chart was displayed, changing a chart setting and then refreshing the chart would display "No Chart Available" to indicate that no data was found. This issue has been resolved.
On a Paired Sample chart that was set to display limits such as Control limits or Specification limits, if either of the SPC standards being charted did not have that limit set, the chart was scaled incorrectly. This issue has been resolved.
When generating a Paired Sample chart, if either of the SPC standards being charted had only one data subgroup that met the retrieval criteria, GainSeeker would display an error message. This issue has been resolved.
When generating a Paired Sample chart, if a data record being charted has no numeric values (all missing data), GainSeeker would display an error message. This issue has been resolved.
When a Paired Sample chart was displayed, changing any Settings or refreshing the chart would incorrectly change the chart title and retrieval settings such as Date period, Filter, and Maximum count for retrieval. This issue has been resolved.
When a dashboard was displayed, right-clicking the dashboard and sending to HTML did not automatically open the resulting HTML file in a web browser. This issue has been resolved.
When a dashboard was displayed, right-clicking the dashboard and sending to Clipboard or Email - or right-clicking on an individual dashboard control and sending that control to HTML - would immediately send the dashboard or control instead of waiting until the data retrieval was finished. This issue has been resolved.
When a dashboard contained a Big Data DMS or Big Data SPC control, right-clicking the dashboard and sending to any output before the data retrieval was finished would fail to send the dashboard. This issue has been resolved.
When a dashboard contained a Dynamic Text control, opening that dashboard would display placeholder values until the data retrieval was finished and the actual statistics were calculated. This issue has been resolved.
When editing a dashboard with SnapToGrid enabled, a control whose width or height was less than half of the SnapToGridSize property would automatically size that dimension to zero. This issue has been resolved.
When editing a dashboard with SnapToGrid enabled, GainSeeker ignored the AutoSize property for a Button control. This issue has been resolved.
When a dashboard contained a Marquee control, sending that control or the entire dashboard to some outputs such as e-mail, HTML, .rtf file, Word, or WordPad would not correctly display the Marquee text. This issue has been resolved.
When a dashboard contained a Marquee control, refreshing the dashboard would generate an error message. This issue has been resolved.
When editing a saved dashboard that included a Dashboard Grid control with a column for DMS data, the Cell Display property for some DMS statistics would display "Unknown". This issue has been resolved.
When a dashboard included a Dashboard Grid control with a column for DMS data and Rows Defined By set to a traceability field, that Dashboard Grid control would not return any data. This issue has been resolved.
When a dashboard included a Big Data SPC control with the ContinuousValues property set to a traceability field, viewing and working with that dashboard control demonstrated several issues. Selecting a row on the control and then clicking the Scatter Plot button would display an empty chart or generate an error message. Also, right-clicking a row on the control and then clicking "View continuous data" or "Chart continuous data" would display data for the wrong SPC standard. These issues have been resolved.
When a dashboard included a Big Data DMS control, selecting a row on the control and then clicking the DMS Drill-Down button would always group the resulting Pareto chart bars by Defect instead of grouping by the "Data sorted by" value for that row on the control. This issue has been resolved.
When editing a Python Script Designer dashboard control, any value entered in the Z-Order property was not saved. This issue has been resolved.
When editing a Python Script Designer dashboard control, modifying a Python script and clicking the Save button in the Python Script Editor sometimes failed to store the changes to the Python script.
When using the Edit Script button on the control, this could happen if you clicked the Save button for the script, clicked Cancel (instead of Select), and then saved changes to the dashboard.
When using the Properties grid to edit the PythonScript property for the control, this could happen if you clicked the Save button for the script, clicked either Cancel or Select, and then edited the same property a second time.
When using the Properties grid, this could also happen if you clicked the Save button for the script, clicked either Cancel or Select, and then saved changes to the dashboard.
This issue has been resolved.
When sending a Python Script Designer dashboard control to Word, WordPad, or .rtf file, GainSeeker captured an image of the control at the correct size but not at the correct location on the dashboard. This issue has been resolved.
For a dashboard that included a Python Script Designer dashboard control, when sending that dashboard to any destination such as Clipboard, HTML, Email, Word, etc., GainSeeker was supposed to wait up to 10 seconds for the script to finish running before sending the dashboard. However, GainSeeker was not observing this 10-second timeout for this type of control and could send the dashboard before this control had finished drawing. This issue has been resolved.
When sending a Python Script Designer dashboard control to .xml file, GainSeeker would sometimes generate an error message. This issue has been resolved.
When using the Slideshow to create an HTML file for a dashboard, several dashboard controls were not displayed correctly on the HTML. These include Dial gage, Bar gage, Python dashboard control, Big Data SPC, Big Data DMS, Statistic List, and Chart. This issue has been resolved.
When a dashboard (or individual dashboard control) was configured with a Timer property and TimerFileNameExport property, opening it or refreshing it with the Timer did not properly export the dashboard image. This issue has been resolved.
When using different copies of the HSISCRIPT table for different configurations, using the File menu to log in as a different user or change configuration did not change the list of Python scripts displayed when setting up or debugging a Formula test and when creating and debugging standalone Python scripts. This issue has been resolved.
When debugging a Python script after using the File menu to log in as a different user or change configuration, the sql.tables.tablename Python command returned the table name for the original configuration instead of the table name for the new configuration. This issue has been resolved.
When configuring a Planned Inspection, a traceability field that was hidden would still be displayed. This issue has been resolved.
Commands that accessed the database tables for Event, Cause, or Action Taken would generate an error message if those tables contained invalid values. This issue has been resolved.
When a traceability field was hidden, GainSeeker would hang when trying to export SPC or DMS data records. This issue has been resolved.
When importing DMS data from a tab-delimited file that did not contain the necessary columns for GainSeeker data, GainSeeker would generate an error message. This issue has been resolved.
When using the Note Manager utility to edit notes, clicking the Edit Data button would generate an error message if no corresponding data record existed for the current note (indicating that the Data and Note tables needed to be synchronized). This issue has been resolved.
When editing Tables and File Paths, changing the file path for a single Table or File Type would initially display that change for only the item you selected - even if other Table or File Type entries also used that file path. It was necessary to click Submit and then edit Tables and File Paths again to display the change applied to all affected Table or File Type entries. This issue has been resolved.
When editing a configuration with more than 31 traceability fields defined, displaying the Traceability Group by setting for Paired Sample charts would generate an error message. This issue has been resolved.
Documentation of the Dashboard control property Z-Order has been updated for clarity.
When using expanded data fields, GainSeeker will display an error message if there is a mismatch between the GainSeeker column length settings and the actual column lengths found in the current data tables, with instructions for repairing the problem displayed at the end of the message. However, this message can be very long if many columns exhibit this mismatch, and on low-resolution displays the instructions for repairing the problem could not be seen. The instructions for repairing the problem have now been moved to the top portion of this error message, so that they can be viewed on all displays, regardless of screen resolution. This issue has been resolved.
On some Citrix or Terminal Services implementations, newer GainSeeker modules such as LaunchPad, GainSeeker Inspections, and GainSeeker Charts were reading values such as "pre-selected GainSeeker user" (user_name=), "last GainSeeker user" (user_last=) or "computer identifier" (physid=) from the server's shared Cms.ini file instead of the user-specific Cms.ini files in the users' Home directories. GainSeeker now sets and reads these three settings in a new user-specific Usershared.settings file. This issue has been resolved.
On an Oracle database, GainSeeker was querying USER_TABLES instead of ALL_TABLES when checking for the existence of database tables. This prevented GainSeeker from finding tables that were created in Oracle user schemas that are different from the Oracle user being used to log in to GainSeeker. GainSeeker now queries ALL_TABLES to verify the existence of database tables. This issue has been resolved.
In the GainSeeker Inspections module and the PC Collect module, clicking the Setup menu and choosing Traceability Labels and Lists would erroneously display the traceability setup window that is used by the System Administration module to edit the traceability labels. These two modules have been corrected to display the traceability setup window that is used by the GainSeeker Charts module, which allows you to edit the lists of pre-defined traceability values but not the traceability labels themselves. This issue has been resolved.
The PC Collect and GainSeeker Inspections modules did not always display correctly on monitors with ultra-high resolution. The font size on some window titles and button captions was not correctly reduced to fit the available space, and it was not always possible to correctly resize program windows to fit the screen. This issue has been resolved.
When exporting some types of information from GainSeeker, having a special character ( \ / : * ? " < > | ) in the name would sometimes produce unexpected results. This could happen when exporting an Inspection with one of these characters in the name of the Inspection or in the name of a Device Profile or Python script used by the Inspection. It could also happen when exporting a Dashboard with one of these characters in the name of the Dashboard or in the name of a retrieval, filter, statistical filter, statistics list, or Python script used by the Dashboard. At this time, a Dashboard that uses an SPC or DMS filter whose name includes the | character cannot export that filter with the other Dashboard components - but for all other combinations of these characters and types of information, this issue has been resolved.
When GainSeeker is set to use Active Directory for User/Group login verification and a Role was set to check the login password to access a restricted portion of the application, it asked for the GainSeeker password instead of the Active Directory user password. This issue has been resolved.
Changing the GainSeeker password did not require the user to re-enter the new password to continue. This issue has been resolved.
When using SPC Priority Lists, the standard description was not being displayed. This issue has been resolved.
DMS Priority Lists for standards did not work properly with expanded databases and would display an empty list. This issue has been resolved.
After applying a September 29, 2017 update to Microsoft Excel, sending to Excel from within GainSeeker modules could generate the message "System was unable to find the file specified". This issue has been resolved.
Traceability fields that were not set to be displayed still showed up in some traceability lists. This issue has been resolved.
When editing a filter that uses the Date/Time column, the dropdown button caused an error if the current value for Date/Time was not a valid date and time. This issue has been resolved.
When editing a Python Script Designer dashboard control, you could click the Edit Script button to select a different Python script for the control, but the PythonScript property on the property grid was not automatically updated. This issue has been resolved.
When using a Quick filter with a "Doesn't contain" test and a traceability field that is not one of the first six in the list, re-opening the filter would display its contents incorrectly. Although the filter functioned properly, it displayed text about the field not being NULL. This issue has been resolved.
Refreshing a Dashboard on a timer or repeatedly opening and closing a dashboard with a Python script would eventually crash the GainSeeker Charts module due to a memory leak. This issue has been resolved.
When an SPC Event, Cause, or Action Taken did not contain a Long Description, no marker was displayed on a Control Chart. When the subgroup was edited, that Event, Cause, or Action Taken would be removed. GainSeeker now updates any blank Long Description in Events, Causes, and Actions Taken when the GainSeeker Charts module is launched. This may cause the Audit Trail change dialog to display when GainSeeker Charts is launched.
Charting more than three SPC standards that all contained the percent symbol (%) could generate an error message such as "Error in Like operator: the string pattern ... is invalid." This issue has been resolved.
After using drill-down functionality on a Pareto chart to view data for just one bar and then changing a retrieval setting (such as date range), the resulting chart included all data and lost the drill down criteria. This issue has been resolved.
Storing a Combination chart, Scatter chart, Time Axis chart, or X-bar/Moving Range/Range chart in a Desktop would not save the Show sigma stripes setting in the Desktop. This issue has been resolved.
When defining the columns for a DMS data table, a "Count" column was erroneously displayed on the list of available columns. This issue has been resolved.
When selecting a different Python script for a Formula test and then cancelling the selection by clicking the X (close) button on the top right of the dialog, the new selection was not cancelled and was selected. This issue has been resolved.
When editing a Planned Inspection, if the selected Inspection contained a Traceability test with the BarcodeAllowed property set to True, the display of Traceability fields did not indicate that the Inspection contained this Traceability test. This issue has been resolved.
When sending a real-time failure email from a sub-inspection with charts, the Compose Email window would remember whether or not charts were attached to the previous email. However, if the previous email had been sent from a sub-inspection without charts, then the Compose Email window would remember that no charts were attached to the previous email, instead of remembering whether or not charts were attached to the last email that had the option to attach charts. This issue has been resolved.
When using a Device Profile that was configured with a Write To Device field containing \r (carriage return), \n (line feed), or \t (tab), this module would display the error message "EOL while scanning single-quoted string". This issue has been resolved.
In a Defect List test with the EnableSampleSize property set to True and the SampleSize property set to a value, if the inspector entered a different Sample Size during data entry, the data was still stored with the default sample size (from the SampleSize property). This issue has been resolved.
When executing Formula tests with Python scripts in a sub-inspection, executing any Formula where the FormulaMode was Click or OnChange would erroneously enable any sub-inspection tests that had been disabled by a Formula with FormulaMode set to Pre. This issue has been resolved.
When executing Formula tests with Python scripts in a sub-inspection, a Pass/Fail/NA test that was disabled by a Python script was not grayed out. This issue has been resolved.
In a sub-inspection where the ShowIndividualNote property was True, using a Python script to disable a Pass/Fail/NA test, Numeric Input test, or Defect List test did not gray out the individual Note button for the disabled test. This issue has been resolved.
When double-clicking in a Numeric Input cell to highlight the existing value, any minus sign in the text was not selected. This issue has been resolved.
When an inspection launches a Python script, it disables the buttons on the PC Collect screen. Sometimes, the script would not return properly and the buttons would not get enabled. This issue has been resolved.
When a Python script used the inspect.setnextinspection(None, True) command to return to the list of Planned Inspections but the script also had the inspect.cursubi.cancel() command, it would return to the list of Inspections instead of Planned Inspections. This issue has been resolved.
When running a Sub-inspection with Text tests, the cursor was not initially placed in the correct test and would not move between tests properly. This issue has been resolved.
When an Inspection was set to force a note for real-time failures and a chart in the side panel was based on a specific Numeric Input test, the chart would not update correctly if the Submit button was clicked before entering the note. This issue has been resolved.
When sending an email for a Numeric Input real-time failure, the operator note was not included and the chart was not current with the last subgroup. This issue has been resolved.
When using a Traceability field that did not have a pre-defined list and creating a list for it with a Python script, the field did not display the list. This issue has been resolved.
If a Timer test was running when the user clicked Submit on a Sub-inspection, GainSeeker would display the error message "The given key was not present in the Dictionary". This issue has been resolved.
When a Python script was running, all the tests on the sub-inspection did not get disabled properly. This issue has been resolved.
Launching a Python script erroneously enabled all Numeric Input tests on the current sub-inspection, regardless of their previous status. This issue has been resolved.
When making a Numeric Input visible via Python script, the Numeric Input test displayed at the top of the sub-inspection instead of the actual location of the test in the sub-inspection. This issue has been resolved.
When a sub-inspection tried to display a read-only document or a document in a read-only folder, the document would not display properly the first time. This issue has been resolved.
In the Python Script Editor, when you right-clicked the code window and then chose GainSeeker Python Commands, the table of commands that was displayed did not include the Login command. This issue has been resolved.
In the Python Script Editor, when editing an Action-based script where an Action displayed a long Description, the Edit button for the Action would sometimes cover part of the Description. This issue has been resolved.
The Python commands statdms.data.datetimedisp() and statspc.data.datetimedisp() ignored the Show time to configuration setting when formatting the time stamp. These two commands were hard-coded to display the time stamp to the number of seconds - even when the current configuration was set to display more detail (hundredths of seconds) or less detail (minutes). These commands now use the Show time to configuration setting when formatting the time stamp. This issue has been resolved.
When editing a Python custom code block, changes would not always be saved correctly. This issue has been resolved.
An error occurred when editing a Python script that used a Condition action that had another action inside the condition. This issue has been resolved.
When creating a new database connection, checking the Trusted Connection box and then switching to a Database Provider that does not support trusted connections would disable the User id and Password fields. This issue has been resolved.
The SQL script to copy data for a MySQL database contained several minor syntax errors. This issue has been resolved.
When using the Standard Utility function to export Process Specifications, GainSeeker displayed the list of SPC standards instead of the list of Process Specifications. This issue has been resolved.
When using the Standard Utility function to import Process Specifications, GainSeeker generated an error when limits were set to None. This issue has been resolved.
When using the Standard Utility function to export Standards, GainSeeker generated an error when the name of the Standard included a single quote ( ' ). This issue has been resolved.
When working with Planned Sessions, the Part Number field would not support a value longer than 30 characters. This issue has been resolved.
When checking for "Range Run above R-Bar" or "Range Run below R-Bar" and using Run values based on Gate, GainSeeker generated a run time error 438 and would not continue. This issue has been resolved.
The SPC statistic number for CuSum decision interval has been corrected.
For the Dynamic Reports module, the parameter to automatically open a Mixed report has been added to the existing documentation for the other report types.
The table of GainSeeker Python commands has been updated to include the Login command.
For the Formula test in PC Collect Inspections, the table of OnChange triggers has been corrected for DMS Standards, DMS Event, SPC Event, SPC Cause, and SPC Action Taken.
Documentation of the inspect.cursubi.cancel() Python command has been updated to note that this command suppresses the warning message about unsaved data being lost.
Documentation of the Custom Statistics Editor and the newstat special variable has been corrected.
Documentation of the File Import Wizard has been updated with the correct location of the *.fiw configuration file.
The list of Tables and Files used in GainSeeker 8 has been corrected to note that each configuration can use its own copies of the tables VPRI, VPRIDT, DPRI, and DPRIDT.