Skip to main content
Skip table of contents

DigAIRange

ComponentVersion
DigAIRange.exe5.10.847.1
DigAIRange.exe

5.9.817.9 (Patch)

DigAIRange.exe5.7.751.8 (Patch)

Dependencies

  • BCS 5.9.379.1 (recommended)
  • DigaSQL.dll 3.17.3485.0 (recommended)
  • MultiRec_4.ocx 4.7.302.0 (recommended)
  • OTMControl.ocx 2.5.703.0 (recommended)
  • DigaRTF.ocx 1.6.89.0
  • DigaContentTabHost 1.1.7.0 (of Release 2020.2)

New Features

  • DigAIRange now can handle different scaling configurations for the many dialogs and popup windows that may appear. Now when moving popup windows to monitors with different zoom configuration, the moved window keeps an individual scaling configuration, which is independent from the one of the main application. This was the last issue to solve concerning dpi awareness per monitor in DigAIRange.
  • All known controls and windows (in this build specially check boxes, radio buttons, normal buttons, etc) are now UiScheme/Themes compliant.
  • There is a new option in the View menu, which allows the user to change the currently used UiScheme (although DigAIRange doesn’t completely apply all color configuration of the scheme yet). This feature will officially be available with version 6.0 of DigAIRange. If you are interested in testing it already, it can be activated. In this case please contact DAVID Systems.
  • Design (UiScheme) colors are now applied for the background of the tree view, showlist and the navigation and filter bars, as well as for show info and the bottom pane if, and only if, no special color was set for it in the settings dialog. Splitters and scroll bars also observe these colors.
  • It is now possible (as in DBM) to define specific colors for specific toolbar buttons or for specific groups of toolbar buttons by specifying the respective keys (see table below) under the desired UiScheme configuration. (Attention: this works only in the UISchemes subkey of DigAIRange, not in the common UISchemes!)  (CCDA-2432)
  • The manage dialog for jingle groups allows to define media directory profiles now (like already available for shows). (CCD-42021)
  • Within the settings for an export module, it is possible now to use macro functions in the field "Expression". For more information, please see BCSTechManual chapter 8.4.2. This feature will be officially available with DigAIRange 6.0. For testing purposes, it can be activated earlier. Please contact DAVID Systems if you are interested in testing this feature.

