Skip to content

DueUI Release v3.3.0
Compare
Choose a tag to compare
@gtjoseph gtjoseph released this 31 May 18:31
· 3 commits to v3 since this release
v3.3.0
40a00da

DueUI Release v3.3.0

Breaking Changes:

  • This was true for the DueUI 3.2.0 release
    but I'm going to reiterate...You MUST be running a Duet
    board or Duet Software Framework installation at release
    3.1.0 or higher. There were simply too many object model
    differences between DSF and Standalone installations in
    earlier releases and I couldn't keep up with them.

  • If you stored your DueUI
    settings in your dueui_config.json file, the syntax has
    changed slightly. Instead of declaring the settings as a
    class class DueUISettings {, they're now declared as an
    object: configFileSettings = {. See the new default config
    for exact syntax. Other than this change, a configuration
    that worked in the previous version should still work as long
    as it was compatible with RRF 3.1.

  • I'm no longer going to host a DueUI installation at dueui.org.
    It's just too much trouble to maintain.

Changes:

  • There are no longer separate downloads and default
    configuration files for DSF vs Standalone installations. The
    same zip download and default configuration will work for
    both types of installations.

  • You no longer have to choose between DSF and Standalone
    installation types in Settings. It's autodetected.

  • There is now only one poll interval setting when operating
    in a Standalone installation. With recent changes made to
    RRF, the other poll intervals are no longer needed.

  • A new "Save" button was added to the menubar. It and
    the existing "Save" button in the Settings tab now change
    color when settings are changed to remind you to save them.
    Don't forget, "settings" can include things like jog speeds
    if you configured their widgets to save the value and
    restore it the next time you use DueUI.

  • The underlying JavaScript and CSS files have been
    reorganized to make loading from standalone devices less
    resource intensive. I was noticing that sometimes the pages
    weren't rendering and realized that the Duet had too many
    connections open to service the requests.

  • An "alt" property was added to the image widget to allow
    setting alternate text to be displayed if the image or stream
    can't be loaded.

Behind The Scenes

  • There was a lot of refactoring done to the connection and
    polling code that should make it more reliable (and easier to
    maintain for me).
Assets 3
Loading