1.6.xx.xx

Version 1.6.13.00 10/30/2020

  • Fixed an issue that would prevent user panels from working if the security settings denied access to the main Devices object since their ability to work relies on being able to check the service load state and the ping property.

    • Get operator only is granted access to that object's few properties for all valid user logins so that these properties may be queried.

  • Added some error trapping to catch a rare situation where an ip client in the process of being disposed and sending at the same time might cause a crash.

  • Removed an error message from the logs regarding the failure to remove meters from a lookup collection that is not actually an error.

  • Clarified an info log message to make it less error-like regarding Qor Lwcpss message handling for amix.

    • "amix" parameter support currently requires the beta version.

  • Fixed an issue with the userpanels xy grid and locks with virtual routers.

  • Added code to decode ampersands properly in uerspanel properties that use url as their property type in the property grid.

  • Fixed an issue where the user panels list web page still displays notes and warnings about using legacy panel designer.

    • These notes should have been removed in version 1.4.

Version 1.6.12.00 09/25/2020

  • Fixed an issue with user panel countdown clocks where the change of countdownlength was not being raised to sapV2 and therefore would not update data in the countdown clock without refreshing the panel web page.

  • Fixed an issue with user panel countdown clocks where reloading the page or changing the countdown time on a page where the timer had elapsed but not been reset would show the count down duration instead of 0.

  • Added code for user panel countdown timers in countdown mode to display 0 if countdownlength minus elapsed milliseconds is less than zero.

  • In the User Panel Designer, added an alert and block to the countdown timer --countdownlength, stopmode, and resetmode properties to prevent them from being unbound as binding must be left on for them to function properly.

Version 1.6.11.00 09/11/2020

  • Fixed an issue with UserPanels where it is possible to start receiving state messages before the bindings file is loaded leaving those states with no place to go.

    • This could cause some panel objects to have an incorrect starting state when the panel gets loaded.

    • To address this problem, this version does not connect the web socket until the bindings file has been loaded.

Version 1.6.10.00 09/10/2020

  • Fixed an issue where phase 1 of the Lwcp state initialization was sending GET SUPV STATE whereas Quasar would only accept GET supv state.

    • The result was that with Quasar we would often not get to phase 2 and therefore not get initial states for a variety of parameters until those parameters changed.

    • For example, a user panel label bound to the show profile name would likely be blank on system startup until the show profile was changed or we happened to poll that parameter.

Version 1.6.9.00 08/25/2020

  • Fixed an issue where generic emulators set to TcpClient mode were not raising connected change events.

  • Fixed Connected property for Device Emulator listeners so that it will be true if at least one client is still connected and False otherwise.

  • Fixed an issue where subscribing to a GenericEmulator would yield a ToSend event with an empty string for each ToSend attempt.

    • ToSend is a write only property and should not raise events.

  • Fixed Generic Emulator ConnectedCount not displaying the correct count and not changing when tcpclient is selected as the connection type.

Version 1.6.8.00 08/15/2020

  • Fixed an bug introduced in version 1.6.6.00 where user logs were no longer accessible from the web ui and were instead showing a forbidden access error message.

  • Fixed a bug where the disabled property on Html5 user panel buttons was not being respected by touch actions on touch screens.

  • Added a blankvalue property to the saselector drop down control in html5 panels.

    • The blankvalue property allows you to define a value to use if the value returned is blank.

    • For example, the manual example refers to using the currentsource property of a virtual destination and filling the list with virtual sources.

    • The None source has a value of "0" but often a cleared destination route is returned as a blank field instead of 0.

    • Using 0 in the blankvalue property will force the empty currentsource to be interpreted as 0 which matches the none source causing it to be displayed.

    • Without this property being configured, a destination with nothing returned as the current source will simply not make a change to the current item in the list causing it to retain a route where none actually exists.

    • This has been implemented as a separate field because each list might or might not require different values to be used or not used for a blank field.

Version 1.6.7.00 07/17/2020

  • Please review the release notes for the non-public 1.6.6.00 version as those changes exist in this version as well.

  • Change the factory default file to alter the timezone localtime symlink rather than overwrite the file.

    • In some cases this was overwriting the underlying symlinked file causing a specific timezone to show Eastern offset rather than the correct offset for the timezone after a factory default.

    • Bank updating would fix the problem as well until the next factory default.

  • Added a question to the r2 production install script to ask if it is being installed on the mbx platform.

    • If the answer is yes, the crystal fontz display application is disabled and we use the new default ip addresses in the ip address questions.

