Scott Lahteine

- Spinning the knob still alters the feedrate, but now there is no feedback. - The more nonstandard / unexpected behaviors that are added, the more confusion that is generated.

Sounds close. Which of our existing boards is closest to this one?

So if a user wants to change a simple filament sensor for a motion sensor, they will need to have configured both. But, it would be nice if we had...

Thanks! I already noticed that, but hadn't updated yet due to falling asleep at my keyboard.

Before this can be merged, it needs to restore the old filament runout handling, including retaining `M412`, and to make the `M569` additions into optional features. RRF is designed to...

I'm still unclear on why the `home_offset` matters in checking the probe bounds (outside of a Dual X setup where it has a special meaning) because the coordinates being checked...

Note that the `manual_feedrate_mm_s` for a rotational axis should already _actually_ be in degree-per-time units, not mm-per-second. The name has not been changed, but that would be the idea for...

We should be expressing feedrates in mm/s for all axes in the G-code. Then we do any required math to produce a limited feedrate for all the axes in the...

Yeah, I realized later that in the angular case the prior inches-to-mm conversion on input would definitely mess with things. So, that means the feedrate either needs to be un-done...

I merged in the latest bugfix code, moving the `fr_deg_s` argument into the `PlannerHints` structure with the other optional arguments for the planner methods. The followup commit patches a few...