{"push_id":2130537827,"size":1,"distinct_size":1,"ref":"refs/heads/bf2_wednesday_tweaks","head":"2da29b40874bc0f5d25f834396e5c2c25de3fe69","before":"ab5a063672ae94a3df2c1121722c0aa50d5efa1e","commits":[{"sha":"2da29b40874bc0f5d25f834396e5c2c25de3fe69","author":{"name":"Scott Lahteine","email":"f27a17fc90c00d8c248d8510a1084221738b492b@thinkyhead.com"},"message":"Don't rewrite the mesh in refresh_z_offset\n\nIf using babystep to adjust the Z probe offset, the axis will move and the mesh will be updated at the same time, causing a doubling of the Z offset over the rest of the print.\n\nTo correct for this, the current Z position would need to be modified in the opposite direction, canceling out the additional Z offset added to the mesh. This would be confusing to users, and moreover it would not be accurate without also taking the current Z fade level and current Z height into account.\n\nIt might make sense to change the mesh in the case where no babystepping is taking place, but this could be considered an undesirable side-effect of changing the `zprobe_zoffset`.\n\nOne way to remedy this would be to return to storing the mesh with `zprobe_zoffset` included, then subtracting `zprobe_zoffset` from the returned Z value. Thus, a babystep moving the Z axis up 1mm would subtract 1 from `zprobe_zoffset` while adding 1 to all mesh Z values.\n\nWithout including the `zprobe_zoffset` in the `z_values` there is no safe way to alter the mesh in conjunction with babystepping, although it's fine without it.","distinct":true,"url":"https://api.github.com/repos/thinkyhead/Marlin/commits/2da29b40874bc0f5d25f834396e5c2c25de3fe69"}]}
{"actor":{"display_login":"thinkyhead"}}