Ability to move recent weight subtraction to a different spool

[CapnBry]

Is your feature request related to a problem? Please describe. Filament Manager is fantastic but what's not fantastic is my ability to remember to select the correct spool I have loaded before I start a print. This leads to the odometer applying a weight adjustment to the wrong spool. The plugin info log makes this information at least recoverable, but the steps of downloading the log, and applying the weight difference to the two spools is a little cumbersome for something that happens every few days to me.

Describe the solution you'd like It would be great if the database stored the last 5 or 10 update_filament_usage updates and they were accusable directly from the OctoPrint UI. Then, there could be a link to apply the weight diff to a different spool, just adding the weight back to the original spool and removing it from a new user-selected spool. The data is easy to capture, and the UI I think would be straight-forward to implement.

consumption table Schema

timestamp	spool_id	weight

Describe alternatives you've considered Downloading the log file? Possibly implement this in PrintJobHistory but that feels too external.

Additional context I'm not sure if the weight transfer should just update the consumption table with the new spool_id or add two new rows. I would think the former because it can still be applied back to the original spool or another spool without generating new rows. If new rows are created for every transfer, then it becomes confusing which was the original and then multiple transfers could occur and throw off the weight.

[OllisGit]

Hi @CapnBry,

thanks for the detailed description!

This is a really nice feature and I would like to implement this in the SpoolManager-Plugin, so I added it to my backlog. https://github.com/OllisGit/OctoPrint-SpoolManager/projects/1#card-42694565