Skip to main content

mXrap 6.1.4 - Release notes and Changelogs

mXrap Team
mXrap Developers

6.1.4 introduces a few bug fixes, and a new feature: the ability to download files from HTTP and SFTP hosts (SFTP is for transferring files via SSH - used for downloading event files from IMS servers).

You will be prompted to upgrade by a yellow banner at the top of the Apps window. Follow the link to download and install.

What's New for Users - mXrap 6.1.4

Release Date: 30 September 2025

mXrap Changes

  • New Feature: Action button can now "Copy File" to or from a HTTP or SFTP network server.
  • Improvement: Update for Plugins to support new Stope Reconciliation App features.
  • Fixed bug: the Apps Window would sometimes not appear when there was a problem with accessing the root folder related to usernames and passwords.
  • Surveys: fix for decimation / cleanup,
  • Map3d import improvement: use unique vertices for each layer, rather than sharing ALL of the points across all layers. This especially helps when the imported Map3d survey isn't "cleaned".
  • Markerstyles: fix the reversing behaviour to only reverse Percentage thresholds.
  • 3D View:
    • Don't Fly/Go if the mouse is outside the Window bounds.
    • Improved 3D text rendering.
  • Panelview: Allow right-click-copy text from Value and Text elements.
  • Fixed a crash related to menus.
  • Charts: fixed a crashing bug related to charts and hover labels at infinity.

mXsync Changes

  • mXsync's file lists can now show all files in all folders in one list, and sort by the columns. This can help to identify large files in one list.

What's New for Developers - mXrap 6.1.4

Release Date: 30 September 2025

  • Tablecalc/Rowcalc: Builtin network.Http.query()
    • query() will now throw an Error if a network or HTTP error occurs (where a HTTP error is almost any code above or equal to 400). Devs can disable the throw behaviour with an option, or wrap calls with try/catch.
    • query() has additional advanced options for sending requests without fetching all the data (no_body) and for requesting the timestamp of the resource from the server (get_timestamp).
    • Passwords can be scrambled to avoid exposing secrets.