Skip to content

Conversation

@blaggacao
Copy link

@blaggacao blaggacao commented Sep 3, 2025

Expected

  1. User sets workzero
  2. Either: a) reset occurs or b) a M0
  3. The workzero remains set

Actual (before this patch)

  1. User sets workzero
  2. Either: a) reset occurs or b) a M0
  3. The workzero is reset to something else (what had been stored inside config-override.g)

@blaggacao
Copy link
Author

@chrishamm Would you kindly consider this (or a similar) improvement to the UI?

@blaggacao blaggacao force-pushed the v3.6-dev-fix-m500-workzero branch from fae2642 to 360dd34 Compare September 6, 2025 10:42
@blaggacao blaggacao force-pushed the v3.6-dev-fix-m500-workzero branch from 360dd34 to 4afb29b Compare September 8, 2025 15:42
@blaggacao blaggacao changed the base branch from v3.6-dev to v3.7-dev September 8, 2025 15:42
@blaggacao
Copy link
Author

@chrishamm This now targets v3.7-dev as requested in the forum.

Copy link
Collaborator

@chrishamm chrishamm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure if this is right, no other buttons in DWC call M500 because not everyone uses config-override.g. I'd be happy to make that change if there is a new option in the machine settings to specifiy if M500 may be called on workzero changes, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants