Skip to content

DIGIGUI v1.3.0-beta

Pre-release
Pre-release
Compare
Choose a tag to compare
@ReubenHill ReubenHill released this 26 Jun 14:07
· 27 commits to ReubenHill/updates since this release

Changelog v1.3.0-beta

General, compared to v1.3.0-alpha:

  • Fixed version number being incorrect on the GUI
  • Fixed a bug where plotted points would not disappear despite being remeasured
  • Fixed a bug where deleting a row would not remove the corresponding plotted point
  • "Set row as next location to measure" button renamed "Delete Coordinate Row(s) and Set Point to Get"
    • It now supports deleting whole selections of rows to delete, with the top row being set as the next point to measure
    • This is the recommended way to delete chunks of measurement data without losing location name information
  • Measurements skip over ones which have already been found to avoid accidental overwrites.
    • If you want to change a measurement you use the "Delete Coordinate Row(s) and Set Point to Get" button on it.
  • The "Remove last measured point" button now removes the last point that was measured in the order that they were measured by keeping a cache of measurements. Obviously it skips over points which have been deleted!
  • The toolbar now contains most of the GUI buttons, filed in logical places
  • Insertion changes:
    • "Insert Below" has been renamed "Insert Row Below"
    • A new "Insert Row(s) Below..." button allows multiple rows to be inserted
  • Double tap "warning" has been made an an error and measurements are disabled after it appears
    • Note that the point recorded as the second tap is now deleted after the error appears.
    • A new settings option has been added to allow double tap errors to be completely turned off in case someone really wants to measure points close together in sequence
  • Expected Coordinates changes:
    • When an unexpected measurement error occurs, further measurement is disallowed until the error has been cleared
    • An option to disallow measurements until expected coordinates are loaded has been added under "Options/Expected Coordinates..." as a second quest dialogue after the first one disappears (clunky but functional). This could be useful for those who use this feature regularly.
    • The expected coordinates file itself is now a CSV file with labelled location names (see attached files). If these do not match with current location names,
      loading will fail.
    • The expected coordinates are now shown on the table after they've been loaded as an extra set of columns titled "X exp., Y exp, Z exp.". Note: these coordinates are not coordinate transformed by atlas alignment
    • When an expected coordinate is successfully measured within tolerance, a checkbox to the right of the new columns is ticked
    • A "Reset Expected Coordinates..." is now find in the "File" menu - this removes all expected coordinates.
  • Measurement is now disabled when most popup windows are open
  • "Reset All..." under "File/Reset All..." is now available to completely reset the GUI.
    • An "Are you sure?" warning is given in case it's pressed accidentally
  • A warning has been added that "Export Locations..." does not save the coordinates data - users are pointed towards "Save Data As..." if that is what they want to do

The attached DIGIGUI_web.exe is an installer created using DIGIGUI.prj with MATLAB 2016b and the MATLAB compiler v6.3. It will download the MATLAB runtime environment when executed. See the licence information displayed upon executing.