|
Build 839:
· Fixed: Modbus: Dropping values when there were 2 devices on different IP addresses, but with the same Slave address, where one of them had an error
· Fixed: Modbus: Problem autodetecting a device which was connected to a COM port, which had been disabled
· Fixed: Networking: Local/Remote connections over the Internet to different countries, where timezones differ, can mean that some Configuration files are sent on every connection, not just on the first connection
· Fixed: Networking: IP addresses beginning with a single digit were not considered valid, so the Local was not started
· Fixed: Networking: Multi-homed issue where Local setup on an IP address beginning with a single digit is not remembered
· New: ActiveX: Controls where the version differs between that used by the Configuration and that installed (registered) on the PC can now be used, with automatic adjustments based on names applied, where appropriate, and error messages displayed where automatic adjustments cannot be made
· Fixed: ActiveX: Controls on a screen are not updated with the values of inputs, under certain circumstances, if the screen is closed and then re-opened
· Fixed: ActiveX: Value checking on ActiveX Controls has been optimised to improve the speed of opening a screen
· Fixed: ActiveX: The message about a conflict of ActiveX version numbers was being displayed erroneously when AXL files were present with no corresponding GDW or GD3 file
Build 838:
· Fixed: ActiveX: Improvement in the rate that ActiveX controls update, when there are many controls on a screen.
· Fixed: Copy & paste of items that have been grouped together, could affect their names.
Build 837:
· Fixed: File->Open followed by double-click to select the file can cause a problem if the screen contains ActiveX objects or OLE objects.
· Fixed: File->Exit from Runtime mode with a Local defined, but without having any Remotes attached, could occasionally cause a problem.
· Fixed: During dongle upgrade SpecView doesn't now assume that the first 8 characters of all Step2 codes will be the same.
· Fixed: Clicking the [Help For Instrument] button on the 'Add/Rename Instrument' box tried to invoke .HLP as well as .CHM help files.
· Fixed: The Parameter list now fills in from the top down to the bottom rather than randomly, and there is a better match between the "Par List PPS" in File->Preferences and the comms bandwidth with block requested data. Consequently the Parameter list should appear to update faster.
· Fixed: ActiveX: filenames in the lists of ActiveX controls now show the full filename rather than an abbreviation.
· New: Modbus: Instruments with automatic 'Scaling of Numbers' now have better control over the rate at which the Decimal Place parameter is requested, this results in reduced comms. New driver commands SONTTL (Scaling Of Numbers Time To Live) and SONBL (Scaling Of Numbers Block Length) for manually specifying a longer time than usual. See release notes in the software for further details.
· Fixed: Modbus: Could show negative values when reading & writing Time parameters.
· Fixed: Modbus: Getting Modbus exception codes could cause the driver to lockup over TCP/IP.
· Fixed: Modbus: TCP Autodetects did not handle initial connect failures well, resulting in a failure to find instruments.
· Fixed: HC900: HCDesigner Import for Update would sometimes create a new instrument definition, rather than updating an existing one.
· New: Watlow: EZ-ZONE PM and ST controllers supported over Modbus, including auto-detection.
· New: Watlow Demos, Help file and Addendum PDF.
· New: Watlow: Updates for the F4 controller.
· New: RKC: Improvements to support for the SRZ controller.
· Fixed: Eurotherm: Improvements in support for the 3504.
Build 836:
· Fixed: ActiveX: When a Remote connection was made to a Local running a configuration containing ActiveX controls it was possible for it to hang.
· Fixed: Modbus: Problem when an error code generated by the instrument was received over serial comms.
· Fixed: OPC: Improvements to the support for the Beijer OPC Server.
· Fixed: OPC: When using the RSLinx OPC server it is now possible to create instruments within a group.
Build 835:
· Fixed: Copy/Paste did not always work because Edit->Paste was greyed out under certain conditions.
· Fixed: When using Remote / Local networking between computers that are in different timezones, it was often the case that the entire configuration was sent across the link when the connection was made.
· Fixed: When using Remote / Local networking it was not possible to set a SpecView User Variable from a Remote to the Local.
· Fixed: Remote connection setup would not remember the packet size if set to less than 8000 bytes.
· Fixed: When setting up a Local PC to listen for incoming TCP/IP connections, the File->Preferences box could, under certain circumstances, cause a crash.
· Fixed: On a Local PC, using Recipe Save-As in the Recipe Manager would cause the message: "Attempting to Start Local on..." to be displayed.
· Fixed: When using File->Preferences on a Local PC, a message saying "Attempting to Start Local on..." could be displayed briefly.
· Fixed: When defining an instrument, the [Address help] button would not always give the correct help.
· Fixed: When using a Configuration which contains ActiveX controls, that are not yet installed on this PC, using File->Preferences could sometimes cause a crash.
· Fixed: Buttons could occasionally lose their font information when positioned very close to the top or bottom of the screen.
· Fixed: ActiveX: Further improvements to the handling of bitmap buttons and ActiveX Design mode (or Properties Sheet).
· New: ActiveX: Better handling of the loading of ActiveX Controls lists throughout SpecView.
· New: Modbus: The 'J' is no-longer required on standard Modbus addresses. Also, the default port number (:502) can also be ommitted.
· New: Modbus: New driver command MINTL which superceeds the driver commands: BTTL, WTTL and TCPTL. See here for further details.
· New: Modbus: New driver command TCPERBS for use in systems with redundant instrumentation. See here for further details.
· Fixed: Modbus: Problem with initial requests to some devices. See here for further details.
· Fixed: Modbus: Slow Modbus TCP/IP throughput caused by the driver occasionally requesting blocks of data too often.
· Fixed: Modbus: The driver did not correctly handle busy responses from devices over TCP/IP. The ECR (Error Code Retry) and ECR2 driver commands now work correctly.
· Fixed: Modbus: After setting either TCPLCTOR or TCPCTOR they would not then be shown in the Driver commands list.
· New: Honeywell HCDesigner: SpecView's HC900 File Reader now allows the Signal Tag or Variable number to be omitted from the name. Also, duplicate tag names have the tag number added to them to differentiate between the tags.
· Fixed: Honeywell HCDesigner: SpecView could not import these files when they had tag names (or variable names) containing commas.
· Fixed: Yokogawa Green series: The driver would cease communicating when altering enumerated value parameters.
· Fixed: OPC: The driver did not correctly decode 'unsigned char' data types.
· Fixed: Eurotherm PC3000: Occasional crash when loading a configuration with multiple PC3000 intruments defined.
Build 834:
· Fixed: Significant improvements in the robustness of SpecView when communicating with instruments over TCP/IP. These issues were more noticable on, but not restricted to, dual-core PCs. The effect could be either the comms error 1001, or possibly a crash.
· Fixed: Bitmap buttons would occasionally lose their bitmaps and, when positioned very close to the top or bottom of the screen could occasionally be displayed in the wrong place.
· Fixed: Copy/paste of bitmap buttons did not work.
· Fixed: If a Strategy Action caused a screen swap to a screen that did not exist, then a message was displayed saying so, this message stopped Strategy from executing any further actions until the user acknowledged the box.
· Fixed: Exiting SpecView during rapid communications with ModBus TCP/IP devices could sometimes cause a crash.
· Fixed: In a Configuration which was developed using a build of SpecView prior to 825, and where not all the GDWs have not yet been converted to GD3 files, when exiting Runtime, a message was incorrectly displayed saying that the Configuration had changed.
· Fixed: ActiveX Design Mode was not working, consequently Symbol Factory controls could not be edited properly.
· Fixed: HC900 File reader did not always mark Signal Tags as Read-Only and did not choose a useful short name for Signal tags and Variables - this caused problems when assigning these as pens to a Trend chart.
Build 833:
· Fixed: Strategy Controller could sometimes execute some Time-Based Events before the Startup Event.
· Fixed: In systems with a large number of opening screens and a large number of Strategy Events, it was possible for Strategy Controller to crash SpecView occasionally just after the screens were opened.
· Fixed: TCP/IP Modbus Autodetect - in the case where a TCP to Serial bridge device is being used to autodetect a number of serial instruments across TCP/IP, it was possible for the Autodetect routine to skip across Serial device Slave addresses without detecting them correctly - this usually occurred when there were gaps in the slave addresses of the instruments.
· Fixed: Problems with importing (or updating) some HCDesigner files for the HC900.
· Fixed: TCP/IP Modbus did not correctly handle the recipe facilities in the Watlow F4, also, Serial Modbus to the same device occasionally showed some intermittent problems with recipe.
Build 832:
· Fixed: In high-throughput Local/Remote situations where a lot of data is being passed from the local to the remote, the remotes could occasionally disconnect after many days of being connected.
· Fixed: In Strategy Controller, if there were a number of Events that all had the same trigger conditions in the “Watch For” fields, and one of them had an “Enable on Boolean” that was selected, but not filled in, then some of the other Events watching for the same thing may not trigger. The workaround was to fix the missing 'Enable on Boolean'.
· Fixed: Also in Strategy Controller, if there were a number of events that all used the same variable in the “Watch for” or “Test against” or “Enable on Boolean” filelds, and one or more of the other component parts was unavailable over comms, then the rest of the events might not be checked, even though it was valid to do so.
· Fixed: Grouping ActiveX objects with SpecView objects could cause a crash at runtime.
· Fixed: Long delay and error reported during startup caused by Local Networking startup on a different IP address has been improved. Now there should not be a delay during startup unless there really is a genuine network fault on the specified LAN connection. In addition, better reporting when a Local attempted to start on an IP address that does not exist.
· Fixed: 'Swap COM port' now correctly handles swapping from a serial COM port to TCP/IP and includes a reminder to add TCP/IP addresses to the instrument addresses.
· Fixed: Modbus could not handle redundant IP addresses in all situations due to a length problem on the address.
· New: Modbus now logs abnormal termination conditions.
· Fixed: Modbus redundant startup problem fixed.
· Fixed: Modbus instruments sharing a single TCP/IP address (as in the case of a TCP to Serial Convertor) can now have errors on one instrument without affecting the others on the same TCP/IP address.
· Fixed: Modbus failures in writing to an instrument could sometimes cause a 5 second delay in comms.
· Fixed: Modbus Comms Backoff was non-functioning, causing instruments that were switched off to keep retrying, wasting comms bandwidth. This was a fault with Build 831 only.
· Fixed: Yokogawa FAM-3 protocol failure when addressing more than one CPU on the same link.
· Fixed: Exiting SpecView from Configuration mode without saving the GD3 could mean that any changes to underlying configuration files could be lost, for example, changes to the Variables List. A save prompt box has been added (message number E12293).
· New: Honeywell HC900 HCDesigner Modbus Map import file support.
Build 831:
· New: The OPC Browser can now create a SpecView instrument from any parameters or groups selected in the tree. Previously, only an OPC group or single parameter could be selected to create an instrument from. Now, the tree supports multi-select, allowing any parameters to be selected for inclusion into an instrument. Also, the full hierarchy of the name can be optionally added, or not, to the names of the parameters created in instruments.
· Fixed: Some Active-X Controls could flicker noticeably during runtime.
· Fixed: Some Active-X Controls would not correctly display themselves. This particularly affected Active-X Controls written in Visual Basic.
· Fixed: A problem with copy/paste of buttons that could result in a GDW that could not be correctly closed. This could cause a crash when going from Runtime into Config mode.
· Fixed: Modbus driver was consuming an excessive number of handles on large configurations (with over 1000 communicating items). This could result in system instability from time to time.
· Fixed: Modbus TCP/IP could randomly fail when attempting to communicate with devices that are not accessible over TCP/IP.
Build 830:
· Fixed: Improvements to the fix added in Build 828 with respect to: Local PC could crash when Remotes were connected. This occurred at random, although it was more likely when running a large configuration with fast remote PCs.
· Fixed: When SpecView was exited using a button on the screen, passwords were disabled.
· Fixed: Remote Recipe Save / SaveAs did not work correctly when the recipe screen was still a GDW rather than a GD3.
· Fixed: Added the Japanese version of SpecView's Help, in HTML format.
· Fixed: Yokogawa Green Series driver now copes with errors more and is tested to work over TCP/IP virtual COM port
Build 829:
· Fixed: Configurations that contain ActiveX controls which are not yet installed (or registered) on the PC can now be Restored & run. Although a warning message will be displayed informing the user that the ActiveX controls need to be installed.
· Note: This release does not contains the Japanese version of SpecView’s Help.
Build 828:
· Fixed: Local PC could crash when Remotes were connected. This occurred at random, although it was more likely when running a large configuration with fast remote PCs.
· Fixed: Pressing the <ESC> key whilst in Configuration mode could cause a crash.
· Fixed: Remotes sometimes failed to notice if the Local PC became unavailable, so instead of giving a warning message they would just appear to ‘freeze’.
Build 827:
· Fixed: When time changes due to Daylight Savings Time, sometimes SpecView Remote/Local networking can think the files have changed due to the time difference. This causes little problem on a Network, but can cause long startup times on a Phone link - these files now have extra checking to see if they are the same.
· New: Help changed to be HTML help rather than Windows help to allow support for Windows Vista. Note that Help may not operate on Windows 95 any longer, depending on the updates applied. Some Instrument specific help may not yet work on Windows Vista – these will be changed as soon as possible and included in a future release.
· New: Choice of instrument views when putting an instrument on the screen. Certain classes of instrument can now support multiple different pre-canned instrument views rather than just the one allowed previously. For these instruments, when adding to a GDW, a choice of Instrument views is given. The user can select the most appropriate one for the task at hand, or indeed, use them all!
· New: :ActiveX Method Trigger Booleans: For methods that take multiple parameters, previously changing the value of ANY of the parameters would fire off the whole Method, making it difficult to setup the parameters of the Method without multiple invocations with incomplete data.
Now, each parameter of a Method has a Boolean Trigger allowing the Method to be triggered only when required.
Build 826:
· Fixed: Occasional lockups with DDE. A rarely encountered timing issue caused DDE transactions to stop after some time.
· Fixed: The display of the Local Networking Tx/Rx rates on the Local was not adding up the combined total of all the Tx/Rx rates of all the connected remotes.
· Fixed: Some OLE items could be copied incorrectly, resulting in an un-loadable GDW
· Fixed: Crashes when manipulating Active-X objects have been protected against
· Fixed: SV32.INI DDE settings in wrong place, causing some to be incorrectly applied when SV32.INI moved from the windows folder to the sv32 folder.
· Fixed: File->Save-As would behave incorrectly when saving to a filename belonging to a file that was still open in SpecView. This has been prevented from happening. Some other file -> Save-As anomalies have also been fixed.
· Fixed: ModBus driver TCP-IP fault tolerance has been improved in the area of multiple instruments where one or more instruments are offline - this no longer starts to affect the other instruments on different IP addresses.
· Fixed: Recipes did not show which items were in recipe at runtime
Build 825:
· Fixed: When connecting as a remote, sometimes Trend charts could blip down to 0.0 on User Vars. Local was not affected.
· Fixed: Active-X changes to allow passing of Strings back from functions (e.g SendEMail support)
Build 824:
· Fixed: Auto-open GDW's set as first were sometimes forgotten if files recently converted to GD3
· Fixed: Variables List Include Name was not remembered from one run to the next
· Fixed: Buffered driver (like Modbus) would freeze values 49 days after PC reboot.
Build 823:
· Fixed: Bug whereby fullscreen mode was not remembered from one run to the next
· Fixed: Bug where editing a button that was a GDW Swap caused it to no-longer work because files are now named .GD3
Build 822:
· Fixed: When doing Historical Replay on a screen that was still old GDW format from earlier builds, the screen could get converted into the new format, which had the undesirable effect of saving current values and color dynamic colors to the file. This no longer happens as the file is not converted during replay.
· Fixed: Active-X crashes with some controls - timing issues meant that sometimes SpecView could crash with some controls, apparently at random.
· Fixed: Active-X controls on Remote not working some of the time even though the option for running them on the remote was set.
· Fixed: If a configuration was read-only, then a strange situation could happen if it took more than 20 seconds to respond to the warning box about this. Also, if 'Cancel' was chosen, then none of the buttons on the 'Configs Found' screen were enabled.
· Fixed: The first Historical Replay after toggling into Full Screen mode would appear in a window rather than full screen.
· Fixed: After Historical replay, the menu bar could sometimes be incorrect after toggling Full Screen and back.
· Fixed:Mysterious RAD menu sometimes appeared.
· New: When a screen is converted from the old GDW format to the new GD3 format, a safe copy of the GDW is stored in an "OLDGDWS" folder for safe keeping.
Build 821:
· Fixed: Spurious message about not having Active-X controls enabled on configurations without Active-x Controls.
· Fixed: Random disconnects of remotes.
Build 820:
· New: Active-X Support - see SpecView’s help file for details and here
· New: When restoring a configuration, many checks are now performed to allow restore of configs over existing ones.
· New: It is now no-longer possible to create a new configuration by overwriting an old one - a new name must be used. This is to prevent accidental erasing of existing configurations and data.
· Fixed: Log File conversion including Alarms would sometimes miss off the last day's Alarms from the file.
· Fixed: Files transferred from one PC to another using a CD-ROM are left marked as Read-Only - this causes a problem in SpecView when such a configuration is run. SpecView now checks to see if the important files are marked as Read-Only and removes the Read-Only attribute from all files in the config to allow SpecView to operate correctly.
· Fixed: Recipe Downloads still in progress when SpecView exits runtime into configuration mode caused the download box to remain on screen.
· Fixed: Occasional SpecView crash related to event logging fixed. Problem was timing related and could happen for apparently no reason - although very rare.
· Fixed: Was possible to name different types of User Variable with the same name, e.g. a Bool called "trigger" and a Number called "trigger". This has been fixed to not allow duplicate names
· Fixed: User Variables occasionally lost their initial values when going from Config mode to runtime mode. Fixed (B0261)
· Fixed: When changing Variable list "Include names", the variables list would often collapse down - fixed (D0013)
· Fixed: In recipe mode, was possible to hit [X] in corner to remove recipe box, but still leave system thinking it was in recipe mode. Fixed. (D0012)
· Fixed: Button Action for Download Specific recipe would crash if no recipe was chosen. (D0014)
· Fixed: SpecView could crash under the situation where the last User variable is removed from a recipe and then runtime mode is entered immediately. (D0016)
· Fixed: Passwords allowed the same username to be created twice (B0196)
· Fixed: Renaming variables sometimes had an undesirable effect on the Log Report Format setup dialog. Fixed (D0017)
· Fixed: Button Attributes Download Specific to a Bool did not always have the correct Boolean senses shown. (D0018)
· Fixed: Strategy Controller Enable on Boolean did not show correct Boolean senses (was just true/false) (D0019)
· Fixed: Save-As a screen did not copy the recipe files if there was a recipe on that screen. (D0020)
· Fixed: Most recent recipe Name downloaded was not saved between run-time sessions. It now is remembered (B0225)
· Fixed: TCP-IP Networking was not correctly using the packet timeout value and so could cause significant resends of data on a very heavily loaded system
· Fixed: Crash when SpecView local is being monitored using "Host Monitor" software that repeatedly tries to establish a connection to SpecView networking post.
· Fixed: Visual Line Writer dialog box is now resizeable
Build 814:
- Fixed:SpecView could sometimes be very slow when there are a large number of UserVars (over 1000) and a lot of Strategy. There are now some settable options to control the amount of time spent by SpecView on User Vars - tradeoff between speed and Remote Connection update rate. See here for more details.
- Fixed:SpecView could be slow on systems where there are a large number of User variables on a large number of open screens (e.g. 40 or more open screens each with 50 to 100 values on) - Code has been optimized so that these screens take less time to update.
- Fixed:OPC Browser modifications to support new AB RX Linx Server
- Fixed:Print and Minimize buttons now work in Recipe mode
- Fixed:Some Enumerated Floating point values were not appearing correctly.
Build 813:
- Fixed: Using time-based copy of external instrument copied wrong value when the external value was not available over comms.
- Fixed: Modbus TCP/IP huge number and spurious alarms now fixed (Modbus version 1.0.7.12)
Build 812:
- New: Colour Dynamics can now apply to Bar Charts.
- Fixed: Password mode "Select-All" now marks the GDW as changed to force a save.
- Fixed: File->Exit or the [X] on the corner now prompts to save a changed GDW and does not cause odd behaviour if [Cancel] is selected.
- Fixed: Strategy Controller could sometime crash when copying String (text) variables from external instruments to SpecView User Variables
- Fixed: Selecting a running batch in the Batch Chooser now fills in the 'current time' in the log report dialog box rather than 1-Jan-1970
- Fixed: Selecting a running batch in the Batch Chooser caused a crash on timezones west of GMT
- Fixed: GDI handle leak fixed when using bitmaps on buttons.
- Fixed: Log file convert problem on busy PC's resulting in "could not read 4 bytes from timepacket" message.
Build 811:
- Engineering release, as 812 above
Build 810:
- Fixed: OPC support of Siemens SimaticNet OPC Server
- Fixed: Modbus Driver TCP/IP crash fixed (Modbus Version 1.0.7.6)
Build 809:
- Fixed: Crash when re-starting or exiting SpecView - fixed
- Fixed: Crash or delay exiting sometimes when very few IDF files loaded - fixed
- Fixed: Modbus Driver TCP/IP crash fixed (Modbus Version 1.0.7.2)
Build 808:
- Fixed: TAPI reconnects would occasionally fail to work - fixed - Fixed: Log report editing would sometimes crash - fixed
Build 807:
- Fixed: SpecView could crash sometimes when editing dynamic attributes of a variable that had been deleted from an instrument through the automatic update routine for parameter lists
- Fixed: OPC Rslinx changes for 'flat' appearance in OPC
- Fixed: Remote Alarm Clear bug fixed, allowing the Cleared status of alarms to be shown correctly on the Remote
- Fixed: Lack of CONFIG.VAR caused crash on exit of Runtime has been fixed
- Fixed: Tapi Idle disconnect now works correctly and also does not work during a long config download
- Fixed: Tapi password failure now puts up correct message
- Fixed: Tapi crashes in reconnect fixed - sometimes when the line was dropped through telephone service interruption, the Local or Remote would sometimes crash, depending on type of modem in use and speed of PC
- Fixed: Tapi remote crashes during connect fixed - again, dependant on type of modem and speed of pc.
- Fixed: Tapi retries number was incorrectly displayed in dialog box during re-connect and also the message displayed at end of retries was incorrect.
Build 806:
- Fixed: SpecView could crash sometimes when editing dynamic attributes of a variable that had been deleted from an instrument through the automatic update routine for parameter lists
Build 805:
- Fixed: DDE Decimal places set to 4DP for User Variables, and fixed to be the correct precision otherwise for normal instrument parameters
- Fixed: Sometimes SpecView would automatically assume that it needed to wait on a network link (SpecView local/remote networking), even when the networking option was not purchased. This behaviour has now been fixed.
- Fixed: Remote user password box now shows the password as "****" when entering.
- Fixed: Some problems relating to incorrect update of colour dynamics in recipe items that involve read-only changes have been fixed.
- Fixed: If SpecView installed in a custom folder, then these release notes could not be found! Fixed.
Build 804:
- Fixed: Startup buttons re-arranged for Mini8 CD
Build 803:
- Fixed: Problem where build 795 and earlier was set to wait on LAN for incoming network connection, upgrade to Build 800 and this was forgotten. This fix moves the old LAN-only Network listening to the new LAN/Internet/Modem way of doing it, but as in the notes above, it is best to check the File->Preferences, Remote Tab to be sure that the Local is waiting correctly.
Build 802:
- Fixed: Problem with double-clicking a Text Entry - sometimes this would cause a crash - this was caused by a problem when opening and closing the text entry box very quickly twice in a row (a double-click is actually 2 single clicks and so two boxes are created very quickly).
- Fixed: Problem when connecting a Build 800+ SpecView to a Build 795 and earlier SpecView resulted in a crash. Due to a change in the networking to support Modems, Build 800+ will not connect properly to Build 795 and earlier. This 'fix' prevents the crash, but the Local and Remote will both need to be 800+ for a real connection.
Build 800:
- New: Direct Dial Modem support in Local/Remote networking
- New: SV32.INI file has been moved to the SV32 installation folder - previously this file was stored in the Windows folder, but on some systems (e.g Win XP), if the computer user does not have access to the windows folder, then SpecView behaved oddly. See here for further details.
- Fixed: Problem with Strategy "Enable on Boolean" - if the parameter marked as "Enable on Boolean" was not available over comms, then the Strategy Controller assumed the value to be False and could sometimes trigger the event even though the status was not know. This has been changed so that any missing parts (Watch_For, Test_Against, Enable_On_Boolean) will cause the event not to trigger.
- Fixed: Problem with Trend Chart Update rates - if the GDW Update Rate was not set at 0 (In File->Preferences->Runtime), then the Trend charts would only update at a rate that was slower than that needed. For example, if the GDW update Rate was set at 10, then the Trend Charts would update at a rate 10 times slower than they needed to. This has been fixed so that the Trend Chart update rate is sufficient to feed each new pixel to be plotted and is independent of the GDW Update Rate.
- Fixed: In some national language versions of SV, various dialog boxes needed to be re-sized to fit their content. This includes the Historical Replay Control Panel and the Log File Conversion dialog.
- Fixed: Help buttons added to some error messages in Local/Remote networking (especially Modem based) to aid in the resolution of connecting problems.
|