Fixed issues

  • The title of the shows for show pools was not being loaded when the navigation keys were used to navigate through the days. (CCDA-2069)
  • Icons for start modes "relative" and "external" were inverted.
  • Handling of start mode/type "relative" for groups/stories and of "Default start mode for group elements" was not always correct. (CCDA-2042)
  • For any element that didn’t have the LinkIn value set, the LinkOut image was always being drawn, no matter whether it really had link out set or not.
  • In the manage dialog for the BroadcastServer properties the two fields for the port of the master and buddy server were greyed out. This was a new bug since build 798.0. (CCD-42123)
  • Removed unneeded spacing/padding when displaying text and images in the show list, which caused problems when updating from an older DigAIRange version (5.7). Also, in the tree view (on the left) the icons are now drawn a little bit bigger to improve visibility, as well as in the filter and navigation bar. Also, here spacing was adjusted to use the available space better and provide a more comfortable user experience. Together the drawing of LinkIn images in this column was corrected. (CCDA-2227)
  • Drawing of LinkIn values when only LinkIn is set was still wrong. (CCDA-2227)
  • When copying a show in the tree view and when selecting the option to compute new node IDs, the references of relative starts were destroyed. Note: if you are using a BCS version 5.2.311.0 or newer, this computation is done by BCS and you need a BCS build 5.9.378.1 or newer. (CCD-42062)
  • Made some improvements regarding the drawing of combo boxes in the metadata mask, which were so far drawn too often, causing some flickering. (CCD-42244)
  • When closing the modal metadata mask, it could happen that the mask still handled BCS notifications and displayed them, though the mask was already closing. This caused flickering and an unnecessary delay. (CCD-42244)
  • When right-clicking on a line in a rundown view in the upper window in order to show the context menu, it could happen that the mask in the lower window was not correctly changing to the clicked element before the context menu was displayed. This occurred only sometimes, depending on the exact timing of BCS and Windows messages. As a result, wrong error message boxes could have been displayed.
  • The list for the combo box items for Flags, StartMode and StartType wouldn’t display the entries completely lacking space. Now the size of the list is adapted dynamically as needed. (CCDA-2364)
  • When leaving the mask with a loaded group and without changes, the question "Do you want to save your changes?" did appear too often. This occured when special/old data was being present in one of the group fields: JingleGroup/JingleGroupName, DefaultStartMode or FillerAlgorithm. (CCD-42300)
  • A lot of issues were handled specially for the case where TurboPlayer is used with the main monitor having zoom greater than 100%. Besides there were also issues when the splash screen would change monitors during initialization, causing the application to start in a wrong way. Additionally, the functions to adjust the interface elements automatically were also fixed, which also had problems related to the same issue.
  • DigAIRange would crash if a popup window containing a tab control was created in a monitor which had zoom configuration > 100%. Also the dialog displayed when a show is loaded was not fully dpi aware
  • If the element’s mask was opened in a monitor which had zoom greater than 100%, the combo boxes that display images would have the wrong height.
  • The list for the combo box items for Flags, StartMode and StartType wouldn’t display the entries completely lacking space. Now the size of the list is adapted dynamically as needed. (CCDA-2364)
  • Whan starting DigAIRange, if the startup window didn’t have the focus, the login dialog would be displayed behind it and a second entry for it would be created in the task bar, making it difficult to see the login dialog again and giving the impression that the initialization of DigAIRange was interrupted.
  • When leaving the mask with a loaded group and without changes, the question "Do you want to save your changes?" did appear too often. This occured when special/old data was being present in one of the group fields: JingleGroup/JingleGroupName, DefaultStartMode or FillerAlgorithm. (CCD-42300)
  • Fixed a crash when opening a remote BCS-GUI and when the zoom value of the current monitor was applied to this new window.
  • The commands of the window menu to move the main window (or one of the other top-level windows) to a certain position did not work correctly.
  • Removing a key shortcut did not always work – the definition remained in the registry and a different shortcut was removed.
  • In non-100% zoom enviroments, selecting font sizes did not work properly.
  • The selection logic with the ressort filter dialog did not always work correctly.
  • When a different mixer source was selected for an element, this was not always / immediately displayed in the rundown view.
  • In the mask the input fields for the start type and mode were not wide enough to hold every possible text.
  • Fixed some drawing and focus issues around the comb boxes for distribution endpoints.

Changes

  • Breaking change: the background color used for Normal elements is now applied only to normal elements and not to the whole interface background, as it was before. New options were created to set the background color for the tree view and for the show list. 
  • Breaking change: The 3D grid look for the rundown view was removed from the available settings, because it is no longer supported after embellishment.
  • The text color for the tree view is not set anymore together with the font (in the View tab page), but in the Tree tab page under Text color. Besides, if no custom text color was specified, the text color defined in the Theme will be applied.
  • Replaced the used WebSocket library with an implementation based on boost::asio.
  • The settings dialog is now complete dpi aware when changing monitors, even though the main window is in a monitor with a different zoom configuration. Besides the tab pages of the settings dialog already apply almost completely the colors of the UiScheme.
  • There is a new option in the colors page of the settings dialog which allows for DigAIRange to use theme colors for drawing text if no special color was configured. Besides in this version sliders and splitters conform to the configured colors for themes.
  • DigAIRange does no longer put the name of the source show into the metadata field "ShowName" when a drag&drop is being initiated from a rundown window. This prevents the field being overwritten if it was set in the database. Hint: the field is still set when an element is moved to a day-trash, because this is done in order to make it visible from which show the element in the day trash was removed.
  • Removed unneeded spacing/padding when displaying text and images in the show list, which caused problems when updating from an older DigAIRange version (5.7). Also, in the tree view (on the left) the icons are now drawn a little bit bigger to improve visibility, as well as in the filter and navigation bar. Also here spacing was adjusted to use the available space better and provide a more comfortable user experience. Together the drawing of LinkIn images in this column was corrected. (CCDA-2227)
  • Since the rundown list doesn’t have vertical lines separating the columns anymore, there was the need to implement some padding on the right (at the moment 8 pixels in 100% zoom), so that in case the column width was not enough to display the whole content, the text of it wouldn’t come visually together with text of other columns.
  • As it was in version 5.7, the default configuration for hierarchy lines in the main list is to use gray dotted lines if nothing was configured. (CCDA-2431)



JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.