Remove reference to 750us servo mode in webui #3452
Merged
+14,486
−14,497
Conversation
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
Collaborator
|
They are in the source tree so all our users that still build from PRs or branches don't have to have node installed etc. There's a build:all target in the package.json which builds all the combinations.
|
pkendall64
approved these changes
Dec 17, 2025
Member
Author
|
Thanks, PK, that does make sense for the Configurator's footprint on the user's systm. I'll build the headers as soon as I get a chance, I just got distracted with the size discussion on Discord 🫠 |
Contributor
Sorry |
mha1
approved these changes
Dec 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Removes the webui help text referring to the obsolete 750us servo mode and specifies that "Stretch" mode is also not used for failsafe.
EDIT: Ah crap I guess I need to rebuild the headers. Can we not get that as part of the build process? I guess not unless we require Node on the cloud build, etc, eh? Wait. If the github action can do it, why do we have them in our source tree?