-
-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OP printer settings dialog does not query fresh settings #532
Comments
It now queries the settings, but its not passed on to the UI.
|
Should be able to sort without killing anything major. It just needs to call the cleaner again on the system one, or update the cached. Think I have a graceful work around after your comments anyway. |
Wasn't a cache update issue, it ran perfectly fine. It was me not pulling the correct information. Port preference comes from my getState command, so it needed to fire: getState, getSettings, getSystem. Has been fixed in latest PR. Just need to sort the button and write the test now. I created a new function for this anyway within state, this also calls the printer clean just encase there are any weird timing issues with the default timer. Ran a load of tests and now correctly pulls the new settings. |
Nice job! What in PrinterClean does it call, like a whole refresh? Oh btw, we are conflicting on PrinterClean most probably. I will try and minimize my PrinterClean changes on my bugfix PR #568, I propose for you to do the same. |
I shouldn't have changed printerClean here? If I did I'll undo it as I shouldn't need to. PrinterClean.generate function, it will run the cleaner for a single printer you pass to it so it now reruns that. In my tests the 500ms timer had mostly run already like by the time the updated settings had been called it was just to make sure. |
No your right I did aha. I tried to use the cache file, is that complete? It kept returning undefined for me so I updated the printer function to be able to return a single printer as well as the whole bunch. |
Ah my goof there, no that's a work-in-progress :S |
* version 1.1.13-hotfix * remove useless code * Initial Printer Settings class refactor. Fixed #532 * seperated try/catches * missing script import * #Fixed 351 * add power reset listener * button... doing... nut in * Squash printer settings dialog * Fixed #532 - Now correctly updates octoprint settings * Fixed #576 Fixed #577 * Fix for event listener not getting applied to save button * added checks for octofarm successful/unsuccessful update * allow Click Me button to refresh settings page. * clean up and test init * Add auth mock * Small whoopsie * introduce a prettier file to hopefully stop the random commit changes * jest test for 400 and 500 errors returned from update settings endpoint * Prettier * Changed prettier and add + run command * move refresh button so can be pressed at anytime fix issue with port preference been null * Prettier and gulp source maps * Prettier on already changed file * Prettier Ignore more specific client code * Prettier new file * Prettier on printer management runner * Split up getById and list (v2 CRUD style) * Fix le tests * Do my job properly this time * make settings saving refresh dialog unify the response into a single button removed 900 check not applicable anymore neaten up some styling * remove uneeded refresh calls Co-authored-by: David Zwart <davidzwa@gmail.com>
Description
Upon editing settings we gotta have the latest settings set from OP. Fix that with an OP API call. Also add a loader to printer settings dialog.
Repro
Open printer settings dialog.
The text was updated successfully, but these errors were encountered: