bugfix: split fan/speed slider callbacks to fix gcode dispatch collision#212
Open
gmmcosta15 wants to merge 1 commit intodevfrom
Open
bugfix: split fan/speed slider callbacks to fix gcode dispatch collision#212gmmcosta15 wants to merge 1 commit intodevfrom
gmmcosta15 wants to merge 1 commit intodevfrom
Conversation
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
controlTab.on_slider_change: now handlesfan_genericobjects only, dispatchesSET_FAN_SPEED.tunePage: add_on_speed_slider_changefor print speed (M220);on_slider_changehandlesfan_genericonly.printTab: minor cleanup following the callback split.Motivation
When a
fan_genericwas named"speed", bothcontrolTabandtunePagewould dispatch conflicting gcodes (SET_FAN_SPEEDandM220) on the same slider event. Splitting the callbacks eliminates the collision and ensures the correct gcode is always sent.