Changelog

New Features

Major Fixes

• Fixed linear scaling in MonitoringLive by ensuring register format is set in backend before applying scaling configuration
• Fixed register configuration persistence by loading configurations from backend when session is selected and marking workspace as modified when configurations are saved
• Fixed Modbus connection error handling (error 10053) by detecting I/O errors and discarding unhealthy connections, forcing fresh connection creation on next poll
• Fixed chart popout synchronization by resetting lastUpdateTime to include all historical data when initial sync is received from main window

Minor Fixes

• Fixed chart data overlapping between registers by including address in duplicate detection, preventing data from different registers with the same timestamp from being skipped
• Fixed chart point disabling by updating datasets in-place instead of replacing them entirely, which preserves Chart.js internal state for disabled points
• Resolved all cargo clippy warnings by removing unused function, converting single-match to if statement, and refactoring functions with too many arguments using parameter structs
• Fixed logger not creating new file when logfile is deleted while logging is active by checking if file exists before writing and recreating it if necessary
• Fixed Create chart menu label editing by restructuring the modal layout to prevent button click handlers from blocking input field interactions
• Fixed "Keep current devices" checkbox in NewWorkspaceModal to be checked by default (opt-out instead of opt-in)
• Removed redundant HEX/DEC/Binary format buttons from MonitoringLive and ModbusLogDialog (format selection is now handled through register configuration)
• Fixed start address validation in ModbusReader to allow address 0 (was incorrectly treating 0 as falsy)
• Fixed workspace loading to restore start address and offset in ModbusReader by saving and loading device formState in frontend and backend
• Fixed DataLoggerManager logging output to include function code specific register address (e.g., 40001 for holding registers) by adding register_type to LogEntry and calculating Modbus address with proper offset
• Fixed DataLoggerManager CSV output to include label field by adding Label column to header, label value to each row, and passing address labels from MonitoringLive to logging service
• Fixed TypeError when clearing workspace by importing selectedDevice and currentMonitoringSessionId at module level instead of using dynamic import
• Fixed register format not persisting in ModbusLogDialog by passing registerFormats and processedValues props from MonitoringLive
• Fixed formatted register values not displaying in logging output by using processed values in ModbusLogDialog preview mode
• Fixed scale factor and offset not getting default values when enabling custom calculations in RegisterConfigModal for the first time
• Fixed label not loading in RegisterConfigModal after being set in MonitoringLive by reading directly from addressLabels store instead of trying to load from backend