Bug fix: speed for finish_layer was not properly set

This commit is contained in:
Lukas Matena 2018-03-19 15:35:31 +01:00
parent e41eff9186
commit 349a8a88ae
2 changed files with 1 additions and 2 deletions

View file

@ -1014,7 +1014,7 @@ WipeTower::ToolChangeResult WipeTowerPrusaMM::finish_layer()
else box.expand(-m_perimeter_width);
}
else i=2; // only draw the inner perimeter, outer has been already drawn by tool_change(...)
writer.rectangle(box.ld,box.rd.x-box.ld.x,box.ru.y-box.rd.y);
writer.rectangle(box.ld,box.rd.x-box.ld.x,box.ru.y-box.rd.y,2900*speed_factor);
}
// we are in one of the corners, travel to ld along the perimeter:

View file

@ -529,7 +529,6 @@ void TabPrint::build()
m_wipe_tower_btn->Bind(wxEVT_BUTTON, ([this](wxCommandEvent& e)
{
std::vector<double> init_data = (m_config->option<ConfigOptionFloats>("wiping_volumes_matrix"))->values;
load_key_value("wiping_volumes_matrix", a);
WipingDialog dlg(this,std::vector<float>(init_data.begin(), init_data.end())); // dlg lives on stack, no need to call Destroy
if (dlg.ShowModal() == wxID_OK) {