Multiple Shared Database issues #360
Description
I finally got this working today and have run into several quirks in the way it works. The following are some areas that need looking into in no particular order.
- when I add a spool it doesn't show up in the lists of spools without exiting and coming back in.
- the refresh button doesn't seem to do anything, it should re-query the database for spools.
- It let me put in two spools identical to each other. I did this because of issue number 1, I thought I did something wrong so I added it again. When I looked in the actual database table, I saw there were two.
- For some odd reason, the color was set to show the two older spools I had in the system, but not the new brown one I was adding. I had to go in and select the color filter to get it to show up. That may be the reason behind issues 1 and 2 now that I think about it. I had never filtered anything in this system before and this was the first brown spool I have added.
- when you copy the local database to the shared database, It really would be nice if you gave people the ability to append to the existing data rather than truncate it. Let people choose.
- Some work needs to be done around what happens when you run out of filament half way through a job. If there isn't feedback from the printer, the user should be able to click a button indicating a filament change so that the first roll can be depleated out of the system, and the second roll assigned to the print. Just curious how does it handle color changes on a MMU?
I'm a retired developer and DBA. If I can help work through any of this with you, let me know.
Thanks