Closed wawanbreton closed 1 year ago
26 tests ±0 26 :heavy_check_mark: ±0 15s :stopwatch: +6s 1 suites ±0 0 :zzz: ±0 1 files ±0 0 :x: ±0
Results for commit c92f8363. ± Comparison against base commit 559db006.
:recycle: This comment has been updated with latest results.
In order to fix the last bed temperature setting bugs, I changed the way
GCodeExport
handles it. ThewriteBedTemperatureCommand
method has a check to ensure that the same temperature is not send twice in a row. So I removed checks done before calling this method, and made sure that the initial temperature is properly initialized in thepreSetup
method. This way, thewriteBedTemperatureCommand
method will be called a bit more often, and it is fully in charge of knowing wheter the given temperature is different from the old one.An other change on the
writeBedTemperatureCommand
is that we don't send any GCode command in case it is called with the same temperature as before, but with a wait command. Before, we would have set the wait command anyway. This does make sense, but actually the wait case is used only once, in the situation that is being heavily refined and retested, so I think changing this behavior does not create an unwanted side-effect.Maybe we should also cache the
"machine_heated_bed"
setting inGCodeExport
so that it would take care of it inwriteBedTemperatureCommand
, making calls to this method simpler.