Version 1.6.6.00 06/12/2020

  • This version includes major changes in how PathfinderCore PRO is compiled and built in order to bring it more inline with other Telos Alliance products and Continuous Integration policies.

    • As this is a major change, please report any bugs you encounter.

  • This version was not publicly released.

Version 1.6.5.00 04/22/2020

  • Fixed an issue where an image assigned to an SaConsole button would not display and would disappear after saving the panel.

  • Fixed an issue changing the name of a logic flow view (folder) would cause flows within that view and/or its sub views that have combiners in the flow not to function past the combiner.

    • Previously the workaround was to either reboot or rebuild the flow.

Version 1.6.4.00 04/06/2020

  • Fixed an issue where the default friendlyname if no other was specified for an object was the object type without the id which led to duplicate entries in the logic flows tree.

  • Fixed issues with image properties in the user panel designer not displaying a list of panel images as choices in the translation dialog.

  • Added the overflow property to label controls which when used in conjunction with text-overflow can prevent the text from overflowing the label.

  • Fixed an issue in the user panel designer where the image selection dialog appeared when pressing the bind button for background-image and img src properties when it should not.

  • Fixed an issue in the user panel designer where the image selection dialog appeared when clicking the property header for background-image and img src properties when it should not.

    • These two issues made it difficult to get to the flow editing of those properties.

  • Fixed an issue with image fields in the user panel designer property list where the shift-click option for manual editing would not work.

  • Fixed issues with images switching from relative url to full url when saving a user panel design.

Version 1.6.3.00 03/19/2020

  • Fixed a bug introduced in 1.6.2.00 which only affects a small number of customers who have been provided with information about using auto insert limits in Axia Audio Routers to split Ios from different sites into different routers.

    • 1.6.2.00 changed when backfeed sources where tested against the autoinsert limits which broke backfeed discovery when auto insert limits were used.

    • That should be fixed in this version.

Warning: If migrating from a patch version earlier than 1.6.2.xx or 1.7.2.xx review the notes for 1.6.2.00 and 1.7.2.04 regarding a manual sync.

Version 1.6.2.00 03/18/2020

  • Fixed additional bugs related to discovering backfeeds introduced in 1.5.20.43.

    • New backfeeds were often not being discovered into the router or on clusters they might only be discovered on one of the systems or neither of them.

  • Fixed an issue where newly discovered Ios (especially backfeed ios) might not make it into the io lookup table on the secondary server in a cluster.

    • This might cause certain parameters on those ios to not update until/unless the secondary server took over.

  • Fixed issues with the cluster synchronization of newly discovered backfeeds which was not working correctly in all situations.

  • Fixed an issue where the secondary server in a cluster might not show the current owner changes for backfeeds until/unless it took over as primary.

  • Fixed an issue with Gpio routing to iport destinations which was not allowing the route to take place.

    • The command was sending invalid name information in the SRCA property which other devices allowed but Iport did not.

Warning: Because of the discovery issues above it is possible that clusters might have backfeed Ios on only one server or the other. After updating, a manual sync from primary to backup is recommended. Review the manual for details on executing a manual sync. To sync from Primary to Secondary, open the clustering tab on the secondary server and click the manual sync button. This will request a special clustering backup from primary and restore that backup into the secondary PathfinderCore PRO which will subsequently trigger a reboot of the secondary PathfinderCore PRO.

Version 1.6.1.00 02/27/2020

  • Fixed bugs introduced in 1.5.20.43 related to how backfeeds are handled differently with iQx/Qor.

    • The changes required to handle differences in how iQx/Qor handle backfeeds caused backfeeds to sometimes be created without certain information in the database.

    • In some situations this could cause the backfeed to display as a normal source rather than a backfeed source.

    • The backfeed rtp stream address was also appearing in some cases in the device's normal port causing multiple source targets for a route due to the duplicated multicast address.

    • This version fixes the missing data in the database on ingest of the io so that it properly gets created as a backfeed object.

    • This version fixes the missing data when new backfeeds are discovered on an iQx/Qor and are added to the database.

    • This version sets the device port to no address, disabled, and a default name in the source table when being used as an autobackfeed style source.

  • Updated copyright footer on web pages.

Version 1.6.0.00 12/05/2019

  • 1.6.0.00 release build for fanless engine, r2, and vm platforms.

  • This build is the same as 1.5.20.43 but moved to the master release branch and versioned as 1.6.0.00.

  • All future bugs related to features already in this version will become patches to 1.6 versioned as 1.6.x.00 where x is the patch number.

  • All new features will be created in the next 1.7 beta branch.

  • See Version Numbering for details.

  • Updated the manual link to version 1.6 of the manual.

Last updated