Describe the bug
After uploading to version 1.9.1 all my empty or suppose to be empty spools have been disappeared automatically... If i try to click on the check box "overuse spools" it seems to do nothing, because all the spools already gone.
On version 1.9.0 all the spools are present and disappeared only when check the "hide overuse"
Steps to reproduce
Go to '...'
Click on '....'
Scroll down to '....'
See error
Expected behavior
The filament manager, i think, that needs a general check box in the configuration menú to enable or disable the empty spools, but do not do it automatically without any method to recover the empty ones.
I have a spool that remain filament but i missed to change the spool while printing with other and i realize that that spools disappeared from all places.
On version 1,9,0 i continue having that spool with a -40g but i have it.
To workaround this, i access to the postgres database and put 1g, but the people with no knowledge about postgres neither sqlite will have a enormous headache :)
Screenshots
Version 1.9.0:
Version: 1.9.1
lol !!!!!!
After downgrade to 1.9.0 the check of hide overuse is working in reverse mode:
Describe the bug After uploading to version 1.9.1 all my empty or suppose to be empty spools have been disappeared automatically... If i try to click on the check box "overuse spools" it seems to do nothing, because all the spools already gone.
On version 1.9.0 all the spools are present and disappeared only when check the "hide overuse"
Steps to reproduce
Expected behavior The filament manager, i think, that needs a general check box in the configuration menú to enable or disable the empty spools, but do not do it automatically without any method to recover the empty ones.
I have a spool that remain filament but i missed to change the spool while printing with other and i realize that that spools disappeared from all places.
On version 1,9,0 i continue having that spool with a -40g but i have it.
To workaround this, i access to the postgres database and put 1g, but the people with no knowledge about postgres neither sqlite will have a enormous headache :)
Screenshots Version 1.9.0:
Version: 1.9.1
lol !!!!!! After downgrade to 1.9.0 the check of hide overuse is working in reverse mode:
Hide overuse checked:
Uncheck: