Version 3.7.0-beta.3
Pre-release
Pre-release
·
7 commits
to v3.7-dev
since this release
New features:
- Added the measured force in grams of load cell probes to the status panel, with the raw readings moved into the tooltip
- Probe trigger highlighting uses the reported force where there is one, and negative probe thresholds are supported
- The object model browser can request verbose fields, and obsolete fields whenever a deprecated node is selected
- Added a delete option to the macro list context menu
- Added a setting to scroll panels into view on scroll
- The Settings page restores the tab that was used last
- Added a button to return to the device list when running inside the FindMyDuet app
- Added links to URLs in the object model browser documentation
- Multi-file analysis in the input shaping plugin handles recordings with different sample rates and lengths, and axis names come from the recorded file
- Updated the G-code documentation (M575 F, M915 alternatives)
Plugins and architecture:
- Added
registerModelPatchandpatchModelso plugins can augment incoming object model updates - Added
registerCodeInterceptorso plugins can rewrite or answer codes sent by DWC - Externalized the Vuetify composables so external plugins can use them
- Standalone plugin builds install missing dependencies declared in the plugin
package.jsonand remove them again afterwards; in-tree plugins report the missing packages instead - Stable builds ship their sourcemaps as
srcmaps.zipand plugin builds as<id>-<version>-srcmap.zip, withscripts/resolve-stack.jsto decode minified stack traces offline - Documented the new plugin hooks, npm dependencies and sourcemap handling in
PLUGINS.md
Changed behaviour:
- Renamed the Boards settings tab to Infrastructure to match its caption
- The firmware installer looks up IAP and WiFi binaries on the mainboard instead of scanning every board
- SBC reboot and shutdown buttons are disabled while a print is active
- Object model key queries are applied as authoritative updates, so values missing from a response are reset to null
Bug fixes:
- Filament changes only unloaded the old filament, because RRF discards codes that arrive while a message box is waiting to be acknowledged
- The temperature chart threw when a heater or sensor disappeared from the object model, stranding the reconnect after an emergency stop or firmware update
- Dialogs opened and closed in a background tab flashed up when it was reactivated
- The connection dialog fell back to "please stand by" while it was closing
- Custom values were not applied when confirming temperature and spindle inputs, and preset values were applied while typing
- Version checks did not handle prerelease suffixes
- Failed firmware uploads reported the wrong error message
- The G-code viewer camera was reset when a job started
- The printing file position jumped ahead of the code being executed
- Plugins with styles required a
package.jsonto build, and stale chunks could end up in the package ZIP